On Wednesday 08 December 2010, Klaim wrote:
Thanks! I'll try this solution.
By the way is there a way to list all projects found recursively in a
folder?
Didn't follow the thread closely, but did you have a look at the
FeatureSummary.cmake macro ?
It can tell you which packages have been
Didn't know about that, thanks for pointing it. I'll take a look at it.
2010/12/12 Alexander Neundorf a.neundorf-w...@gmx.net
On Wednesday 08 December 2010, Klaim wrote:
Thanks! I'll try this solution.
By the way is there a way to list all projects found recursively in a
folder?
On 7-12-2010 at 11:59, in message
aanlktimssr9mqjgkhkz9xdtgh=1b9vsu1utlb90vb...@mail.gmail.com, Klaim
mjkl...@gmail.com wrote:
I would try to start with just one (base-)project, try to get
everything in place and building the way you want it. If you're new
to
CMake, that's really the way to
Thanks! I'll try this solution.
By the way is there a way to list all projects found recursively in a
folder?
On Wed, Dec 8, 2010 at 10:20, Marcel Loose lo...@astron.nl wrote:
information about XXX availabe to CMak
___
Powered by www.kitware.com
On 8-12-2010 at 11:41, in message
aanlktike_bxnege96vtpzinyv6scwvjwtg+un74vn...@mail.gmail.com, Klaim
mjkl...@gmail.com wrote:
Thanks! I'll try this solution.
By the way is there a way to list all projects found recursively in
a
folder?
Not that I know of.
You can of course do a grep, but
Yeah I was meaning in the context of a CMake script. I don't understand what
makes, for example, the CLang project generate different projects in the
solution folder depending on the project folder content in LLVM repo? Or
maybe it's automatic because Cmake will scan all the subfolders of folders
Sorry, a part of my sentence got cut :
I don't understand what makes, for example, the CLang project generate
different projects in the Visual Studio solution generated depending on the
project folder content in LLVM repo. Or maybe it's automatic because Cmake
will scan all the subfolders of
Sorry,
I really wouldn't know, I do development on Linux. My knowledge of MS
Visual Studio is negligible.
On a general note, though, CMake uses a so-called generator to generate
the Visual Studio project files, as it can also generate Unix Makefiles,
or KDevelop project files.
Maybe you should
Every project(...) command in a CMakeLists.txt file (we expect at
most one in any given CMakeLists.txt file) results in a *.sln file
being generated for use with Visual Studio.
Every add_library(...), add_executable(...) and add_custom_target(...)
results in a *.vcproj or *.vcxproj file being
Thanks it's more clear.
From what I read in the documentation, if I have a tools directory with
one directory by tool project, I'll need to add_subdirectory() for each tool
project, right?
I'll try to us that in my main repo that have to know the projects anyway.
On Wed, Dec 8, 2010 at 17:20,
Hi Klaim,
I would try to start with just one (base-)project, try to get
everything in place and building the way you want it. If you're new to
CMake, that's really the way to go. Once you have this base-project
ready, you can think of starting a second project, using the
base-project as
I would try to start with just one (base-)project, try to get
everything in place and building the way you want it. If you're new to
CMake, that's really the way to go. Once you have this base-project
ready, you can think of starting a second project, using the
base-project as
By the way, I'm using a set of test projects to play with CMake and
understand clearly how it works, so I can experiment.
On Tue, Dec 7, 2010 at 11:59, Klaim mjkl...@gmail.com wrote:
I would try to start with just one (base-)project, try to get
everything in place and building the way you
Hi Klaim,
It's a bit clearer to me now ;-)
Reading between the lines I get the feeling that you're probably better
off using just a single project anyway.
A developer doesn't need to continuously update the whole project when
working on his subproject. Building the whole thing once in his
It's a bit clearer to me now ;-)
Reading between the lines I get the feeling that you're probably better
off using just a single project anyway.
A developer doesn't need to continuously update the whole project when
working on his subproject. Building the whole thing once in his working
On 2-12-2010 at 16:12, in message
aanlktimju5wav=ekxnbmkplnl7dn_c+xssgkoefm5...@mail.gmail.com, Klaim
mjkl...@gmail.com wrote:
Hi!
I'm currently trying to understand how to use CMake for a non-trivial
setup
of multiple-projects-framework. I'm a beginner at CMake (as developer
I
mean, not
Thanks for pointing EXTERNAL_PROJECT , I've looked at it but can't
understand how to get the path from outside.
I'll try again see if I missed something about this feature and get back to
you.
The projects are almost all independent and I need to allow working with a
clone of one subproject
Hi!
I'm currently trying to understand how to use CMake for a non-trivial setup
of multiple-projects-framework. I'm a beginner at CMake (as developer I
mean, not as library user).
I've read the docs and I tried to read the Ogre project CMake organization
but it's a bit overkill for my project I
18 matches
Mail list logo
