HS>
HS> #!/bin/sh
HS> for i in *.c; do
HS> echo
HS> done
HS>
HS> Something like that? You can write the proper file lists to an extra .cmake
HS> file and include that into the CMakeLists.txt file or use a template file.
Yes, and I'm able to write these
Am Montag 26 März 2007 19:17 schrieb Michael Bieber:
> HS> Did you try adding a PROJECT call to every lib's CMakeLists.txt file?
> HS> Then run make -G ... on the top-level CmakeLists.txt file.
>
> No, I'm fiddling with a single lib for the moment.
>
>
> HS> It's in the FAQ why this is not a good i
HS> Did you try adding a PROJECT call to every lib's CMakeLists.txt file?
HS> Then run make -G ... on the top-level CmakeLists.txt file.
No, I'm fiddling with a single lib for the moment.
HS> It's in the FAQ why this is not a good idea (well, you will miss some good
HS> features) and you are for
Am Montag 26 März 2007 12:03 schrieb Michael Bieber:
> qmake is able to write VS projects for every lib and the executable
> preserving the given directory structure. How can I achieve the same thing
> with cmake? My globbing attempts turned the structure into plain
> header/source source groups.
@list,
I'm a new cmake user with a history in using qmake. The following seems
a FAQ to me, but I'm still unable to find a solution:
I have a 100 KLOC project here, splitted in some static libs and a single
executable.
Simplified source tree:
./lib_0
|
|- basic
|- gui
|- other_stuff_enc
