[CMake] Enabling Fortran only builds with Cmake 3.10.2 on Windows

2018-03-23 Thread Belcourt, Kenneth
Hi, I have a project that builds fine on Mac and Linux by disabling C/C++ and building with only Fortran. PROJECT(Noel LANGUAGES Fortran) When I try to build on Windows, it seems that CMake is looking for variable VCTargetsPath, here’s the error: Setting environment for using Microsoft

[CMake] execute_process appending redirected output

2011-12-27 Thread Belcourt, Kenneth
Hi, I'm trying to get CMake to execute this command INSTALL(CODE EXECUTE_PROCESS (COMMAND cat \${CMAKE_CURRENT_SOURCE_DIR}/onejar_classpath.txt ${CMAKE_INSTALL_PREFIX}/onejar/boot-manifest.mf\) ) but this doesn't work, here's the error I get when I run the install. cat:

[CMake] CMake make test feature?

2011-03-31 Thread Belcourt, Kenneth
Hi, This is probably old news but is there some reason why I can build my code in parallel with make -j8, for example, but trying to run the tests in parallel with make -j8 tests ignores the -j option. I've resorted to invoking ctest with -j8 which works fine. Any way to normalize the

Re: [CMake] CMake make test feature?

2011-03-31 Thread Belcourt, Kenneth
On Mar 31, 2011, at 4:43 PM, Nicolas Desprès wrote: On Fri, Apr 1, 2011 at 12:22 AM, Belcourt, Kenneth kbe...@sandia.gov wrote: This is probably old news but is there some reason why I can build my code in parallel with make -j8, for example, but trying to run the tests in parallel

Re: [CMake] File remove_recurse doesn't on OSX

2011-03-16 Thread Belcourt, Kenneth
On Mar 16, 2011, at 11:57 AM, Belcourt, Kenneth wrote: On Mar 16, 2011, at 11:46 AM, David Cole wrote: On Wed, Mar 16, 2011 at 1:40 PM, Belcourt, Kenneth kbe...@sandia.gov wrote: Hi, A quick bug report with CMake 2.8.4 on OSX 10.5.8 built with Intel 11.0.064. This command works fine

[CMake] Test properties

2011-03-15 Thread Belcourt, Kenneth
Hi, Another add_test() question. I reuse the same test directory because I run both Fortran and C executables on the same test and the input files are so large that I don't want to replicate the entire test hierarchy. The problem is that I need to remove files both before I run the

[CMake] add_test WORKING_DIRECTORY option

2011-03-14 Thread Belcourt, Kenneth
Hi, The documentation states that the add_test() WORKING_DIRECTORY option will run the test in the given directory. This add_test rule in my CMakeLists.txt file: add_test( NAME bwr_melgen WORKING_DIRECTORY ${Bwr_Dir} COMMAND melgen.x ${Bwr_Dir}/_BWR_v2-0.inp ) with ${Bwr_Dir} ==

Re: [CMake] add_test WORKING_DIRECTORY option

2011-03-14 Thread Belcourt, Kenneth
Hi David, On Mar 14, 2011, at 3:34 PM, David Cole wrote: What is the cwd when your test starts? The directory where the executable runs from (/scratch/trunk/tools), not the directory containing the test input. It should be ${Bwr_Dir} according to your email's WORKING_DIRECTORY arg.

Re: [CMake] add_test WORKING_DIRECTORY option

2011-03-14 Thread Belcourt, Kenneth
On Mar 14, 2011, at 4:19 PM, Belcourt, Kenneth wrote: Hi David, Oops, busted. The modules I loaded inserted an older version of CMake, v2.8.1. When I run with my local copy of CMake 2.8.4, the error goes away. Sorry about the noise. -- Noel

[CMake] Recompiling source file multiple times

2010-10-11 Thread Belcourt, Kenneth
Hi, I did a quick scan looking for this but didn't see this mentioned in the FAQ. Is there a documented process for compiling a single source file multiple times? For example, the UMFPACK library need to compile most source files at least twice with a different set of defined macros for

Re: [CMake] Always compile source file in debug

2010-09-03 Thread Belcourt, Kenneth
On Sep 3, 2010, at 5:07 AM, Eric Noulard wrote: 2010/9/3 Belcourt, Kenneth kbe...@sandia.gov: Apologies if this has been answered before. In an effort to ensure cross-platform consistent results, I need to force some (C++ and Fortran) source files to always be built debug. Is there any

Re: [CMake] Always compile source file in debug

2010-09-03 Thread Belcourt, Kenneth
On Sep 3, 2010, at 7:51 AM, Michael Hertling wrote: On 09/03/2010 01:07 PM, Eric Noulard wrote: 2010/9/3 Belcourt, Kenneth kbe...@sandia.gov: Hi, Apologies if this has been answered before. In an effort to ensure cross-platform consistent results, I need to force some (C++ and Fortran

Re: [CMake] Always compile source file in debug

2010-09-03 Thread Belcourt, Kenneth
On Sep 3, 2010, at 6:30 PM, Michael Hertling wrote: On 09/03/2010 04:13 PM, Belcourt, Kenneth wrote: On Sep 3, 2010, at 5:07 AM, Eric Noulard wrote: Curious to know, Why do you want to some files files to always be built debug in the first place? For example, certain Lapack routines like

[CMake] Always compile source file in debug

2010-09-02 Thread Belcourt, Kenneth
Hi, Apologies if this has been answered before. In an effort to ensure cross-platform consistent results, I need to force some (C++ and Fortran) source files to always be built debug. Is there any easy syntax to do this? I build our libraries like this. SET(SRCS

[CMake] Link multi-language applications

2009-10-08 Thread Belcourt, Kenneth
Hi, I'm using the Intel 11.1 toolchain with a C++ main program, but need to link in the Intel Fortran libraries as well. Is there a CMake built-in way to do this or do I have to explicitly add the Intel Fortran libraries to, for example, the CMAKE_EXE_LINKER_FLAGS? Thanks. -- Noel