Re: [CMake] custom configuration types and linking with 3rd-party libs

cyril_wobow wrote: Unfortunately, there is a showstopper : when it comes to linking, tell me if I am wrong, there is no way to express which configuration type should link against which library. In particular, all my configuration types end up linking against the release version of my 3rd party

Re: [CMake] custom configuration types and linking with 3rd-party libs

Brad King wrote: Use an IMPORTED library. This is supported in CMake 2.6: add_library(xx_lib STATIC IMPORTED) set_target_properties(xx_lib PROPERTIES IMPORTED_CONFIGURATIONS "DEBUG;RELEASE" IMPORTED_LOCATION_GUIDEBUG ${XX_DEBUG} IMPORTED_LOCATION_GUIRELEASE ${XX_RELEA

Re: [CMake] custom configuration types and linking with 3rd-party libs

Yuri V. Timenkov wrote: > On Tuesday 26 August 2008 03:59:04 Brad King wrote: >> http://www.cmake.org/Wiki/CMake_2.6_Notes#Importing_Targets >> http://www.cmake.org/HTML/cmake-2.6.html#command:add_library >> http://www.cmake.org/HTML/cmake-2.6.html#prop_tgt:IMPORTED_LO

Re: [CMake] custom configuration types and linking with 3rd-party libs

Philip Lowman wrote: > On Mon, Aug 25, 2008 at 9:27 AM, cyril_wobow <[EMAIL PROTECTED] > > wrote: > > Philip Lowman a écrit : > > Does LINK_INTERFACE_LIBRARIES_ do what you want to do? > > See > > http://www.cmake.org/HTML/cmake-2.6.html#pro

Re: [CMake] custom configuration types and linking with 3rd-party libs

Philip Lowman wrote: > Ultimately, TARGET_LINK_LIBRARIES() works just fine the way it is with > the debug/optimized keywords satisfying normal use cases. The > debug/optimized keywords are in the lexicon and they aren't going > anywhere. What is the harm in accepting a patch (if a user submitted

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] Build flags not applied during compiler testing on Ubuntu

On 08/21/2018 03:18 PM, Richard Shaw wrote: > without --specs=nosys.specs applied during compiler testing, cmake fails. How is this flag specified when invoking CMake? > https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1787723 According to that discussion it works on Fedora but not on Ubuntu

Re: [CMake] Build flags not applied during compiler testing on Ubuntu

On 08/22/2018 03:49 PM, Richard Shaw wrote: > Initially I tried setting the flags before invoking "project" and that seemed > to be enough for Fedora. I've tried other things as well that I've probably > forgotten but one other method I tried was: > > set(CMAKE_REQUIRED_DEFINITIONS "--specs=nosys.

Re: [CMake] Build flags not applied during compiler testing on Ubuntu

On 08/22/2018 04:23 PM, Richard Shaw wrote: > Currently I'm using an "include" of the toolchain file prior to calling > "project" since 100% of development happens on a PC instead of having > to pass the CMAKE_TOOLCHAIN_FILE option every time. CMAKE_TOOLCHAIN_FILE must be used in order to be prope

Re: [CMake] Build flags not applied during compiler testing on Ubuntu

On 08/22/2018 04:23 PM, Richard Shaw wrote: > Here's the contents: > > set(CMAKE_EXECUTABLE_SUFFIX_C ".elf") > set(CMAKE_EXECUTABLE_SUFFIX_CXX ".elf") > set(CMAKE_EXECUTABLE_SUFFIX_ASM ".elf") [snip] On 08/22/2018 05:05 PM, Richard Shaw wrote: > One step closer: > ...me forcing the binary output to

Re: [CMake] Build flags not applied during compiler testing on Ubuntu

On 08/25/2018 05:48 PM, Richard Shaw wrote: > set(CMAKE_EXE_LINKER_FLAGS "-T${CMAKE_SOURCE_DIR}/stm32_flash.ld") > > The build dir is the binary directory, not the source directory... Toolchain files cannot reference variables like CMAKE_SOURCE_DIR that depend on the source and build tree locatio

Re: [CMake] LOCATION target property, generator expressions

On 09/26/2018 10:23 AM, Hendrik Greving wrote: > Is there any way before 3.13 to achieve what I need? Right now we > modify LINK_FLAGS based on something that is computed with values > from LOCATION. [snip] > our cmake setup is using LOCATION property for two targets to compute > a relative path fr

Re: [CMake] Relative RPATH for installation (was: LOCATION target property, generator expressions)

On 09/27/2018 08:03 PM, Hendrik Greving wrote: > Thanks. Ok one step back. What we want is to have the same relative path > from binary/executable to linked library in build and install tree > (which we assume is the same for us). Looks like by default, > e.g. cmake 3.9, puts in an absolute path.

Re: [CMake] LOCATION target property, generator expressions

On 10/02/2018 01:12 PM, Hendrik Greving wrote: > By the way, the new generator expression support in 3.13, is this for > LINK_FLAGS or LINK_OPTIONS. LINK_OPTIONS, though it should be used through target_link_options. > And regardless of the former, will it be possible to compute a relative > path

Re: [CMake] find_package Module/Config mode and nontrivial package version checks

On 10/04/2018 02:36 PM, Joachim Wuttke wrote: > What then about user code that ought to check > for version compatibility? Module mode only offers a check > for an EXACT version string, and does not terminate if > that condition is not met [3]. Module mode is only selected if there is a Find.cmake

Re: [CMake] [cmake-developers] [ANNOUNCE] CMake 3.13.0-rc1 is ready for testing

On 10/09/2018 02:00 PM, Rolf Eike Beer wrote: > Seems like you missed one part of the announcement mail ;) > > Policies > == The announcement comes from the release notes, and all policies are mentioned there in relevant bullets. We've never called them out separately in such notes. One can

Re: [CMake] Finding Boost in versioned layout on Linux

On 10/24/2018 01:22 PM, Mateusz Loskot wrote: > So, I had to bend CMake this way to find Boost for me: > > cmake -DBoost_COMPILER=-gcc5 -DCMAKE_CXX_COMPILER_ARCHITECTURE_ID=x64 .. See these issues: https://gitlab.kitware.com/cmake/cmake/issues/17701 https://gitlab.kitware.com/cmake/cmake/issues/

Re: [CMake] [ANNOUNCE] CMake 3.13.0-rc2 is ready for testing

On 10/25/2018 11:10 AM, Mateusz Loskot wrote: > FindBoost.cmake changes seem to be missing from this section We don't record every version update or implementation change in release notes. The interface of the module has not changed. -Brad -- Powered by www.kitware.com Please keep messages on

Re: [CMake] CMake script mode not backward compatible?

On 10/29/2018 04:28 AM, Damien R wrote: > Hi, > > Since cmake 3.10, using cmake in script mode (-P) produce an error with the > following script: > > cmake_minimum_required(VERSION 3.9) > set_directory_properties(PROPERTIES EXCLUDE_FROM_ALL FALSE) > > I did not see something related in the relea

Re: [CMake] building host tools during cross compiliations (was: dependencies of cross compiliations)

On 11/27/18 5:28 AM, Rolf Eike Beer wrote: > Then I came up with: > >add_host_build("relative source dir" "build dir" [VARS]) > > This would create an entirely new CMake scope (with it's own > CMakeCache.txt and the like) in "${CMAKE_CURRENT_BUILD_DIR}/build dir", > and would not take the C

Re: [CMake] cmake + ninja how to use several CPU cores?

On 7/29/19 11:50 AM, Dave Milter wrote: > Only source code are generated, so main.cpp -> main.cpp.o doesn't > depend on anything. > But generated by cmake build.ninja still require link of extern_lib > before starting main.cpp -> main.cpp.o If there are any custom commands in any targets on which

Re: [CMake] cmake + ninja how to use several CPU cores?

On 7/29/19 3:22 PM, Dave Milter wrote: >> Since then all objects in a target can start compiling independently >> so long as that target does not depend on any targets with custom >> commands. See also https://gitlab.kitware.com/cmake/cmake/issues/17097 > Is any way to tell cmake that add_custom_

Re: [CMake] cmake side effects: possible bug

Michael Bell wrote: > All, > > I am running cmake 2.4.3 on solaris. > > In many of my subdirectories, I have commands to copy files to a > release directory and make some of them executable: > ADD_CUSTOM_TARGET(makeExecutable ALL) > FOREACH(file ${SCRIPTS}) >CONFIGURE_FILE(${CMAKE_CURRENT_SOU

Re: [CMake] Re: ADDITIONAL_MAKE_CLEAN_FILES --> FILE(REMOVE ..)

Stephen Adler wrote: > It looks to me like the > double quotes is canceling out glob'ness of *~. [snip] >> FILE(REMOVE >> "core" >> "core*" >> "*~" There is no globbing here. The clean code is a CMake script, not a shell script. The make clean step is meant to clean files specifically created by

Re: [CMake] Re: [out-of-tree] install uses wrong path

Eduard Bloch wrote: > It seems like install_manifest already contains hardcoded absolute > (wrong) directions when created. The workaround was adding an absolete > path based on CMAKE_BINARY_DIR to INSTALL targets: > > SET(BINS_SET mkisofs/mkisofs cdrecord/wodim rscsi/rscsi readcd/readcd > mkisofs

Re: [CMake] cmake side effects: possible bug

Michael Bell wrote: > Ok, it certainly makes sense that running cmake globally would > simplify things, which is a good thing. It does seem to cause a > problem for me that maybe you can help me work around: > > Say I have a several subdirectories, each with C++ code and perl > wrappers to that co

Re: [CMake] cmake side effects: possible bug

Michael Bell wrote: > I have one more issue to deal with. I have been relying on > CONFIGURE_FILE to set some variables as my scripts get copied. How can > I integrate that into this framework? cmake -E copy does not seem to > set the variables. You can instead run "cmake -P somescript.cmake" to c

Re: [CMake] cmake side effects: possible bug

Brad King wrote: > A completely different approach would be to make sure that > myscript.pl.in has execute permission in the source tree. ...and a much simpler way is to not actually make them executable at all but instead use FIND_PACKAGE(Perl) to get the perl executable and then run the

Re: [CMake] Create a project that generate the .dll and the .lib

[EMAIL PROTECTED] wrote: > I try to write a CMakeList.txt file which create a DLL project under Visual > Studio .NET 2003 by using ADD_LIBRARY. > > How do I make my project to generate both the .dll and the .lib ? ADD_LIBRARY(mylib SHARED src1.cxx src2.cxx ...) Make sure the source files use _

Re: [CMake] CONFIGURE_FILE output not cleaned up

Eduard Bloch wrote: > CONFIGURE_FILE is used (see below) to adopt an autoconf-style config > file, however the result is not cleaned up when the clean target is run. > It is not that bad as long as the generated file is not shipped and so > the generation is triggered on users machine, but when som

Re: [CMake] Managing library name decorations

Anders Sundman wrote: > Boost will produce the library files: "libboost_date_time-gcc-mt-s.a" or > "boost_date_time-gcc.lib", or add some other nifty suffix. The > decorations specifying toolset, run-time, etc. that the library was > compiled with. CMake has no formal knowledge of such decorations

Re: [CMake] getting rid of additional quotes in generated vcproj PreprocessorDefines

[EMAIL PROTECTED] wrote: > Is there a way to get rid of the additional " > Given > ADD_DEFINITIONS(-DSN_TARGET_PS3) > Then cmake autogenerates: > PreprocessorDefinitions=","SN_TARGET_PS3"," > I just want: > PreprocessorDefinitions="SN_TARGET_PS3" > > Is there a template that I can

Re: [CMake] [ADD_CUSTOM_COMMAND] How to add source dependences to the target ouside of the command?

Tristan Carel wrote: The module `UseSwig' provided in the version 2.4.3 provides a macro named `SWIG_ADD_MODULE' to define a C/C++ library wrapped for one of the targets supported by Swig. This macro uses the command `ADD_CUSTOM_COMMAND' to define the rule as below: wrapper.cxx: foo.i swig [

Re: [CMake] Using cmake under windows

Yann Renard wrote: > I'm trying to use cmake under windows in order to generate VC8 > makefiles. I have read > http://cmake.org/Wiki/CMake_Generator_Specific_Information chapter about > windows and written down a sript that looks like this : > > set path=d:\yrenard\platform-sdk\bin;%path% > set in

Re: [CMake] custom command question

Doug Henry wrote: > No, since it is a dependency of a source file that is included in the > executable I would expect it to be handled (it was in previous > releases). It seems that cmake does know about it, because it gives an > error with the correct path to the file that needs to be generated.

Re: [CMake] Using cmake under windows

Yann Renard wrote: >> You did not run cmake / cmakesetup from the correct command prompt. >> Therefore your env vars 'LIB' and 'INCLUDE' are not set correct. >> Take a look into your start menu (PlatformSDK -> OpenBuildEnv Window >> -> ...) and don't open your command prompt by executing cmd.exe. >

Re: [CMake] Using cmake under windows

Yann Renard wrote: > Brad King wrote: >> You need to run CMake from the same command prompt in which the >> environment is set. From that same command prompt try: >> >> mkdir myproj-build >> cd myproj-build >> cmake c:/path/to/myproj -G"NMake Makefi

Re: [CMake] Using CMake for cross-compîling?

Eric Noulard wrote: > Let's say I want to cross-compile my Windows application/library > on my Linux box using a cross-gcc (like mingw)? > > Is it possible to indicate to CMake that we will use > a cross compiler? > > In order to avoid (for example) to get a mylib.so file > if we want a mylib.dll

Re: [CMake] Support for Compaq Visual Fortran?

Arjen Markus wrote: > Hello, > > I have trouble getting CMake to recognise Compaq Visual Fortran > as a valid Fortran compiler under Windows. > > Philippe Poilbarbe sent me his configuration module for CVF, but > he also noted that there is another problem - CVF does not like > the default option

Re: [CMake] Avoid overwriting files at installation time

Alexander Neundorf wrote: > Original-Nachricht > Datum: Wed, 30 Aug 2006 12:38:40 +0100 > Von: Marco Canini <[EMAIL PROTECTED]> > An: CMake ML > Betreff: [CMake] Avoid overwriting files at installation time > >> Hi, >> is there a way to not install a file (e.g. config file) is i

Re: [CMake] Avoid overwriting files at installation time

Marco Canini wrote: > Hi, > that's correct. > In this case a config file should be installed only if it doesn't exist > in order to preserve what the user wrote. > But I guess cmake doesn't support it yet. This is what the INSTALL(CODE) or INSTALL(SCRIPT) commands are meant to do: create custom in

Re: [CMake] Deleting a directory

Brandon J. Van Every wrote: > Yann Renard wrote: >> Cheers list, >> >> when using cmake for building my libraries, I add additional commands >> in order to copy all the corresponding header tree to a target >> directory. On clean stage, I would like to remove this tree so removed >> the .h files on

Re: [CMake] cmake license question (Was: CMake Modules)

Joerg Mayer wrote: > cmake itself is 4-clause BSD license (including the advertising clause) > which is incompatible with GPLv2. The CMake license should be free enough to allow you to copy and modify the code and redistribute it under any license you choose as long as the original notice appears.

Re: [CMake] System Include Directories

Yannick Koehler wrote: > Is there a command such as > > INCLUDE_SYSTEM_DIRECTORIES that exists? > > Which would add the directories in CFLAGS such as -isystem DIR for > both C and C++? No. Does such a flag exist on any compilers other than GCC? I think that for GCC if a directory is given with

Re: [CMake] Linking Problems w. CMake 2.4 and MinGW32

[EMAIL PROTECTED] wrote: > although I am aware of the fact that the following issue was already > discussed by some fellows several months ago on this list, no solution was > found there, so I'm just asking this again: > > When generating Makefiles with CMake 2.4 for the MingW environment, the b

Re: [CMake] Regex with character '+'

Xavier Larrode wrote: > Hi all, > i have a regex like this : > SET(GTKMM_LIBDIR_EXTRACT_REGEX "[-][l]([a-zA-Z0-9/._-]*)") > And gtmm is using the lib sigc++-2.0 > So i need to add to my regex the character + . > i tried with \+ ; \\+ '+' but nothing work ... Make sure the "-" is still the last ch

Re: [CMake] CUSTOM COMMANDS with no depends under VS 2003

Luigi Calori wrote: > After several test and trials, I ve the suspect that if one use > ADD_CUSTOM_COMMANDS without DEPENDS, then the generator ->Visual Studio > 7 .NET 2003<-, is not > running the command at build but requires a rebuild. > Am I completely wrong or is a known issue? I happened to

Re: [CMake] Generated VC8 project don't change the library paths

Radu Mihai wrote: > Hello, first time on the list > > I am working on a project that links with some external libs that we > build ourselves (OpenSceneGraph). > To accommodate the use of release and debug versions the current layout > looks like this: > osg/lib.rel/ . > osg/lib.dbg/ . > >

Re: [CMake] Patch to install dlls correctly when cross-compiling

Toni Timonen wrote: > When cross-compiling windows dlls with mingw compiler using linux, the > dlls are not installed to the correct location (and the import library > is not installed at all). It seems that some things about the platform > are fixed at runtime. > > The patch attached fixes this i

Re: [CMake] Adding cross-compiler support to CMake ...

Sean McBride wrote: > I'd just like to mention that the Mac community would dearly love to see > cross-compilation support in cmake. > > Are you familiar with Apple's concept of a "Universal Binary": > CMake 2.4 does support universal binaries on OS

Re: [CMake] ADD_SUBDIRECTORY and EXCLUDE_FROM_ALL

Stephan Tolksdorf wrote: > If a subdirectory is included with EXCLUDE_FROM_ALL, targets in the > subdirectory are listed in the generated Visual Studio solution, but > targets recursively included in subdirectories of the subdirectory are > not. Is this a bug or a feature? (I'm using CMake from CVS

Re: AW: Re: [CMake] Linking Problems w. CMake 2.4 and MinGW32

[EMAIL PROTECTED] wrote: >> ADD_EXECUTABLE(foo foo.cxx) >> TARGET_LINK_LIBRARIES(foo bar.lib) >> >> and I got a "-lbar" on the link line from CMake 2.4.3 with the "MSYS >> Makefiles" and "MinGW Makefiles" generators. > > This example works for me, too. Maybe there's some issue on setting the > LI

Re: [CMake] INCLUDE_DIRECTORIES includes two directories appended together

Ryan Phillips wrote: > I am having a problem when I include INCLUDE_DIRECTORIES(${SOMEVAR}) > within my project. The generated CFLAGS (under linux) include my > CMAKE_SOURCE_DIR appended with my ${SOMEVAR}, ie: > > SOMEVAR="/usr/include/openssl/" > > upon compilation: > -I/home/rphillips/work/pr

Re: [CMake] setting a default build type

Brandon J. Van Every wrote: > On MSVC my CMakeLists.txt generates Debug, Release, MinSizeRel, and > RelWithDebInfo build types. I want to keep all 4 of 'em. I want to > select MinSizeRel as the default build, so that if an end user just > fires up BUILD_ALL and does nothing else, he'll get a MinS

Re: [CMake] setting a default build type

Brandon J. Van Every wrote: > Brad King wrote: >> This would be a nice feature but I don't know how to implement it. Try >> generating a project and then manually editing the project files in such >> a way that the IDE selects a different configuration by default. Don

Re: [CMake] Mailing lists for cvs and bugtracker

Joerg Mayer wrote: > I'd like to follow development of cmake a bit more closely. In order to > do that, many other open source projects have mailing lists that follow > the cvs commit and the bug tracking system. > Is something like that available and just not mentioned on the mailing > lists page

Re: [CMake] Adding cross-compiler support to CMake ...

Michael Casadevall wrote: > I wish to add support for cross-compiling to CMake since its a tool I > use a lot, and I can finally kill the last few of my projects using > autotools. To my knowledge, autotools is the only system that provides > cross-compiling, and poorly at that, and I've been think

Re: [CMake] CMake Modules

frederic heem wrote: > According to cmake template FindPACKAGE.cmake > (http://cmake-modules.googlecode.com/svn/trunk/Templates/FindPACKAGE.cmake) FYI, this is not an official CMake module repository, nor has a CMake developer looked at these modules in detail. > Can someone explain why the incl

Re: [CMake] Fortran 9x dependencies

Warren Turkal wrote: > Is there a way to override the mechanism for finding dependencies? No. > I am trying to work around the crappy support for preprocessed Fortran > dependency generation. See bug #2361 [1]. Unfortunately we do not have time to solve this problem ourselves right now. Your ti

Re: [CMake] Fortran 9x dependencies

William A. Hoffman wrote: > At 03:20 PM 9/8/2006, Warren Turkal wrote: >> On Friday 08 September 2006 13:11, you wrote: >>> #ifdef FOO >>> use abc >>> #else >>> use xyz >>> #endif >> That's exactly the type of thing causing the problems. > > Brad, how hard do you think it would be to run the fortr

Re: [CMake] make install not works for me

Alexander Neundorf wrote: >>> Yes, this would be a good idea. >>> Actually, just login in to the Wiki and create a new wiki page with the >> same contents. >>> >> It still needs to be canonized by Kitware, so that users aren't looking >> at the wrong page. > > As a test I "ported" the "A simpl

Re: [CMake] Creating a custom target on Windows - strange problem

Arjen Markus wrote: > add_custom_target(${CMAKE_CURRENT_BINARY_DIR}/${file} ALL [snip] > When I run this in ..\build, using > cmake -G "NMake makefiles" ..\src [snip] > CMake Error: Cannot open file for write: > C:/arjen/plplot-5.6.1-cmake/testcbs/build/CMakeFiles/C:/arjen/plplot-5.6.1-cmak

Re: [CMake] MSYS EXEC_PROGRAM() or EXECUTE_PROCESS() fails

Peter Visser wrote: > I just "discovered" cmake, I find cmake easy to setup and it works > fantastic. > However, a small problem occurs. I'm using: cmake 2.4-patch3 under > MSYS-1.0.10. > > The problem occurs when using EXEC_PROGRAM() or EXECUTE_PROCESS(). > Instead of "sh.exe" from MSYS being us

Re: [CMake] MSYS EXEC_PROGRAM() or EXECUTE_PROCESS() fails

Brad King wrote: > Peter Visser wrote: >> I just "discovered" cmake, I find cmake easy to setup and it works >> fantastic. >> However, a small problem occurs. I'm using: cmake 2.4-patch3 under >> MSYS-1.0.10. >> >> The problem occurs when us

Re: [CMake] static vs. shared lib with same name

Darby J Van Uitert wrote: > I am linking against a library that I have as a static and shared > library with the same name (foo.a and foo.so). When I build my project > with BUILD_SHARED_LIBS on, I want it to look for foo.so and when I build > static libs, I want it to link against foo.a. But it s

Re: [CMake] EXEC_PROGRAM vs.. EXECUTE_PROCESS problem

Alexander Neundorf wrote: > EXECUTE_PROCESS(COMMAND ${RUBY_EXECUTABLE} -r rbconfig -e 'puts > Config::CONFIG["libdir"]' >OUTPUT_VARIABLE RUBY_POSSIBLE_LIB_PATH) EXECUTE_PROCESS does not use a shell like EXEC_PROGRAM so it directly converts CMake arguments into command line arguments. The abo

Re: [CMake] static vs. shared lib with same name

Brad King wrote: > Darby J Van Uitert wrote: >> I am linking against a library that I have as a static and shared >> library with the same name (foo.a and foo.so). When I build my project >> with BUILD_SHARED_LIBS on, I want it to look for foo.so and when I build >> sta

Re: [CMake] Missing MAP files support in VS 2005

Wojciech Jarosz wrote: > On Tuesday 05 September 2006 08:21, Laurentiu Nicolae wrote: >> Is there a way of enabling the generation of MAP files in the >> CMake-generated projects? I've been digging around in the source code >> and I can't seem to find anything that allows it. >> >> Basically, what

Re: [CMake] elseif request

Alan W. Irwin wrote: > So far all but one of those who responded to the discussion are in support > of the idea, but it is also fair to say that only a handful of subscribers > to this list have responded yet. > > I am particularly interested in the opinion of Bill Hoffman, Brad Ki

Re: [CMake] post-installation tests

Brandon J. Van Every wrote: > I'm going up the Dart / CTest learning curve. How am I supposed to > implement tests that depend on my project already being installed? > Doing what I thought would be obvious, I found a way to crash > CMakeSetup. I've reported this as bug #3779. > ADD_DEPENDENCIES

Re: [CMake] HDF5 Build files

Mike Jackson wrote: > Has anyone created an HDF5 cmake build script for the HDF5 1.6.5 > distribution? > > I took the cmake file from the XMDF project and put in the sources for the > HDF5 1.6.5 project and tried to build but got some link errors. I am > assuming that I _all_ the sources didn't ne

Re: [CMake] exclude directories from dependency scanning ?

Alexander Neundorf wrote: > I'd like to exclude some files from being scanned for dependencies, i.e. all > files which have ecos/install/include/ as part of their path. > I found CMAKE_C_INCLUDE_SCAN_REGEX, but I don't think I can use it for > excluding directories, or is there a way to do this ?

Re: [CMake] Make a Find"lib" generic

Xavier Larrode wrote: > I have done lots of FindPackage (for linux) for Ogre, Cegui, GLADE2 > etc... And i would like to make it generic. [snip] > So the question is, how to provide an argument to an INCLUDE (file) and > use it You can just set a variable before the INCLUDE command. However you s

Re: [CMake] How to specify default build dir in CMakeLists.txt?

Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote: > I am pretty new to CMake. Is there a way to specify a > default build dir in CMakeLists.txt? The build directory is always a user selection. There can be more than one build tree per source tree so trying to turn an in-source invocatio

Re: [CMake] Portable "treat warnings as errors"?

Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote: > I thought about doing it this way. However, then I thought > that there might be some portable way of doing that which would save me > all the IF/ENDIF's. Sounds like something relatively easy to implement. > Should I add that to CMake's

Re: [CMake] How to specify default build dir in CMakeLists.txt?

Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote: > The goal is to have an out-of-source build by default. > The target is a programmer who compiles my package just > to get the libraries needed for another project. He would > have one less option to worry about, especially, if > he wasn't

Re: [CMake] 3rd party modules

Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote: > Some packages provide modules/programs that > provide information where they were installed. For > example, "FooLibrary" may provide > FooLibrary.m4 for auto-tools, > FooLibrary.pc for pkg-confing, > or > Foo-config for anything else. >

Re: [CMake] Using CPACK to generate RPM

Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote: > I am sorry to bomb the mailing list with all my questions. > However, CMake is pretty exciting and my group is very likely to > migrate to it. > I found a link that mentions that CPACK can generate an RPM: > http://wiki.na-mic.org/

Re: [CMake] template files (.t) in Windows VCproj builds

Philip Lowman wrote: > 1.) [minor] After adding all of my header files (.h) and template files > (.t) to the ADD_LIBRARY command I noticed that the header files were > being placed in a separate folder called "Header Files" in the VC > Projects. Cool. Unfortunately, however, the template files we

Re: [CMake] Static Linking C++ Library

Mike Melanson wrote: > I am working on a fairly large software project that I autotool'd some > time ago. The build system has been working reasonably well. However, I > have hit a possible limitation that I don't know how to solve with > autotools. So I wanted to know if CMake can solve this probl

Re: [CMake] Static Linking C++ Library

Mike Melanson wrote: > Brad King wrote: >> This is not really a problem that a build system can solve directly. >> The native build tools need to be configured to support it. In order to >> link statically to the C++ runtime but dynamically to the C runtime and >>

Re: [CMake] Static Linking C++ Library

Mike Melanson wrote: > Brad King wrote: >> You can link the entire program statically if you don't have any of your >> own shared libraries. Then running "ldd myexe" will produce a message >> that the executable is not dynamically linked. This

Re: [CMake] make scanner.i :(

Filipe Sousa wrote: > [EMAIL PROTECTED] ~/build/stl $ make scanner.i > make[1]: *** No rule to make target `cmake_force', needed by > `CMakeFiles/stl.dir/scanner.i'. Stop. > make: *** [scanner.i] Error 2 > > [EMAIL PROTECTED] ~/build/stl $ cmake --version > cmake version 2.5-20060920 Fixed: /cv

Re: [CMake] custom_command pre_build vs. post_build

Richard Fuchs wrote: > I've added some logging around each of our libraries that we build, but > I'm getting an unexpected result. I'm using a custom command with the > cmake -E echo to print a log out before and after a library is built. > However, the results are not consistent. When we have c

Re: [CMake] About testing with ctest

Slava Semushin wrote: > - I added ENABLE_TESTING() to CMakeLists.txt and ADD_TEST() to > tests/CMakeLists.txt and my test works. But I see autogenerated > files with name DartTestfile.txt in src/ also: > > [EMAIL PROTECTED] ~/openfm]$ cat src/DartTestfile.txt > # CMake

Re: [CMake] custom_command pre_build vs. post_build

Richard Fuchs wrote: > Ah, I see the note now. It's not in the section of the cmake book that > describes the command, but it's in the command index in the back and on > the web. > So why does it work with the add_custom_target? It doesn't AFAIK. The custom rule specified by the custom target is

Re: [CMake] How to rename a target?

Enrico Scholz wrote: > does there exist a way to rename a target 'exe-foo' so that it is > installed as 'bin/foo' finally? You can do this at build time before installing. See OUTPUT_NAME in SET_TARGET_PROPERTIES. -Brad ___ CMake mailing list CMake@cma

Re: [CMake] Re: TRY_COMPILE painful for tool testing

Brandon J. Van Every wrote: > I think the result is, quotes and backslashes cannot be reliably escaped > with respect to macro wrappers for ADD_CUSTOM_TARGET. Thus it is not > possible to write a macro that will TRY_COMPILE an arbitrary COMMAND. > > So the feature that I would like, is a TRY_COMM

Re: [CMake] template files (.t) in Windows VCproj builds

Philip Lowman wrote: > Brad King wrote: >> If they have the same name as a .h or .cc file there is a bug in CMake >> 2.4.3 that causes this. The work around is to add the HEADER_FILE_ONLY >> property with SET_SOURCE_FILES_PROPERTIES. It is fixed in CVS CMake and >

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