Re: [CMake] [CMake ] Specify linker for a mixed language Fortran/C++ application (linux)

On 06/27/2011 02:39 PM, Raphael Münster wrote: > # name of the project > PROJECT(Q2P1) > > enable_language (Fortran) Languages can also be specified in the project command: project(Q2P1 C CXX Fortran) > I invoke cmake like this "CC=mpicc CXX=mpic++ cmake > -DCMAKE_Fortran_COMPILER=mpif90" F

Re: [CMake] [ryppl-dev] Re: $<> expressions in include_directories command

On 07/25/2011 07:56 AM, Dave Abrahams wrote: > > on Mon Jul 25 2011, Daniel Pfeifer wrote: > >> Hey, >> >> is there an update on this topic? > > Well, I asked > > "Does cmake use response files when generating command-lines for windows > compilers that support them?" > > to which there wa

Re: [CMake] $<> expressions in include_directories command

On 07/13/2011 12:10 PM, Alexander Neundorf wrote: > When I talked last time with Brad such a feature was still on his TODO, and > is > there since at least 2007 already, but still more or less at the bottom of > the > list. It's more of a "wish I had time to do this" ;) > add_library(foo ${fo

Re: [CMake] [ryppl-dev] Re: $<> expressions in include_directories command

On 07/25/2011 12:00 PM, Daniel Pfeifer wrote: > what is your opinion on the $<> syntax I originally proposed? > This would not require creating virtual targets for header only libraries. The implementation is just doing delayed variable evaluation and is not a true generator expression in the same

Re: [CMake] [ryppl-dev] Re: $<> expressions in include_directories command

On 07/25/2011 03:11 PM, Dave Abrahams wrote: >> Yes, CMake does support response file generation in a few cases. >> It uses them to pass long object file lists to linkers. Since >> CMake 2.8.5 it also uses them for include directory lists with >> GNU tools on Windows. > > That makes it sound like

Re: [CMake] [ryppl-dev] Re: $<> expressions in include_directories command

On 07/25/2011 02:17 PM, Daniel Pfeifer wrote: > Does it also handle circular dependencies? Since we were doing the module breakdown ourselves we could define modules to avoid circular dependencies. We separated implementation dependencies from test dependencies so that library and test modules co

Re: [CMake] [ryppl-dev] Re: $<> expressions in include_directories command

On 07/25/2011 11:01 PM, Dave Abrahams wrote: > on Mon Jul 25 2011, Brad King wrote: >>> That makes it sound like it's not going to help us with long include >>> directory lists with non-GNU tools. Is that right? >> >> When generating VS IDE project file

Re: [CMake] How to installing cmake Config.cmake files under Debian multiarch ?

On 8/3/2011 11:41 AM, Alexander Neundorf wrote: On Tuesday 02 August 2011, Hendrik Sattler wrote: If you use cmake 2.8.5, you can use GNUInstalldirs.cmake and let the user specify the multiarch directory to install in (or solve it once in that cmake module). You mean having the user adjust the

Re: [CMake] How to installing cmake Config.cmake files under Debian multiarch ?

On 8/3/2011 1:19 PM, Alexander Neundorf wrote: Is there already a variable which contains the multiarch triplet, so I can do something like lib/${CMAKE_MULTIARCH_TRIPLET}/... ? Yes, "CMAKE_LIBRARY_ARCHITECTURE". It contains no slashes and is empty if there is no architecture choice. Slightly

Re: [CMake] Bug in cmake 2.8.4/5 when using IMPORTED static targets?

On 7/21/2011 1:07 PM, Marco Corvo wrote: Hi all, I'm trying to use a new feature of releases 2.8.4/5, that is the possibility > to define dependencies for IMPORTED targets and when I run cmake I get a > SIGSEV signal. Trying to get some more info with Valgrind I found that: I can reproduce thi

Re: [CMake] Bug in cmake 2.8.4/5 when using IMPORTED static targets?

On 8/4/2011 3:29 PM, Brad King wrote: This was a dumb mistake on my part. I will fix it. Meanwhile you can avoid the crash by not making an imported target depend on a target that does not exist. Fixed to ignore dangling dependencies instead of crashing: http://cmake.org/gitweb?p=cmake.git

Re: [CMake] cmake-2.8.4 on HP-UX runpath issues

On 9/25/2011 8:54 PM, Albert Chin wrote: It is listed as "static" because cmake always uses a path/to/libmodman.sl when invoking the linker. CMake prior to 2.6 always used the -L and -l split. That led to endless problems with search path ordering, static v. shared searches, etc. that made it

Re: [CMake] Dependent variable definitions disappear in fortran module files

On 9/30/2011 1:15 PM, John R. Cary wrote: When I build the definitions from the dependency are missing from the .mod file: [snip] So something later in the cmake build seems to be removing these definitions. Perhaps another target compiles the/a source file producing the same .mod file but wi

Re: [CMake] CMake still broken post-2.8.1

On 10/25/2011 5:00 AM, Eric Noulard wrote: 2011/10/25 Phil Smith: # Specify the cross-compilers SET(CMAKE_C_COMPILER "regina.exe" "cc.rex dcc.exe") SET(CMAKE_CXX_COMPILER "regina.exe" "cc.rex dcxx.exe") I think CMAKE_[C|CXX]_COMPILER vars are supposed to contain a command not command + list

Re: [CMake] OS X Frameworks with spaces in filename

On 10/21/2011 7:32 PM, Adam Somers wrote: Sorry if this is not the correct list to post questions. > Please direct me to the proper place if so. This is the correct place. The resulting linker flag is: -Framework My Framework This of course is incorrect and will cause gcc to try to link >

Re: [CMake] [PATCH] KWSys: Correctly handle empty environment variables

On 12/15/2011 2:56 PM, Vladimir Panteleev wrote: This patch fixes a crash which occurs when SystemTools::GetPath attempts to process an empty environment variable. Applied, thanks: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c544545c FYI, the reason you don't show up as an author is

Re: [CMake] linking mixed language executable; cmake choosing wrong compiler

On 1/9/2012 3:44 PM, Mitchell, John A wrote: add_executable(demo_cf_pointer demo_cf_pointer.F90) target_link_libraries(demo_cf_pointer I_Fortran -lstdc++) CMake prefers to use the C++ compiler to link when any C++ is involved. Some toolchains use a "prelinker" step that actually runs the C++ co

Re: [CMake] CMake still broken post-2.8.1

On 1/3/2012 1:29 PM, Phil Smith wrote: If I comment out line 29 in CMakeDetermineCompilerId.cmake, it works with my old toolchain file [snip] So -- why are semicolons being inserted? The change was discussed here: http://www.cmake.org/pipermail/cmake/2010-March/035810.html http://www.cmak

Re: [CMake] CMake still broken post-2.8.1

On October 24, 2011 6:08 PM Bill Hoffman wrote: > So, right at the end it is doing this: > > C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake(96): > EXECUTE_PROCESS(COMMAND ${CMAKE_${lang}_COMPILER} ${CMAKE_${lang}_COMPILER_ID_ARG1} > ${CMAKE_${lang}_COM

Re: [CMake] CMake still broken post-2.8.1

On 1/20/2012 4:37 PM, Phil Smith wrote: I'm confused because neither of your examples has the semicolon, I was asking which one you need, so neither option has semicolons. > but what we need is: "regina.exe" "cc.rex" "dcc.exe" "CMakeCCompilerId.c" Okay. But it sounds like you're saying

Re: [CMake] CMake still broken post-2.8.1

On 1/21/2012 12:24 PM, Phil Smith wrote: > GOOD > C:/Program Files/Regina/regina.exe cc.rex dcc.exe CMakeCCompilerId.c > -- arg=[C:/Program Files/Regina/regina.exe] > -- arg=[cc.rex dcc.exe] > -- arg=[CMakeCCompilerId.c] [snip] > BAD > c:/Program Files/Regina/regina.exe cc.rex;dcc.exe

Re: [CMake] CMake still broken post-2.8.1

On 1/25/2012 9:06 AM, Phil Smith wrote: Just to be clear: that doesn't mean CMake is right -- it's not passing all > the arguments it should. How to move this forward? IMO the change to CMake that exposed this was correct. The ARG1 has always been a literal string placed in command shells afte

Re: [CMake] CMake still broken post-2.8.1

On 1/25/2012 10:53 AM, Phil Smith wrote: We've also provided other approaches elsewhere in this thread to avoid the problem altogether by setting up your toolchain file to skip compiler id detection. OK, I'm willing to do that, but I can't figure out how to do so. Actually the previous discus

Re: [CMake] CMake still broken post-2.8.1

On 1/25/2012 1:50 PM, Phil Smith wrote: Ok, that *maybe* gets me further. CMakeDetermineASM_DIGNUSCompiler.cmake (in Modules\) is: SET(ASM_DIALECT _DIGNUS) SET(CMAKE_ASM${ASM_DIALECT}_COMPILER_INIT "asmit.bat") INCLUDE(CMakeDetermineASMCompiler) SET(ASM_DIALECT) and that gets invoked several t

Re: [CMake] Adding a generated file as a dependency to a target

On 1/27/2012 12:41 PM, Schuchard, Matthew wrote: Contrary to the CMake FAQ, but consistent with what I have been > reading elsewhere, it does not seem possible for me with CMake 2.8.6 > to add a generated file as a dependency to a target I have done something similar to the following: add_cus

Re: [CMake] 'Parallel' CMakeLists.txt?

On 1/28/2012 11:36 AM, g...@novadsp.com wrote: Is it possible to get CMake to process/search for an alternative > default filename to CMakeLists.txt? Not currently. We're not fundamentally opposed to the idea, but it may be tricky to get the interface right. Should the alternate name be used

Re: [CMake] 'Parallel' CMakeLists.txt?

On 1/31/2012 10:55 AM, Nicolas Desprès wrote: All these considerations are important but maybe we could just do first the easy path which is: add a -f option which change the default name every where, for all sub-directories, try_compile, etc... I'm willing to entertain patches but I really thi

Re: [CMake] 'Parallel' CMakeLists.txt?

On 1/31/2012 11:00 AM, Brad King wrote: On 1/31/2012 10:55 AM, Nicolas Desprès wrote: All these considerations are important but maybe we could just do first the easy path which is: add a -f option which change the default name every where, for all sub-directories, try_compile, etc... I&#

Re: [CMake] ICC + Windows

On 2/1/2012 2:05 PM, Roland Schulz wrote: what is the recommended Generator to compile on Windows with ICC on the shell? If I try to use the Visual Studio 2010 (or 2008) generator There is an open issue tracker entry requesting direct .icproj file generation: http://www.cmake.org/Bug/view.p

Re: [CMake] ansi color

On 2/10/2012 3:15 AM, Matt Fair wrote: I'd like to be able to pipe cmake output and still have the ansi color codes when the output is not TTY, is there a way to do this? Not currently. The "isatty" test is hard-coded here: http://cmake.org/gitweb?p=cmake.git;a=blob;f=Source/kwsys/Terminal

Re: [CMake] #include and fortran dependencies

On 2/28/2012 11:06 AM, Dirk vanMeeuwen wrote: #include "fpp-Windows-definition.inc" MODULE MSG ... END MODULE However, when this module MSG is used, the project build order > generated by CMake is not correct (see attached small example). Fortran dependencies are supported, and the Intel Fortr

Re: [CMake] Fortran 90 Module Issues in CMake

On 3/1/2012 11:21 AM, Matthew Schuchard wrote: In particular, I have noticed that CMake cannot do module dependency scanning outside of the current directory/subdirectories. For example, if /topdir/dir1/src/ has a Fortran file with a dependency on a module built in /topdir/dir2/mod/, CMake wil

Re: [CMake] Fortran 90 Module Issues in CMake

On 3/1/2012 2:38 PM, Matthew Schuchard wrote: I did see those links on the bug report for Fortran 90 module dependency in subdirectories, but I am having some kind of XML schema error preventing me from viewing them in Firefox. To what bug report do you refer, and to what links? If I unders

Re: [CMake] Fortran 90 Module Issues in CMake

On 3/1/2012 3:50 PM, Matthew Schuchard wrote: I must not understand your example case correctly. Please post a sample source tree tarball to reproduce it with CMakeLists.txt files and the Fortran90 sources. Unfortunately, this software is also proprietary, Perhaps you can construct a mini

Re: [CMake] Fortran 90 Module Issues in CMake

On 3/2/2012 10:28 AM, Matthew Schuchard wrote: That person also had an issue with one Fortran 90 file using a module built by another Fortran 90 file in the same target and directory, and had the same error message from gnumake as I did. His solution was to manually add a dependency since in hi

Re: [CMake] Q: cmExportFileGenerator::GenerateImportedFileCheckLoop

On 3/13/2012 1:10 PM, Alexander Neundorf wrote: One option for cmake 2.8.8 would be, instead of erroring out to consider the package not found. That's a nice use case for the new _FOUND behavior we've discussed. The package configuration file would have to cooperate with the cmake- generated ta

Re: [CMake] CMake 2.8.8-rc1 ready for testing!

On 3/27/2012 6:07 PM, David Cole wrote: On Tue, Mar 27, 2012 at 2:41 PM, Mourad Boufarguine wrote: I'm not sure if this is the right place to give feedback about the rc. I noticed a regression with MSVC 2010 generator. Using this CMake command : add_executable(project header.h header.hpp sourc

Re: [CMake] CMake 2.8.8-rc1 ready for testing!

On 3/28/2012 12:28 PM, Mourad Boufarguine wrote: What about the CMakeLists.txt file ? Oops, I was too focused on the header file part of your report. This should fix it: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=01e979ac Thanks, -Brad -- Powered by www.kitware.com Visit other Ki

Re: [CMake] Building CMake for HP NonStop

On 4/3/2012 2:23 PM, Mike Clapper wrote: > I am trying to bootstrap CMake-2.8.7 to HP NonStop using the OSS > environment. The environment provided by OSS is very similar to Linux > and Unix. The underlying hardware is IA64. Thanks for working on the port. We'll be happy to take fixes upstream

Re: [CMake] granular preprocessor defiitions

On 4/3/2012 9:33 PM, Christoph Anton Mitterer wrote: Actually what I'd prefer most if add_definitions (and perhaps even include_directories) could be set in a per file context[0]. add_definitions is the original interface and uses -D in its syntax for historical reasons. The earliest quick-and

Re: [CMake] Adding support for Absoft Fortran compilers in CMake

On 4/12/2012 4:05 PM, Michael Jackson wrote: Dredging this up from last year because it has become relevant again (for me). Has this effort gone anywhere? Support was added for Absoft on Linux and Mac as of CMake 2.8.5 but I never had time to do Windows support. There has been no nightly testi

Re: [CMake] cmake 32/64 bit

On Mon, Apr 23, 2012 at 4:45 AM, Jörg F. Unger wrote: > Hi everyone, > I'm using windows 7 (64). I'm trying to determine the python installation > using cmake. > The problem is that cmake only exists as a 32 bit application. As a > consequence, it has only access to the 32 bit registry entries (WO

Re: [CMake] Reason of Fortran include directories /config?

On 05/10/2012 03:25 AM, Petr Kmoch wrote: > we're using cmake to generate Intel Fortran .vfproj files and some of > my developers were asking why include directories in the project > always include X and X/ for every directory X specified > via include_directories(). Looking at cmake source code, t

Re: [CMake] Clang + MinGW Linking Issue

On 05/24/2012 12:22 PM, Justin Holewinski wrote: > I narrowed the problem down to Clang not having > Platform/Windows-Clang-{C,CXX}.cmake files. There is an issue tracker entry for this: http://www.cmake.org/Bug/view.php?id=13035 but it is in the backlog waiting for more feedback and a volunt

[CMake] VS 10 compiler selection (was: Clang + MinGW Linking Issue)

On 05/25/2012 08:40 AM, Keith Gardner wrote: > it looks like Visual Studio was using its own compiler even though > I specified a different one with CMake. The VS generator does not support compiler selection. Prior to VS 10 each IDE version only worked with one toolchain version, and that behavio

Re: [CMake] Does FIND_PACKAGE ignore REQUIRED and QUIET in Config mode ?

Alexander Neundorf wrote: > On Friday 05 September 2008, Yann Cointepas wrote: >> 1) Why do I need Foo_FIND_QUIET in FooConfig.cmake ? >> First, I would like to display a message with the Foo version found if >> QUIET is not used. Okay. >> 2) Why do I need Foo_FIND_REQUIRED in FooConfig.cmake ? >

Re: [CMake] Does FIND_PACKAGE ignore REQUIRED and QUIET in Config mode ?

Alexander Neundorf wrote: On Friday 05 September 2008, Brad King wrote: ... Brad, any objections to set these two variables always, also in Config mode ? If not I can do that if you're not faster. It doesn't hurt to have them available. Please send me a proposed patch. See attache

Re: [CMake] Compiler varience?

re is a long term goal of > having a more feature based set of options. Things like > CMAKE_WARN_LEVEL. Brad King might want to comment more on this, but the > short answer is yes, but it is a ways off. I've been wanting to implement something like this for years, but haven't ha

Re: [CMake] creating Config.cmake and the LOCATION property

Server Levent Yilmaz wrote: > > I have an outdated version of "Mastering CMake" book (for CMake version > 2.2). Referring to section 6.7 "Creating a Config.cmake > file", the configure step contains the following: > > GET_TARGET_PROPERTY( GROMIT_LIBRARY Gromit LOCATION ) > > where Gromit is

Re: [CMake] Bug on AIXC in CMake 2.6.1, was "RE: Problem with add_definitions on CMake 2.6.0 RC 6 and RC 8 on AIX"

Dieter Rosch wrote: > I've finally had time to play with this a bit. > > It turns out that in cmake-2.6.1/Modules/Platform/AIX.cmake, the following > line is missing > > SET(CMAKE_C_COMPILE_OBJECT > " -o -c ") That is supposed to be set by default in Modules/CMakeCInformation.cmake: IF

Re: [CMake] Generated file and parallel build.

Óscar Fuentes wrote: > Several libraries depends on a generared header file. For enabling > parallel builds I need to state that dependency, and I do it with > set_source_files_properties. This happens inside a macro: > > macro(add_llvm_library name) > if( LLVM_SOURCE_COMMON_DEPENDS ) > set_

Re: [CMake] [Insight-users] INSTALL(EXPORT)

Luis Ibanez wrote: > If you have got this to work in your local build, please feel free > to commit the changes to ITK. In that way we can test them early > enough before the release of ITK 3.10. [snip] >> Brad for pointing me to this). I'm using CMake 2.6.1 - I THINK its >> supported in 2.4, but

Re: [CMake] [Insight-users] INSTALL(EXPORT)

Rupert Brooks wrote: > Checking this in would > break every test running against a build tree. Not only does this > approach require an install tree, it unfortunately destroys the > ability to link against the build tree. I spent some effort trying to > figure out how to get around this, and i d

Re: [CMake] Specifying (partially) load order of DLLs

Wheeler, Frederick W (GE, Research) wrote: To make sure A.dll is loaded before B.dll we use the following line in CMake ... TARGET_LINK_LIBRARIES( A B ) I'm surprised that works. Consider the case when there really is a dependency. That says that A depends on B, so that B should be loaded

Re: [CMake] unrecognized option - --out-implib

John Giordano wrote: > Hello: > > I have been trying desperately to get CMake to configure my system > with no luck. > > I am hoping someone can help me. > > I have the gcc compiler running as a cross compiler producing code for > a coldfire V2 chip. > > The Netburner company has suppli

Re: [CMake] unnecessary linker options when compiling executables with mingw/gcc

Werner Smekal wrote: > recently I found out (make VERBOSE=1) that when an executable is > compiled with MinGW Makefiles some linker options are in the command > line, which should be in my opinion only necessary for libraries: > > -Wl,--out-implib,libtest.dll.a > -Wl,--major-image-version,0,--mino

Re: [CMake] Using multiple config names in a single project

Karl Wallner wrote: > Under 2.4 everything worked fine setting "CMAKE_BUILD_TYPE" for each > directory. > It should be possible to make 2.6 somehow compatible with 2.4. This is simply a bug in 2.6 created by some refactoring of the install script generator. I've committed a fix to CVS HEAD. We'l

Re: [CMake] Output of ADD_CUSTOM_COMMAND generated multiple times

Alan W. Irwin wrote: > On 2008-10-07 10:22+0200 Martin Apel wrote: > >> Hi all, >> >> I'm experiencing the following problem with ADD_CUSTOM_COMMAND: >> The commands defined for it are executed multiple times, if multiple >> targets depend on it and I run a parallel make afterwards. >> An example

Re: [CMake] Output of ADD_CUSTOM_COMMAND generated multiple times

Martin Apel wrote: > Alan W. Irwin wrote: >> On 2008-10-07 16:09-0400 Brad King wrote: >> >>> Now targets b and c and build in parallel, but neither will build until >>> 'a' is generated. >> Thanks, Brad, for your further explanation and examp

Re: [CMake] MSVC71 problems when upgrading to CMake 2.6.2

Luke Kucalaba wrote: > the strategy we > have used to set the compiler definitions for each build configuration CMake 2.6 provides an explicit feature for this: http://www.cmake.org/Wiki/CMake_2.6_Notes#Preprocessor_Definitions http://www.cmake.org/cmake/help/cmake2.6docs.html#prop_dir:COMPILE_DE

Re: [CMake] MSVC71 problems when upgrading to CMake 2.6.2

Luke Kucalaba wrote: > First problem is that you will still have > build configurations in your MSVC project regardless. There is no way > that I know of to disable generation of build configurations in MSVC. This is just the way the VS IDE works. A basic CMake design principle is to follow the

Re: [CMake] "Command line too long" under Windows

Brad King wrote: > CMake once just listed the object files on the command line in the > makefile, but users hit command line length limits with several hundred > object files. We solved the problem by listing the objects in a > response file. Now it looks like you've hit ano

Re: [CMake] "Command line too long" under Windows

Martin Apel wrote: > I am currently in the process of trying to convert the build system of > our software to CMake. > Unfortunately there is one static library consisting of lots of objects > (about 5700), which has lots of cyclic references, so I cannot easily > split it up. > I can generate this

Re: [CMake] "Command line too long" under Windows

Martin Apel wrote: >> Please try building from CVS HEAD to >> make sure it fixes your problem. > > thanks for your quick fix. I tried it out with both generators and it > works fine! > Will this fix make it into 2.6.3? Yes, I think so. -Brad ___ CMak

Re: [CMake] CTest/CDash and git

Ioan Calin Borcoman wrote: > Hi, > > Are there any plans to support git in CTest/CDash? Yes: http://www.cmake.org/Bug/view.php?id=6994 I've been working on it on and off for a while. I'll update the above entry when something is ready. -Brad ___ C

Re: [CMake] GetLibraryNamesInternal called on imported target

Boudewijn Rempt wrote: Hi, When I run (cvs head) cmake on my kde sources on OSX, I get lots of these errors: CMake Internal Error (please report a bug) in CMakeLists.txt: GetLibraryNamesInternal called on imported target: kparts What is going on? We're tracking it down. This is under di

Re: [CMake] Preserving library order in target_link_libraries(...) command

Bartlett, Roscoe A wrote: Does CMake guarantee that the order of the libraries passed into target_link_libraries(...) is preserved on the actual link line? For example, If I have: target_link_libraries(sometarget lib1 lib2 lib3 ...) does CMake guarantee that the link line will have the

Re: [CMake] IMPORTED_LOCATION

Micha Renner wrote: I have two questions for the listening below. 1. Out-commenting the line #4 results in a linker error LINK : fatal error LNK1104: File "_sLib-NOTFOUND.obj" can't be opened" What is the purpose of this command (line #4)? When one adds a shared library that is built in the p

Re: [CMake] Getting rid of unwanted quotes that CMake inserts into commands

Alan W. Irwin wrote: I have defined the following custom command: add_custom_command( OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/grid_EOS1_2.out COMMAND ${free_eos_test_LOCATION} < ${CMAKE_CURRENT_BINARY_DIR}/grid_EOS1_2.in >& ${CMAKE_CURRENT_BINARY_DIR}/grid_EOS1_2.out DEPENDS ${CMAKE_CURRENT_

Re: [CMake] global variable vs propagation of include_directories

Sowa, Bartlomiej (NSN - PL/Wroclaw) wrote: > It would be ideal, to have a way to propagate and aggregate > include_directories up the add_subdirectory hierarchy. Can you help me > to find a way to do this? You can use global properties as global variables. See the set_property()/get_property() co

Re: [CMake] Getting rid of unwanted quotes that CMake inserts into commands

Alan W. Irwin wrote: > Shouldn't that be up to the user to insert quotes where needed in the > command rather than CMake anticipating their needs (incorrectly in this > case)? Every make's shell requires different escapes. The VERBATIM option was *added* to help users get the same custom command

Re: [CMake] cmake 2.6.3 RC 5

Alexander Neundorf wrote: > Just a small thing: > I'm slowly converting a few of the FindFoo-modules from kdelibs to the new > Config-style. > E.g. for automoc4 our FindAutomoc4.cmake looks (basically) like: > > set(_FIND_QUIETLY ${Automoc4_FIND_QUIETLY}) > find_package(Automoc4 QUIET NO_MODULE)

Re: [CMake] cmake 2.6.3 RC 5

Brad King wrote: Alexander Neundorf wrote: So, I think it would be nice if find_package(NO_MODULE) would restore the FIND_QUIETLY variable to the state it was before (as I'm doing here manually). Good idea. I don't think we make any guarantee either way about the value of thi

Re: [CMake] Search paths for FooConfig.cmake files

Jose Luis Blanco wrote: Hello CMake developers! I've been thinking it would be interesting that CMake could look for FooConfig.cmake package files in some likely paths such as C:\Program Files\Foo-XXX\ . This is for Windows, of course, but perhaps could be extended to /opt/foo-XXX/ in Unix syste

Re: [CMake] LOCATION in VS

Brad Aisa wrote: I am trying to use the LOCATION property of a library target in VS. VS is a bit complicated, because a single generate creates all 4 targets (Debug, Release, etc.) I want to add a custom target command. Here is what is in the file: _targ is a variable that contains a previous

Re: [CMake] Symlink problem under linux for runtime search path generation

Nicolas Desprès wrote: But in this kind of case, cmake could figure out that these two directories are actually the same ? There is code to figure that out but it doesn't seem to be working for some reason. My guess is that the recent change to help find openbsd-style libraries enabled loading

Re: [CMake] Symlink problem under linux for runtime search path generation

Nicolas Desprès wrote: Hi Brad, Sorry for the delayed answer. It was Christmas break :-) I've tried your patch and it works :-) Thank you very much. I think the next step is to open an issue in the bug tracker (I could do it). Or maybe you can directly commit the patch if you have access. Tha

Re: [CMake] Strange problem creating and linking against a static lib

Joachim Ziegler wrote: Joachim Ziegler wrote: I suppose the problem is in the link line, which says: /usr/bin/X11/c++ -fPIC -static "CMakeFiles/startCompletionServer.dir/StartCompletionServer.o" -o startCompletionServer -rdynamic -L/KM/home-0/ziegler/tmp/build -Wl,-Bstatic -lbaselib -Wl,

Re: [CMake] File modification detection based on content (not timestamp)

Robin Vobruba wrote: > We also recently moved from SVN to GIT with our main repository. > Because of the way GIT works, we would like CMake to check for file > modification based on file contents, rather then timestamps. This > would let us use the advantages of GIT to its fullest, save us from > k

Re: [CMake] CMake, Visual studio 2005 and long relative path

Eric Noulard wrote: > 2009/1/8 Julien Michel : >> Dear CMake users and developpers, >> >> My project is using cmake and I am trying to build it on Visual Studio 2005. >> The configuration process is successful, but when trying to compile, I have >> a long bunch of fatal C1083 error : >> >> fatal er

Re: [CMake] History and ideas behind FindMPI.cmake?

Alin M Elena wrote: > Do you really need an module for MPI? > > All you need is to set the normal shell variables for compilers to the MPI > wrappers. > You need both mpi and non-mpi binaries just use different build folders. Alin is correct. If the project works with an all-MPI build you can j

Re: [CMake] Using imported targets with export command

Rodolfo Schulz de Lima wrote: > Rodolfo Schulz de Lima escreveu: >> me. The documentation states that an imported target is visible in the >> current directory and below. What is the rationale for this behaviour? > > After some testing, the documentation is misleading. Actually cmake does > the ri

Re: [CMake] test executable failing only when run in ctest

Matthew Leotta wrote: > I've come across a test on the VXL dashboard that seems to segfault only > on some test machines. > > http://www.cdash.org/CDash/testSummary.php?project=12&name=bvxm_test_apm_processors&date=2009-01-26 > > > One of the failing machines is mine (Mac_OS_X-10.5.6_unix_make).

Re: [CMake] test executable failing only when run in ctest

Matthew Leotta wrote: > Brad, > > Thanks, but I'm not sure if I completely understand your suggestion. > Let me clarify. If I run the test executable > > ./bvxm_test_all > > I get no errors and no segfault. I know how to debug this, but there is > nothing to debug. If in the same directory

Re: [CMake] Will CMP0003 OLD become deprecated?

Adolfo Rodríguez wrote: > I am currently migrating a project to CMake, and have been linking > targets to project libraries using full paths (i.e., embracing the NEW > CMP0003 policy of CMake >= 2.6). However, my co-workers are reluctant to > embrace this because the old CMP0003 policy has not yet

Re: [CMake] test executable failing only when run in ctest

Matthew Leotta wrote: > > On Jan 26, 2009, at 3:04 PM, Brad King wrote: >> add_test(run_xterm xterm) >> >> $ ctest -R run_xterm >> >> Then run gdb and the test inside the xterm to see if it fails. It could >> be an environment difference. >> >

Re: [CMake] Regression between 2.4.8 and 2.6.2 for the macada version of the gcc compiler

Alan W. Irwin wrote: The issue can be illustrated by a simple "hello-world" shared library build test project with SOVERSION and VERSION specified for the library. From "make.out_gcc_macada_2.6.2": -- /usr/local/ada

Re: [CMake] Regression between 2.4.8 and 2.6.2 for the macada version of the gcc compiler

Alexander Neundorf wrote: On Wednesday 28 January 2009, Alan W. Irwin wrote: One of the PLplot developers has been using the macada version of the gcc compiler on Mac OS X for a long time because that version gives him an integrated Ada compiler as well. That compiler worked well for cmake-2.4,

Re: [CMake] Regression between 2.4.8 and 2.6.2 for the macada version of the gcc compiler

Hendrik Sattler wrote: > Martin Costabel schrieb: >> Alan W. Irwin wrote: >> [] >>> Is there a better gcc option then -v to find out the _actual_ linker >>> being >>> used? >> Use -Wl,-v :-) >> >> On 10.4, if you run gcc -dynamiclib, the linking is managed by >> /usr/bin/libtool which in turn calls

Re: [CMake] How to append arbitrary linker options?

Bartlett, Roscoe A wrote: > Hello, > > I would like to be able to append arbitrary linker options to the end of > my link lines on Unix/Linux systems. However, the options set in the > CMAKE_EXE_LINKER_FLAGS variable are listed *before* all of the libraries > that CMake knows about. I need to b

Re: [CMake] How to append arbitrary linker options?

Bartlett, Roscoe A wrote: > The hack: > > set(CMAKE_CXX_LINK_EXECUTABLE >"${CMAKE_CXX_LINK_EXECUTABLE} ${NASTY_FLAGS}") > > does not work because my libraries still come after these flags. Read my suggestion more carefully. I'm not setting CMAKE_EXE_LINKER_FLAGS. I'm setting the variable

Re: [CMake] cmake 2.6.3 RC 11

Alexander Neundorf wrote: On Thursday 05 February 2009, Bill Hoffman wrote: I have a release candidate (RC 11) for 2.6.3 ready for CMake. This should be about the last one. At this point I am only going to fix regressions from previous releases of CMake into 2.6.3, so please try this release.

Re: [CMake] CMAKE_MINIMUM_REQUIRED(VERSION 2.6.0 FATAL_ERROR) and cmake_policy(VERSION 2.6.0) not working correctly for 2.6.2

Alan W. Irwin wrote: On 2009-02-01 09:03-0800 Alan W. Irwin wrote: According to the documentation of 2.6.2, policies CMP0008 and CMP0009 were introduced after 2.6.0. Also, according to that documentation, cmake_policy(VERSION 2.6.0) should set those policies to OLD and warn about that. I us

Re: [CMake] MSVC7.1 static link question

Luigi Calori wrote: Bill Hoffman ha scritto: Philip Lowman wrote: On Mon, Feb 9, 2009 at 12:39 PM, Luigi Calori > wrote: I' m quite a newbie in static linking, I would like to combine two lib into one: say libtiff needs libjpeg and zlib If you gener

Re: [CMake] MSVC7.1 static link question

Philip Lowman wrote: On Tue, Feb 10, 2009 at 1:01 PM, Brad King CMake 2.6 makes it easy to export targets from one project (either its build tree or install tree) for use by another project. Is this the easiest way to register dependencies of IMPORTED static libraries against each

Re: [CMake] warning "safe linker search path"

John Biddiscombe wrote: I get a lot of these warnings (example below), because in /usr/lib64 there are symlinks to the libGL files in /usr/X11R6/lib64 Is there a correct (but still safe) way to make these warnings go away. There are a lot of them (a couple per plugin - so on screen we get tens

Re: [CMake] creating custom make targets

Aaron Turner wrote: Whoops, my bad. Typed "add_custom_target" not "add_custom_command". Thanks everyone, this makes sense now. To answer the original question, the best way to generate a bunch of things only when the users asks is to use add_custom_command to create the rules and then associa

Re: [CMake] EXECUTABLE_OUTPUT_PATH is not just deprecated, it's harmful!

kent williams wrote: So we have a big program (well a couple of them Brains2 and Brains3), and a bunch of 'unbundled' programs (BRAINSFit, BRAINSDemonWarp, BRAINSTracer etc..). We use SVN to add the 'unbundled' programs as subdirectories of our BRAINS svn checkout. So our CMakeLists.txt files i

Re: [CMake] EXECUTABLE_OUTPUT_PATH is not just deprecated, it's harmful!

Philip Lowman wrote: > On Thu, Feb 19, 2009 at 5:25 PM, Brad King <mailto:brad.k...@kitware.com>> wrote: > > AFAIK the word 'deprecated' does not appear in the documentation for > EXECUTABLE_OUTPUT_PATH. It will be around for a long time. We just >

Re: [CMake] problem with add_custom_command / add_custom_target in different directories

Michael Wild wrote: On 25. Feb, 2009, at 7:25, Philip Lowman wrote: When I invoke add_custom_target() in the parent directory it causes an error in the makefiles. To me this appears to be a bug in the Makefile generator. I also tried to make a "untarFoo" custom target in test/CMakeLists.txt, wh

<    1   2   3   4   5   6   7   8   9   10   >