I tried that but then target_link_libraries will automatically add “-l” in
front of every additional flag I pass. Is there a way to pass other flags
without having it changed them?
i.e.:
target_link_libraries(${PROJECT_NAME} -Wl,--start-group foo bar -Wl,--end-group)
…ends up like this in the
On 29 December 2014 at 19:02, Evangelos Foutras evange...@foutrelis.com wrote:
Since commit 854e762 (FindRuby: clean up querying variables from Ruby)
we query RbConfig::CONFIG first and, if the command fails or its output
equates to a false constant, then fall back to querying Config::CONFIG.
On 2014-10-03 03:35, Rolf Eike Beer wrote:
find_package(foo 2.0 EXACT) means EXACT, i.e. only 2.0 is allowed. In most
cases this behavior is not the one that one would expect or need. Most people
would instead allow any 2.0.x version to match. This sort of selection is
currently impossible
Matthew Woehlke wrote:
On 2014-10-03 03:35, Rolf Eike Beer wrote:
find_package(foo 2.0 EXACT) means EXACT, i.e. only 2.0 is allowed. In
most cases this behavior is not the one that one would expect or need.
Most people would instead allow any 2.0.x version to match. This sort of
selection
On Fri, Jan 09, 2015 at 20:18:25 +0100, Rolf Eike Beer wrote:
Matthew Woehlke wrote:
On 2014-10-03 03:35, Rolf Eike Beer wrote:
find_package(foo 2.0 EXACT) means EXACT, i.e. only 2.0 is allowed. In
most cases this behavior is not the one that one would expect or need.
Most people would
I realize the cmake documentation says that everything that starts with “-“
should be treated as other linker flags, so I wonder, perhaps it’s a new bug,
or maybe just with a specific generator? In this case I am using the new NVidia
NSight Android generator for Visual Studio.
Can anyone
