S_ABSOLUTE)? The only way I have found to get
an absolute path is to use file(GLOB which works for anything other than .
Kevin Fitch
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.ht
But that pushes the burden of dependency checking onto the developer, which
essentially negates most of the value of having a build system. I want to
know immediately if I make some change that has ripple effects on other
libraries, e.g. I might have updated a header file, so that other libs need
t
specifically call out that you want to specifically
link against the static (or dynamic) version.
Kevin
On Wed, Jul 14, 2010 at 9:13 AM, Michael Hertling wrote:
> On 07/14/2010 02:38 PM, Kevin Fitch wrote:
> > I have found a situation where transitive link dependencies don't seem to
&g
I have found a situation where transitive link dependencies don't seem to
work the way I would expect. I have a library A that depends on B. e.g.
target_link_libraries(A B)
# and elsewhere we have ...
target_link_libraries(foo A)
#then B gets linked into foo as expected
#But, if I try to be more e
target is a seperate invokation of
> make, including using make to validate the cmake files are built...
> it's not really the output but the huge amount of times that make is
> run.
>
> On Sun, Jul 11, 2010 at 8:40 AM, Kevin Fitch wrote:
> > I am transitioning from a
I am transitioning from a make based build system to cmake, overall I am
quite happy with cmake, but currently there are two snags:
1) The main project I am doing this on is quite large, it produces about 300
targets. So, when I type 'make' I get 300 or so lines of "[ 27%] Built
target blah..." ev
I have been converting an existing make based build system over to cmake,
and overall I am loving it so far.
I happened to run across CheckForPthreads.c, and was a little surprised to
see that it was basically a classic example of racy code.
The two spawned threads both increment res, which is th
