Citron/externals/open_source_archives/CMakeLists.txt

add_library(open_source_archives
    src/FontChineseSimplified.cpp
    src/FontChineseTraditional.cpp
    src/FontExtendedChineseSimplified.cpp
    src/FontKorean.cpp
    src/FontNintendoExtended.cpp
    src/FontStandard.cpp
    include/FontChineseSimplified.h
    include/FontChineseTraditional.h
    include/FontExtendedChineseSimplified.h
    include/FontKorean.h
    include/FontNintendoExtended.h
    include/FontStandard.h
)

target_include_directories(open_source_archives PUBLIC include)
externals: Place font data within cpp files This places the font data within cpp files, which mitigates the possibility of the font data being duplicated within the binary if it's referred to in more than one translation unit in the future. It also stores the data within a std::array, which is more flexible when it comes to operating with the standard library. Furthermore, it makes the data arrays const. This is what we want, as it allows the compiler to store the data within the read-only segment. As it is, having several large sections of mutable data like this just leaves spots in memory that we can accidentally write to (via accidental overruns, what have you) and actually have it work. This ensures the font data remains the same no matter what. 2018-09-11 04:15:36 -04:00			`add_library(open_source_archives`
			`src/FontChineseSimplified.cpp`
			`src/FontChineseTraditional.cpp`
			`src/FontExtendedChineseSimplified.cpp`
			`src/FontKorean.cpp`
			`src/FontNintendoExtended.cpp`
			`src/FontStandard.cpp`
			`include/FontChineseSimplified.h`
			`include/FontChineseTraditional.h`
			`include/FontExtendedChineseSimplified.h`
			`include/FontKorean.h`
			`include/FontNintendoExtended.h`
			`include/FontStandard.h`
			`)`
Use open-source shared fonts if no dumped file is available (#1269) * Add open-source shared fonts * Address review comments 2018-09-11 03:31:01 +02:00
externals: Place font data within cpp files This places the font data within cpp files, which mitigates the possibility of the font data being duplicated within the binary if it's referred to in more than one translation unit in the future. It also stores the data within a std::array, which is more flexible when it comes to operating with the standard library. Furthermore, it makes the data arrays const. This is what we want, as it allows the compiler to store the data within the read-only segment. As it is, having several large sections of mutable data like this just leaves spots in memory that we can accidentally write to (via accidental overruns, what have you) and actually have it work. This ensures the font data remains the same no matter what. 2018-09-11 04:15:36 -04:00			`target_include_directories(open_source_archives PUBLIC include)`
No results found.