Thanks for the fast answers :)
I can't seem to use this solution, as i have different files that I include
or not, depending on the platform.
So i guess the good way would be to link all this together.
Here's where I'm stuck :
I try to use TARGET_LINK_LIBRARIES to "in the darkness bind them" (sor
Thanks for the fast answers :)
I can't seem to use this solution, as i have different files that I include
or not, depending on the platform.
So i guess the good way would be to link all this together.
Here's where I'm stuck :
I try to use TARGET_LINK_LIBRARIES to "in the darkness bind them" (sor
Thanks for the fast answers :)
I can't seem to use this solution, as i have different files that I include
or not, depending on the platform.
So i guess the good way would be to link all this together.
Here's where I'm stuck :
I try to use TARGET_LINK_LIBRARIES to "in the darkness bind them" (sor
Hello,
On 2/25/08, packadal <[EMAIL PROTECTED]> wrote:
> Hi, I searched for an answer to this question in vain, so I'm asking here.
>
> I am trying to build a library wich is spead among many subdirectories using
> CMake, but I can't seem to do it "the Right Way".
>
> Looks like the right way to d
packadal wrote:
Looks like the right way to do this would be to write a CMakeLists.txt
in each subdirectory, as this would be cleaner, and much more
changes-friendly, but I can't seem to build only one library when I do
it this way.
example of my source tree :
+ src
| - Application
| - A
Hi, I searched for an answer to this question in vain, so I'm asking here.
I am trying to build a library wich is spead among many subdirectories using
CMake, but I can't seem to do it "the Right Way".
Looks like the right way to do this would be to write a CMakeLists.txt in
each subdirectory, as
