I have a project with many libs and one executable.
I read this email exchange:
https://cmake.org/pipermail/cmake/2009-December/033979.html
on adding linker flags but this was from around 2009 and things most
likely have changed a lot since then.
in my executable my cmakelists.txt looks like th
So you want to hard code a location into the executable, but support
multiple locations without making multiple executables? These sound like
conflicting requirements.
Supporting multiple locations seems reasonable, so this suggests that
you'll have to change how your application looks for these
Hi!
This question bugs me for a long time so I though maybe someone has
a solution. I have a project which includes an application and some
data for it. An application needs to know path to its data files, so
I pass it via compiler definition: ADD_DEFINITIONS(-DDATADIR="...")
The problem is that
On Sun, Nov 29, 2015, 10:47 Dan Liew wrote:
Hi,
# TL;DR
I need a way of determining the header file dependencies of a source
file and inform CMake about them. CMake doesn't do this automatically
because I'm using custom commands for the compilation step so CMake
doesn't do it's usual magic of a
Hi,
# TL;DR
I need a way of determining the header file dependencies of a source
file and inform CMake about them. CMake doesn't do this automatically
because I'm using custom commands for the compilation step so CMake
doesn't do it's usual magic of automatically inferring source file
header depe