Hi all --
We're thinking about extending CMake with a generator that outputs files
for the Buck build system we use here at Facebook (https://buckbuild.com)
Before we get started, was wondering if anyone's been working on such a
thing yet.
Thanks,
Mark
--
"There are 10 types of people in this
On 2016-12-12 13:10+0100 Patrick Boettcher wrote:
Hi list,
is there a policy which can be enabled to forbid calling
target_link_libraries(foo bar)
where bar is _not_ a known cmake target?
Right now, if 'bar' is not a cmake-target cmake tries to link with
-lbar (on linux). Can I inhibit this
Not sure if there is a policy for what you want, but I’ve accomplished
something similar via a macro that I use to link my libraries. It looks
something like this:
macro (LinkOnlyIfLibraryIsTarget linkTarget)
foreach (nextLibrary ${ARGN})
if (TARGET ${nextLibrary})
Hi list,
is there a policy which can be enabled to forbid calling
target_link_libraries(foo bar)
where bar is _not_ a known cmake target?
Right now, if 'bar' is not a cmake-target cmake tries to link with
-lbar (on linux). Can I inhibit this behavior in any way?
I'd prefer cmake telling me
Hello,
Can someone confirm please if this is a bug and whether I should file a bug
report?
Also, the "PRIVATE" workaround doesn't suit me (because it breaks
transitivity of includes). Is there any other workaround I can use? I
assume reverting to static libraries is the best thing to do in the
me