2016-11-18 13:55:24 +00:00
|
|
|
# benchmark runner
|
|
|
|
|
|
|
|
|
|
foreach(pkg_config_lib CAIRO)
|
|
|
|
|
include_directories(${${pkg_config_lib}_INCLUDE_DIRS})
|
|
|
|
|
link_directories(${${pkg_config_lib}_LIBRARY_DIRS})
|
|
|
|
|
endforeach()
|
|
|
|
|
|
|
|
|
|
add_executable(solvespace_benchmark
|
Use the same code for loading resources in all executables.
All of our executables need resources; e.g. the vector font is
a resource and it is necessary for generation. Before this commit,
the GUI executable loaded the resources in a nice way, and everything
else did it in a very ad-hoc, fragile way.
After this commit, all executables are placed in <build>/bin and
follow the same algorithm:
* On Windows, resources are compiled and linked into every
executable.
* On Linux, resources are copied into <build>/res (which is
tried first) and <prefix>/share/solvespace (which is tried
second).
* On macOS, resources are copied into <build>/res (which is
tried first) and <build>/bin/solvespace.app/Contents/Resources
(which is tried second).
In practice this means that we can add as many executables as we want
without duplicating lots of code. In addition, on macOS, we can
place supplementary executables into the bundle, and they can use
resources from the bundle transparently.
2016-11-28 04:16:18 +00:00
|
|
|
harness.cpp
|
|
|
|
|
$<TARGET_PROPERTY:resources,EXTRA_SOURCES>)
|
2016-11-18 13:55:24 +00:00
|
|
|
|
|
|
|
|
target_link_libraries(solvespace_benchmark
|
|
|
|
|
solvespace_headless)
|
Use the same code for loading resources in all executables.
All of our executables need resources; e.g. the vector font is
a resource and it is necessary for generation. Before this commit,
the GUI executable loaded the resources in a nice way, and everything
else did it in a very ad-hoc, fragile way.
After this commit, all executables are placed in <build>/bin and
follow the same algorithm:
* On Windows, resources are compiled and linked into every
executable.
* On Linux, resources are copied into <build>/res (which is
tried first) and <prefix>/share/solvespace (which is tried
second).
* On macOS, resources are copied into <build>/res (which is
tried first) and <build>/bin/solvespace.app/Contents/Resources
(which is tried second).
In practice this means that we can add as many executables as we want
without duplicating lots of code. In addition, on macOS, we can
place supplementary executables into the bundle, and they can use
resources from the bundle transparently.
2016-11-28 04:16:18 +00:00
|
|
|
|
|
|
|
|
add_dependencies(solvespace_benchmark
|
|
|
|
|
resources)
|
