Re: [CMake] conditions and included subprojects

2018-06-11 Thread Andreas Naumann
: "Cornelis Bockemühl" An: "Andreas Naumann" , cmake@cmake.org Betreff: Re: [CMake] conditions and included subprojects Thanks for your proposals!   Actually my problem is basically that I want to keep up with some minimum good practice, but I am seeing myself throwing it o

Re: [CMake] conditions and included subprojects

2018-06-11 Thread Johannes Zarl-Zierl
onsibility of the user to set the option appropriately. > > > > > > > > I think, the second version is the easiest way. > > > > > > > > Regards, > > > > Andreas > > > > > > > > Gesendet: Montag,

Re: [CMake] conditions and included subprojects

2018-06-11 Thread Cornelis Bockemühl
; Regards, > > Andreas > >   > > Gesendet: Montag, 11. Juni 2018 um 10:20 Uhr > > Von: "Cornelis Bockemühl" > > An: cmake@cmake.org > > Betreff: [CMake] conditions and included subprojects > > > Dear CMake users, > > >   &g

Re: [CMake] conditions and included subprojects

2018-06-11 Thread Andreas Naumann
I think, the second version is the easiest way.   Regards, Andreas   Gesendet: Montag, 11. Juni 2018 um 10:20 Uhr Von: "Cornelis Bockemühl" An: cmake@cmake.org Betreff: [CMake] conditions and included subprojects Dear CMake users,   Maybe my question is trivial for most, but still

[CMake] conditions and included subprojects

2018-06-11 Thread Cornelis Bockemühl
Dear CMake users, Maybe my question is trivial for most, but still I do not find an answer on my own! If you have a project and some sub-project (or module or whatever the jargon is) that are both managed with CMake, they should be in separate directories (directory trees), and each of them have