On 29 June 2016 at 05:08, Raymond Wan wrote:
> I agree that what we're observing is a problem, but I don't think it is
that big.
I must admit I am mixing a bit of my own situation here and trying to think
about the most general case. It's just there is a missing bit in the
dependency search syste
Hello Sven, Raymond.
On 28 June 2016 at 16:07, Sven Baars wrote:
> Hence my question if there is some "right" way of doing this with CMake,
without all of the code I wrote to work around the problem.
I am under impression there is an important bit missing from CMake export
system. If some librar
Hello.
I've posted a message a few days ago on a very similar subject. Didn't know
there was a discussion already.
The main problem in my opinion is that CMake target exporting system does
not handle transitive dependencies at all. CMake handles them correctly at
the build step, but not at the ex
> I have a source tree which contains multiple directories each of
> which has a subdirectory called "xyz". I want to create a target
> that creates a zip file with each of the xyz directories.
You can filter the file paths with a few CMake script lines:
file(GLOB_RECURSE FILES "./*")
foreach(FIL
Say the executable Exe uses some static library Foo which uses other
libraries, e. g. Bar:
Exe --> Foo --> Bar
As the developer of Foo and I want to make it easy to link against:
find_package(Foo REQUIRED)
target_link_libraries(Exe PRIVATE Foo)
The problem lies with the various dependenci
