Sorry, David Cole pointed out that I miswrote (and have very poor english to
begin with). Sorry. What I meant to say was that we put the generated cmake
files in the _source_ tree. Text in full:
As a counter example (which perhaps could be improved on), we are currently
putting our generated cm
As a counter example (which perhaps could be improved on), we are currently
putting our generated cmake files in the build tree. The reason for this to
allow git post-checkout and post-rewrite hooks to updating the build files if
needed. We have python script that rewrites the files if they wou
It's nice when everyone agrees.
thanks
On Wed, Jun 12, 2013 at 2:49 PM, Matthew Woehlke <
matthew.woeh...@kitware.com> wrote:
> On 2013-06-12 15:30, William McKenzie wrote:
>
>> Just wondering what the common convention is here. If I have some
>> generated
>> c/c++ source files, say from gSoap
On Wed, Jun 12, 2013 at 2:30 PM, William McKenzie
wrote:
> Just wondering what the common convention is here. If I have some
> generated c/c++ source files, say from gSoap or Lex/Yacc (and my build
> rules take care of the generation), is the convention to generate these
> into the build folder,
Build directory. Every time. No exceptions.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/
Just wondering what the common convention is here. If I have some generated
c/c++ source files, say from gSoap or Lex/Yacc (and my build rules take
care of the generation), is the convention to generate these into the build
folder, or the original source folder? I understand I could use either, and
