subsequently you'll have to call make
> to build the project - make help will get you a listing of all targets CMake
> created for you. Or in yet other words: the two lines of code you wrote will
> never, ever, build anything. It will only create Makefiles.)
>
> Since you a
ect structure.
>
> Andreas
>
> Am 17.06.2011 11:06, schrieb David Springate:
>
> Hi,
>
> Thanks for the reply - but I think you might have misunderstood my
> question.
>
> I want to setup CMake so that when I call Cmake like so (for MY_APP):
> mkdir build &&
dard' machinery for building a list of
> 'sub-packages' using CMake. It's not well documented and probably still has
> many issues, but I could mail it to you if you think it may help you get
> started and if you're interested.
>
> Greetsz,
> Jakob
>
Hi,
I am new to CMake - and whilst I am immediately impressed with it's relative
ease of use - I have a 'noob' question, I'm sure!
I have the following:
A library called MY_LIB that builds with a cmake command (I have created a
nice CMakeLists.txt file)
An application called MY_APP that builds a
