[CMake] Organization of larger projects

Hello, list! A bit of background: I am currently working inside a large perforce repository, containing source code for several programs. Some functionality has been separated out into separate directories, e.g., some linear algebra operations, file I/O, etc. Currently, all programs (save for o

Re: [CMake] How about GNU Automatic Variables

On Sat, Nov 29, 2014 at 1:48 AM, Domen Vrankar wrote: > I was curious and I looked a bit further: > http://www.cmake.org/cmake/help/v3.0/command/add_library.html has a > OBJECT target that perhaps you could use instead of static library. > > referencing objects is kinda messy, was actually cleane

Re: [CMake] How about GNU Automatic Variables

On Sat, Nov 29, 2014 at 12:27 AM, Zhang Xianyi wrote: > Hi Decker, > > Thank you for the answer. > > If I want to debug test_double, the debugger will refer to > ${CMAKE_BINARY_DIR}/test_double.c. > I am not sure it is appropriate to debug a generated file. > > it's as valid as any other source f

Re: [CMake] 3.1 can't link my MinGW executables any more.

On 29/11/2014 11:58, Bill Somerville wrote: Hi, I have just tried 3.1.0-rc2 and my executable links are failing because all the link libraries are not being added. I use: add_executable (jt65code lib/jt65code.f90 wsjtx.rc) target_link_libraries (jt65code wsjt) where wsjt is a static library

[CMake] 3.1 can't link my MinGW executables any more.

Hi, I have just tried 3.1.0-rc2 and my executable links are failing because all the link libraries are not being added. I use: add_executable (jt65code lib/jt65code.f90 wsjtx.rc) target_link_libraries (jt65code wsjt) where wsjt is a static library target with Fortran and C functions. This n

Re: [CMake] How about GNU Automatic Variables

I was curious and I looked a bit further: http://www.cmake.org/cmake/help/v3.0/command/add_library.html has a OBJECT target that perhaps you could use instead of static library. http://www.cmake.org/cmake/help/v3.0/command/set_property.html also has a SOURCE option that I haven't mentioned before

Re: [CMake] How about GNU Automatic Variables

Hi, I haven't tested this but I think you could write something like this: add_library(test_single test.c) set_property( TARGET test_single PROPERTY COMPILE_DEFINITIONS DOUBLE=some_val ) add_library(test_double test.c) set_property( TARGET test_double PROPERTY COMPILE_DEFINITIONS DOUB

Re: [CMake] How about GNU Automatic Variables

Hi Decker, Thank you for the answer. If I want to debug test_double, the debugger will refer to ${CMAKE_BINARY_DIR}/test_double.c. I am not sure it is appropriate to debug a generated file. Xianyi 2014-11-28 23:03 GMT+08:00 J Decker : > > > On Fri, Nov 28, 2014 at 1:29 AM, Zhang Xianyi > wro