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
Hi,
I have a library that already has a build setup. On windows it uses .bat
file that invokes VC compiler and builds a lib file. I would like to first
call this bat file during the build process and then use this library in
rest of the CMake project. After a research I think I need 2 things:
- c
On 12 June 2013 01:46, Ansis Māliņš wrote:
> No, it's not necessary, and you don't have to list them. In fact, I didn't
> know you can list them.
It it still necessary if one wants to see headers listed as project files in IDE
like Visual Studio, isn't it?
Or, has anything changed in recent CMak
