On 7/15/2010 5:40 PM, John Cary wrote:
Is there some way in cmake to get the
auxiliary fortran link libraries? The
ones that one needs to link in if one is
building a C/C++ executable that uses a library
that was created with fortran?
Like libgfortran for gcc?
Thanks...John Cary
See Modules/
On 7/15/2010 6:05 PM, Tyler Roscoe wrote:
On Thu, Jul 15, 2010 at 03:39:20PM -0500, "Jörg F. Unger" wrote:
I'm using cmake to add a test environment to our project (with ctest).
Is there a possibility to generate to groups of test with different tags
in the makefile, so that after the generati
On Thu, Jul 15, 2010 at 03:39:20PM -0500, "Jörg F. Unger" wrote:
> I'm using cmake to add a test environment to our project (with ctest).
> Is there a possibility to generate to groups of test with different tags
> in the makefile, so that after the generation of the makefiles the user
> mig
Is there some way in cmake to get the
auxiliary fortran link libraries? The
ones that one needs to link in if one is
building a C/C++ executable that uses a library
that was created with fortran?
Like libgfortran for gcc?
Thanks...John Cary
___
Powe
I'm using cmake to add a test environment to our project (with ctest).
Is there a possibility to generate to groups of test with different tags
in the makefile, so that after the generation of the makefiles the user
might say
make test or make extensiveTest?
Thanks
JFU
--
**
On 15. Jul, 2010, at 19:14 , michael.schm...@l-3com.com wrote:
>> Did you enable the -includeall option? If so, that might be the problem
>> here. Try removing it, I just copied it from the FAQ.
>>
>> Michael
>
> For someone new to cmake, that option seems non-intuitive. Is there
> documentati
Hello,
I'm using CMake to build a Mac OS X app, generating an Xcode project. I have
two targets, say "projApp" and "projLib". I'd like for them to be built in
such a way that projLib's output is installed in a subdirectory of projApp's
output folder. I tried this:
set_target_properties(projApp PR
On 7/15/2010 12:07 PM, Verweij, Arjen wrote:
Hi Bill,
I don't think we ended up with those flags after installing the intel
compiler for the dashboard we run at Kitware. Are you sure that came
from the installer?
Not really. I wasn't around when that system was set up.
I tried from cmd.exe,
>Did you enable the -includeall option? If so, that might be the problem
>here. Try removing it, I just copied it from the FAQ.
>
>Michael
For someone new to cmake, that option seems non-intuitive. Is there
documentation I missed?
-Mike
___
Powered by
>Did you enable the -includeall option? If so, that might be the problem
>here. Try removing it, I just copied it from the FAQ.
>
>Michael
That was it. Thanks for all your help.
-Mike
___
Powered by www.kitware.com
Visit other Kitware open-source proj
On 15. Jul, 2010, at 18:09 , michael.schm...@l-3com.com wrote:
>> Never done it myself, but reading the FAQ and the docs, I'd suggest
>> something like this:
>>
>> find_package(SWIG REQUIRED)
>> include(${SWIG_USE_FILE})
>> find_package(PythonLibs REQUIRED)
>> include_directories(
>> ${CMAKE_CUR
>Never done it myself, but reading the FAQ and the docs, I'd suggest
>something like this:
>
>find_package(SWIG REQUIRED)
>include(${SWIG_USE_FILE})
>find_package(PythonLibs REQUIRED)
>include_directories(
> ${CMAKE_CURRENT_SOURCE_DIR}
> ${PYTHON_INCLUDE_DIRS}
> )
>
>set_source_files_properties(
Hi Bill,
>I don't think we ended up with those flags after installing the intel
>compiler for the dashboard we run at Kitware. Are you sure that came
>from the installer?
Not really. I wasn't around when that system was set up.
I tried from cmd.exe, MKS ksh and cygwin shell to get something wit
On 7/15/2010 4:19 AM, Verweij, Arjen wrote:
Spot on Bill:
C:\Users\madymo\build\CMakeFiles\CMakeTmp>cat CMakeLists.txt
cmake_minimum_required(VERSION 2.8)
PROJECT(CMAKE_TRY_COMPILE Fortran)
SET(CMAKE_VERBOSE_MAKEFILE 1)
SET(CMAKE_Fortran_FLAGS " /w /I:"C:\Program Files\VNI\CTT5.0\include\IA32" /
--snip--
Ah you're on windows, make sure that you deselect the option to
associate the build rule with cu files as this does the wrong thing
when you're compiling the same file multiple times with different
defines.
--end snip--
Can you give me more info on this? I have looked in CMake variables
> Shouldn't this be COMPILE_FLAGS?
http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_dir:COMPILE_DEFINITIONS
Under properties on directories
Preprocessor definitions for compiling a directory's sources.
The COMPILE_DEFINITIONS property may be set to a semicolon-separated list of
processor
Hello everyone,
I'm trying to create an NSIS installer that contains both release and debug
targets. I'm using CMake 2.6 and Visual Studio and the installer always
contains the Build version I select in Visual Studio.
Has anyone any idea how to force the install of both release and debug targe
Spot on Bill:
C:\Users\madymo\build\CMakeFiles\CMakeTmp>cat CMakeLists.txt
cmake_minimum_required(VERSION 2.8)
PROJECT(CMAKE_TRY_COMPILE Fortran)
SET(CMAKE_VERBOSE_MAKEFILE 1)
SET(CMAKE_Fortran_FLAGS " /w /I:"C:\Program Files\VNI\CTT5.0\include\IA32"
/fpe:3 /nologo ${COMPILE_DEFINITIONS}")
INCL
18 matches
Mail list logo
