Re: [CMake] How to support separate debug and release build directories?

2019-07-13 Thread Marc Herbert
> > >> I am not finding it easy to find 'patterns' for these sort of issues. I >> would have thought that configuring a project with separate debug and >> release directories would be quite typical. But it's hard to find the >> recommended way of doing such things. >> > > It is typical: > https://

Re: [CMake] How to support separate debug and release build directories?

2019-07-13 Thread Marc Herbert
Le ven. 21 juin 2019 à 11:40, Michael Jackson a écrit : > > cd Foo > >mkdir Debug && cd Debug > >cmake -DCMAKE_BUILD_TYPE=Debug ../ > >make -j > > > > We have just created a Debug build in the Debug Directory. Now, the same > is analogous for the Release build. > > > > Cd Foo > > Mk

Re: [CMake] how to set current source directory relative to external project

2019-07-13 Thread Marc Herbert
Le mar. 9 juil. 2019 à 13:24, hex a écrit : > Now that I look at it it seems very obvious. I still have doubts, though: > > I guess I am seeing the contents of a build directory as somewhat > volatile. For most files I want that, to either clean the project or > override the files. > > But what a

Re: [CMake] Better way than: SET(CMAKE_C_ARCHIVE_CREATE " my_flags ... ?

2019-07-13 Thread Marc Herbert
> Additional issue with this CMAKE_C_ARCHIVE_CREATE hack: it's ignored and > reverts back to the default in link.txt when building a "pure assembly" > library without any .c file. Adding an empty.c file works around the problem > Much better than adding an empty .c file: CMAKE_ASM_ARCHIVE_CREATE (

Re: [CMake] In add_subdirectory( binary_dir), binary_dir/ is just a decoy when there's no sub-target

2019-07-13 Thread Marc Herbert
Filed new bug https://gitlab.kitware.com/cmake/cmake/issues/19475 Le jeu. 13 juin 2019 à 11:06, Marc Herbert a écrit : > Ping? > > I'd like to file a bug but I don't know what is the intended behavior: > 1. Should binary_dir work even when no target? > 2. Should CMake warn/error that binary_dir