Re: [CMake] Help with cmake_policy

eblo...@free.fr wrote: I'm having trouble to understand how to use the cmake_policy the easy way: My CMakeLists.txt files are written for CMake 2.6.2 I've upgraded to CMake 2.6.3, and I got some warnings about CMP0011. How can I tell CMake 2.6.3 to work the way CMake 2.6.2 used to work, without

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

Philip Lowman wrote: Brad King wrote: I suggest making the extraction rule generate a stamp file with "cmake -E touch ...". Thanks for pointing out those two problems. Not too worried about either of them at the moment given what this is intended for. Another thing did concer

Re: [CMake] Help with cmake_policy

Alexander Neundorf wrote: On Wednesday 25 February 2009, eblo...@free.fr wrote: The customer may not need to know about CMake internals, and get weird warning messages. I'd also like to have them somewhat less scary looking... Manu, are you actually cutting release snapshots for the custome

Re: [CMake] install(EXPORT ..) and multiple projects

Clinton Stimpson wrote: I've got two projects with one depending on the other. I include the one project as a subdirectory and build it along with my project. Its similar to how ParaView includes VTK. I'm trying to use the install(EXPORT ...) to export my project from an installation tree, bu

Re: [CMake] Avoiding a relink

Philip Lowman wrote: I wasn't thinking of it in that context when I said that. Yes, I think you're correct and I've noticed that behavior before. I usually work around it with make foo/fast assuming foo is the shared library I'm patching. Not sure why CMake does what it does. For the Makef

Re: [CMake] Avoiding a relink

Philip Lowman wrote: On Fri, Feb 27, 2009 at 5:24 PM, Brad King Try removing an object file from a shared library, rebuild just that library, and then run the executable (which still exists). It will break at runtime, but if you try relinking the executable it will fail at

Re: [CMake] Git support status in CMake/CTest/CDash

Félix C. Morency wrote: I want to know if there are any progress on git support for CMake/CTest/CDash. Is this planned to be released "soon"? You can track progress here: http://www.cmake.org/Bug/view.php?id=7541 I have an implementation mostly done, but not quite ready for publishing to th

Re: [CMake] add_dependencies with an imported target

Joachim de Vries wrote: CMake version 2.7-20080708 Mac OSX 10.5 XCode 3.0 I have a problem with add_dependencies. If I add an imported static lib like this: add_library("mylib" STATIC IMPORTED) and try to add a dependency to this target on another target like this: add_dependencies(myapp "my

Re: [CMake] add_dependencies with an imported target

Joachim de Vries wrote: CMake version 2.6 Mac OSX 10.5 XCode 3.0 My problem is that I have the situation I described in the bottom. I have one app and one lib in one project. If I change something in my lib everything is compiled and the app starts but the app didn't link the lib again. The

Re: [CMake] Joining multiple directories into one

Jussi Pakkanen wrote: Hi all I'm looking into compiling OpenOffice.org with CMake. Currently it uses dmake and a custom build tool. The basic structure is that every logical component (Writer, widget toolkit etc) has its own subdirectory. These are well separated. The problem comes from the int

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

John Biddiscombe wrote: John Biddiscombe wrote: OK. I'm using 2.6.2 I'll let you know if the problem continues with 2.6.3 or later so I've been using 2.6.3-rc 14 for a while now /apps-vis/cmake-2.6.3-RC-14/bin/ccmake --version ccmake version 2.6-patch 3 RC-14 and the warnings still appear,

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

John Biddiscombe wrote: Brad BTW, the only reason CMake needs to order the directories is because of compatibility with how CMake 2.4 ordered them. You must be setting CMP0003 to OLD. If you set it to NEW you should never see this warning. That seems to have solved the problem. On second t

Re: [CMake] Joining multiple directories into one

Jussi Pakkanen wrote: On Mon, Mar 9, 2009 at 4:03 PM, Brad King wrote: do not perform very well in the VS IDE (this is not CMake, but the VS IDE implementation). The definitions will work, but they cause the IDE to use a separate invocation of the compiler for every source file instead of

Re: [CMake] 1 tricky question, 1 bug report

Bill Hoffman wrote: >> The following Fortran code cannot be compiled with CMake, because >> CMake looks for module called "name", which of course, does not exist. Actually it thinks the source is defining a module called "name". >> If I replace "Module" with "_Module_" the code compiles. >> =

Re: [CMake] 1 tricky question, 1 bug report

Maik Beckmann wrote: The _second_ option proposed in the book is to have two distinct fortran lexers (and probably two parsers). This is the cleanest solution, but would be engineered for this special problem, IMHO. Fixed and free format are practically two different languages from the parsi

Re: [CMake] imported lib properties...

Asmodehn Shade wrote: I am currently converting my old cmake 2.4 scripts to cmake 2.6.3, as I am enjoying the new possibilities offered by the export / import system I previously implemented my self a little dirty workaround this limitation... so I am pretty happy to see this coming along ;-)

Re: [CMake] 1 tricky question, 1 bug report

Maik Beckmann wrote: Brad King schrieb am Montag 16 März 2009 um 14:24: Maik Beckmann wrote: The _third_ option is to make the lexer format agnostic and handle formats at the parser code. This should work well, since we just have to make sure that the valid MODULE und USE statements are

Re: [CMake] 1 tricky question, 1 bug report

Maik Beckmann wrote: I still didn't test whether fixed format file can include a free format file, or vise versa. In this case having distinct lexers(and parsers?) is the only reliable approach. I just tried these cases and gcc chokes on both cases: ! main-free.f90 include 'fixed.f' ! main

Re: [CMake] automatically re-generating makefiles

Matthew Woehlke wrote: Bill Hoffman wrote: I still don't get the original problem??? We used to have Makefile: . It was removed when that work was pushed into cmake_check_build_system. Ah. Maybe it should come back? The problem with Makefile: input-foo.txt input-bar.txt regene

Re: [CMake] automatically re-generating makefiles

Brad King wrote: AFAIK there is no way to implement the make my-new-target interface reliably. FYI, you can write the above like this: make rebuild_cache && make my-new-target if you know that it is a new target. -Brad ___ Po

Re: [CMake] CMake shared libraries, install, and rpath

Alexander Neundorf wrote: On Wednesday 18 March 2009, Bartlett, Roscoe A wrote: Hello, How can we get CMake to deal with installed shared libraries and set the rpath correctly in a portable way? The issue is that we have is that we need to enable client applications to link to installed Trilin

Re: [CMake] Exporting imported target

Andreas Pakulat wrote: The easiest way to achieve what you want (having targets of projectB+projectC available to projectA) is by having the FindProjectB.cmake file simply do a find_package(ProjectC REQUIRED) call and then make sure that FindProjectC.cmake (or the ConfigProjectC.cmake) load the f

Re: [CMake] CMAKE_CURRENT_LIST_FILE in CMake 2.6.3

KSpam wrote: I attached a small example with the problem. The problem is actually a bit more complicated than my original explanation. I have a macro in my top-level CMakeLists.txt file: macro (getScriptDir _scriptDir) get_filename_component(${_scriptDir} ${CMAKE_CURRENT_LIST_FILE} PATH)

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

James Bigler wrote: I filed a documentation bug: http://public.kitware.com/Bug/view.php?id=8815 I've committed documentation and updated the bug entry. BTW, is there a particular reason why custom commands are only registered in the directory where they appear? They seem kind of like the lit

Re: [CMake] link_libraries() deprecated. Why?

Alex, Looking at history I see this was deprecated by a patch you sent me. Originally we called the command 'discouraged'. Why did we change to 'deprecated'? Marcel Loose wrote: Thanks for your reply. Your solution is ok, but it looks a bit like a workaround for a feature that is missing, but

Re: [CMake] Where to put own FindXXX.cmake files?

Dominique Belhachemi wrote: i would like to add a FindXXX.cmake to each of my library packages. Let's compare CMake with pkgconfig. A package containing a library is responsible to put a .pc file into /usr/lib/pkgconfig/ [snip] A package knows best where to find its own include and library fil

Re: [CMake] Where to put own FindXXX.cmake files?

Modestas Vainius wrote: On 2009 m. April 3 d., Friday 21:37:20 Brad King wrote: If your package is CMake-aware then it should install a CMake package file: http://www.cmake.org/Wiki/CMake_2.6_Notes#Packages [snip="from the wiki page"] It may also provide a CMake package configur

Re: [CMake] managing lists with space separated elements

Piotr Dobrogost wrote: Bill Hoffman wrote: It was a mistake to have CMAKE_CXX_FLAGS and CMAKE_C_STANDARD_LIBRARIES be strings they should have been lists. I'm glad you said this. It's something I've been trying to show in my posts. Certainly CMAKE_C_STANDARD_LIBRARIES should have been a lis

Re: [CMake] managing lists with space separated elements

Piotr Dobrogost wrote: Brad King wrote: Last year I started working on new features to allow projects to specify flags with modern semicolon-separated lists. See my comment from 2008-10-09 here: http://www.cmake.org/Bug/view.php?id=6493 It looks like that is the 3rd solution I suggested

Re: [CMake] Getting the compiler version?

Philip Lowman wrote: On Tue, Apr 14, 2009 at 11:17 AM, Bartlett, Roscoe A > wrote: Thanks for the pointer. We will look into this and try to create a module that other people could use also. However, it would be good if we could get this added as an offic

Re: [CMake] Linking to a library with a "-"

David Doria wrote: When I add a line like this: TARGET_LINK_LIBRARIES(MyProject boost_program_options-mt) in my link.txt file, -lboost_program_options gets produced instead (without the "-mt"), and therefore the library cannot be found. I've been creating a symlink with the name without the -

Re: [CMake] Imported libraries lookup

Sergey Rudchenko wrote: Hi all, My global generator adds some imported libraries in EnableLanguage method, but the TARGET_LINK_LIBRARIES command doesn't obey that fact the libraries are imported. Here is the code which adds an imported library: void cmGlobalSymbianMmpGenerator ::EnableLangua

Re: [CMake] msvc linking problem k3b on windows

Ralf Habacker wrote: For my opinion the problem here is caused by the fact that cmake uses the value of the OUPUT_NAME property for creating the import library name and not the target name which is expected. Why is it expected that the target name be used for the import library name and not OU

Re: [CMake] msvc linking problem k3b on windows

Ralf Habacker wrote: May be the following (new) properties OUTPUT_RUNTIME_NAME OUTPUT_ARCHIVE_NAME OUTPUT_LIBRARY_NAME which enforce the developer to change individual types of generated files would solve this problem in a generic way Good idea. We already do this for the output directory,

Re: [CMake] msvc linking problem k3b on windows

Ralf Habacker wrote: http://www.cmake.org/Bug/view.php?id=8920 Thanks. Oops, you're right. My bad. I guess you can use your workaround for now. yes, thanks for the hint. This might work better: set_target_properties(k3b_bin PROPERTIES IMPORT_SUFFIX _bin${CMAKE_IMPORT_LIBRARY_SUFF

Re: [CMake] Imported libraries lookup

Sergey Rudchenko wrote: What piece of code should handle those imported targets? I thought it is cmMakefile::AddLinkLibraryForTarget, but it doesn't do that. Should a local generator check itself whether a library is an imported target? I thought this work is done transparently for generators.

Re: [CMake] msvc linking problem k3b on windows

Ralf Habacker wrote: Brad King schrieb: We do support the "image version" fields in dll binaries. What do you mean by "real" versioned DLLs? Are you talking about side-by-side stuff? I mean integrating api versions in the runtime target filename to be able to have dif

Re: [CMake] Imported libraries lookup

Sergey Rudchenko wrote: On Wed, 2009-04-22 at 10:41 -0400, Brad King wrote: In general the generators should never have to see any imported targets. If you have a "cmTarget*" you can always ask its IsImported() method. Thanks, Brad. Now it's clean for we how things should be i

Re: [CMake] Problem with NMake generator after upgrade from 2.4.6 to 2.6.3

Dieter Oberkofler wrote: That should be: D:\MyDev\ljs_app\trunk\tools\..\xvt\win\lib\tls12dvc71.lib You are absolutely right but it seems to have worked in CMake 2.4.6... http://www.cmake.org/cmake/help/cmake2.6docs.html#policy:CMP0008 http://www.cmake.org/cmake/help/cmake2.6docs.html#command

Re: [CMake] Problem with NMake generator after upgrade from 2.4.6 to 2.6.3

Dieter Oberkofler wrote: I have been digging into this issue and found out that the problem might be cause by the following command that might have changed it's behaviour in CMake 2.6.4 == SET(CMAKE_CXX_LINK_EXECUTABLE "link.exe /OUT: > .ler ${CMAKE_START_TEMP_FILE} ${CMAKE_END_TEMP_FI

Re: [CMake] 2.6.4 add_subdirectory with same argument broken?

Carsten Neumann wrote: It does so by performing multiple passes over the source tree [snip] This all works fine with cmake 2.6.x (x < 4), but the latest version complains in the OSGSETUP pass on the first call to ADD_SUBDIRECTORY in that pass (see attachment for more details): [snip] Is this

Re: [CMake] foreach() bug?

alexandre.feb...@thomsonreuters.com wrote: foreach(arg ${list}) [snip] The empty element has been discarded by foreach(). Is this the wanted behaviour? If it is, how can I manage empty elements when I need them? The foreach command never even sees the empty arguments. By the time ${list} is

Re: [CMake] foreach() bug?

alexandre.feb...@thomsonreuters.com wrote: Ok, thanks for the info. Can I expect this "IN" mode to be delivered in 2.6.5? Probably not. It's currently experimental, and we might still change how it works. -Brad ___ Powered by www.kitware.com Visit

Re: [CMake] Static linking and find_library

Bill Hoffman wrote: Marcel Loose wrote: 2) How can I persuade find_library() to only search for static libraries? You can't. Yes, you can: find_library(MATH_LIB NAMES libm.a) If you specify a valid library name then CMake will look for it directly instead of prepending 'lib' and appendin

Re: [CMake] Problems building statically linked executable

Marcel Loose wrote: I'm really struggling to build statically linked executables with CMake (also see my previous post with subject: Static linking and find_library). I've answered in that thread. Furthermore I added the '-static' flag to the linker with SET(CMAKE_EXE_LINKER_FLAGS -static).

Re: [CMake] [PATCH] slightly modify cache variable behaviour, Was: Re: option() behavior

Bill Hoffman wrote: So, CMake has done what it does now from the start. There was a short period of time when it did not, and that was when a re-write was done, and it quickly broke some existing projects. Here is the thread: http://www.cmake.org/pipermail/cmake/2007-March/013204.html I th

Re: [CMake] using IMPORTED targets in multiple projects within one CMake tree

Alexander Neundorf wrote: On Tuesday 05 May 2009, alexandre.feb...@thomsonreuters.com wrote: I saw this too. IMHO, it's a bug. If it's a feature, I don't see the point. I think it's a feature that imported targets are not global. Brad explained this in a mail not too long ago, but I don't rem

Re: [CMake] Implicity CMAKE_CURRENT_BINARY_DIR include_directories

Denis Scherbakov wrote: On Monday 11 May 2009, Denis Scherbakov wrote: CMAKE_LINK_DEPENDS_DEBUG_MODE is also not documented. Is this one an official public variable or may it go away again ? If you ask me - I don't know, I am not a CMake developer. But there is a lot functionality built aroun

Re: [CMake] Static linking and find_library

Marcel Loose wrote: On Mon, 2009-05-11 at 13:39 -0400, Brad King wrote: find_library(MATH_LIB NAMES libm.a) Does that also mean that I could change the default search order by using: find_library(MATH_LIB NAMES libm.a libm.so) The search looks for all the names in each directory before

Re: [CMake] Static linking and find_library

S. Levent Yilmaz wrote: How can one enforce static linkage on a per platform basis (not the whole project)? In other words, what setting can we insert into a toolchain file to make this possible? Let me identify a problem here with find_library()

Re: [CMake] Deriving version number from a header (safely)

Doug Gregor wrote: However, we'd also like to force CMake to reconfigure when boost/version.hpp changes. Is there some top-level target that we can attach such a dependency to? This has come up several times recently. We need to add a feature to let projects specify their own files on which th

Re: [CMake] Install problems

Gheorghe Iancu wrote: compiler: VisualAge C++ Professional / C for AIX Compiler, Version 6 I don't think anyone has ever built CMake with that compiler before. The only testing we have on AIX is with VisualAge 9.0. See here: http://www.cdash.org/CDash/index.php?project=CMake for tested pla

Re: [CMake] Copy target from different configurations

Jacob Repp wrote: I found that the VS7 local generator doesn't honor the *_OUTPUT_DIRECTORY properties so here's a modification that I added to our local version: I think your patch just updates the "intermediate files" output location, which includes all the object files. CMake 2.6.4 does hon

Re: [CMake] Using relative paths with INSTALL

Timothy M. Shead wrote: Folks: On a couple of occasions now I've recommended the use of relative paths with the OSX bundle installer - this to install files within the bundle in "nonstandard" locations. It would be good to hear from the CMake gurus on whether relative paths are supported or

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

Bartlett, Roscoe A wrote: 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 be able to append

Re: [CMake] Precompiled Headers

John Drescher wrote: Thanks for your help. Do you (or anyone else) know if there are any plans to make a dedicated function for this so it is cleaner and portable? http://www.vtk.org/Bug/view.php?id=1260 I just added a FAQ entry: http://www.cmake.org/Wiki/CMake_FAQ#Does_CMake_support_preco

Re: [CMake] Precompiled Headers

Pau Garcia i Quiles wrote: Apart from every compiler making this different (i. e. different parameters for each compilers), what are the difficulties you see for making this a first-class feature? It's not the different flags for each compiler that makes it hard. We already do that for other fe

Re: [CMake] Using relative paths with INSTALL

Timothy M. Shead wrote: Brad King wrote: Timothy M. Shead wrote: INSTALL(FILES foo DESTINATION ../MacOS) [snip] The current behavior works fine, my question was whether relative paths outside the install prefix (i.e. paths starting with one or more "..") were officially

Re: [CMake] import library

Tyler Roscoe wrote: On Fri, Jun 12, 2009 at 05:46:39PM +0200, Leon Aronson (DT) wrote: I'm not generating dll's (at least I intend to); it should all be static linking. Static libraries are also controlled by ARCHIVE_OUTPUT_DIRECTORY. If you are using static libraries then you don't get (or n

Re: [CMake] import library

Brad King wrote: VS is not complaining that it cannot *find* the .lib file...it's complaining that it cannot *create* it. The reason is that the directory does not exist. If I make the directory by hand before building then it works. I'm investigating CMake internals to find the cau

Re: [CMake] import library

Brad King wrote: We'll have to teach CMake to work around the problem. Please submit a bug report here: Nevermind, I've fixed it already. I'll schedule the fix for release 2.6.5. If you really did mean to dllexport something, then you need to let VS put the import library

Re: [CMake] One target being built several times during parallel build

Denis Scherbakov wrote: I have a project with three executables: E1 depends on lib A E2 depends on lib A E3 depends on lib A First A must be built, then E1, E2 and E3. I do "gmake -j9 E1 E2 E3" and I see that target "A" is being built 3? times instead of just one. I also notice that progress co

Re: [CMake] Copy target from different configurations

alexandre.feb...@thomsonreuters.com wrote: Hi, yes, this is definitely what I would like, there is no other way to get rid of these Debug/Release directories. I even would like to have the corresponding variables: - CMAKE_LIBRARY_OUTPUT_DIRECTORY_ - CMAKE_ARCHIVE_OUTPUT_DIRECTORY_ - CMAKE

Re: [CMake] Multiple COMMANDs in EXECUTE_PROCESS

David Cole wrote: sequentially... On Tue, Jun 16, 2009 at 3:19 AM, Denis Scherbakov mailto:denis_scherba...@yahoo.com>> wrote: I have multiple commands specified in one EXECUTE_PROCESS call like: EXECUTE_PROCESS(COMMAND cmd1 ... COMMAND cmd2 ... COMMAND cmd3...) Can anybody te

Re: [CMake] One target being built several times during parallel build

Denis Scherbakov wrote: 6. gmake -j5 mytest printf 7. I observe target PUTS being built 2 times and "Building CXX object puts/CMakeFiles/puts.dir/puts.cpp.o" 2 times. Also counter goes to 150%. Your project looks fine. I missed in your earlier post that you ran "gmake -j9 E1 E2 E3". The probl

Re: [CMake] Avoiding error when using add_subdirectory twice on same path (CMake 2.6.4)

[approach using package meta-data files to control build] > This approach minimizes the orchestrating effort and allows > developers to work on their part of an package without worrying > about unrelated projects. Take a look at this thread: http://www.cmake.org/pipermail/cmake/2009-May/029239

Re: [CMake] Avoiding error when using add_subdirectory twice on same path (CMake 2.6.4)

Tyler Roscoe wrote: Even if it were a policy, any project that tries to do this would get the warning. Yes, it could temporarily avoid the warning by setting the policy to OLD, but it should *still* be updated to the NEW behavior! Again, policies are not used for choosing among desirable behavi

Re: [CMake] One target being built several times during parallel build

Denis Scherbakov wrote: Brad, could you please, ask someone who knows about this problem in detail what is this more important feature and why it is not possible to fix this bug? Please report it here: http://www.cmake.org/Bug Could you suggest, how to prevent users from trying to compile

Re: [CMake] Submitting a FindFortran Module for mixed C/Fortran code

Will Dicharry wrote: I spoke with Bill Hoffman at a conference last week, and he mentioned that Kitware is currently working on a module to correctly find the Fortran runtime libraries. I have written such a module, and if you are interested (or haven't finished your own already), I'd like to

Re: [CMake] Submitting a FindFortran Module for mixed C/Fortran code

Will Dicharry wrote: Thanks, it is issue ID 0009195. The attached module is FindFortran.cmake. I didn't mention in my earlier message that the module has also been tested on a Cray XT4 running CNL/PGI. Thanks, I've assigned the issue to myself: http://www.cmake.org/Bug/view.php?id=9195 I'

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

Michael Schildt wrote: Hello! It been a while for this topic... I would like to know if there are any (good) news on this issue. I have exactly the mentioned problem using the ITK 3.14 source. Do I have to make the suggested modification of the first post on this topic to ALL the CMakeLists.tx

Re: [CMake] IBM Fortran and the C Preprocessor

Will Dicharry wrote: It appears that add_definitions() places -DWHATEVER in the compile command line on all Unix variants. Unfortunately, IBM's Fortran compiler uses -D as a compile flag for something other than adding a preprocessor definition. In order to pass a preprocessor definition, yo

Re: [CMake] IBM Fortran and the C Preprocessor

Will Dicharry wrote: The toolchain file looks like this (the project is actually mixed C/Fortran code so there's some C/C++ stuff in the actual toolchain file, but this simple toolchain with a simple Fortran exe reproduces the problem): set( CMAKE_SYSTEM_NAME AIX ) set( CMAKE_Fortran_COMPILER

Re: [CMake] Unix makefiles feature request

Robert Bielik wrote: Ok, apologies if this is already implemented, just haven't seen it. When making "Unix Makefiles", then link.txt script have archive files (static libraries) listed in the order they appear in the TARGET_LINK_LIBRARIES directive. The GCC linker (LD) has the peculiarity tha

Re: [CMake] Unix makefiles feature request

Tyler Roscoe wrote: On Wed, Jun 24, 2009 at 11:38:56AM -0400, Brad King wrote: Flags can be passed to target_link_libraries too: add_library(A STATIC a.c) add_library(B STATIC b.c) add_executable(main main.c) target_link_libraries(main -Wl,--start-group A B -Wl,--end-group) This is

Re: [CMake] IBM Fortran and the C Preprocessor

Will Dicharry wrote: It turns out that the problem is not the toolchain file, it's the flag. Running the following reproduces the problem on both IBMs I have access to: $ FC=mpxlf90 FFLAGS="-qfixed=72" cmake .. However, $ FC=mpxlf90 FFLAGS="-q64" cmake .. works just fine on both systems.

Re: [CMake] Linking 3rd party libraries

Nathan Paul wrote: Doesn't target_link_libraries only allow you to change the library used for the configuration, not set the library path. Sure I could prepend the correct path to the library, but it still doesn't change the library path. Specifying libraries by full path is the preferred me

Re: [CMake] Mercurial support for CTest

Bart Janssens wrote: Hi all, We're planning to move our project (K-3D) from SVN to Mercurial. Are there any plans to support Mercurial in CTest? A search turned up these results: http://www.mail-archive.com/cmake@cmake.org/msg17597.html http://public.kitware.com/Bug/view.php?id=7879 Thanks for

Re: [CMake] cmake -E move/rename?

Marcel Loose wrote: Ah, must not have been the only one wondering ;-) Do you, by any change, know if renames can also be done across directories -- i.e. rename -- or does it only support file-to-file and dir-to-dir rename? It is just a wrapper around the posix 'rename' function. The source

Re: [CMake] if(string MATCHES regex) question

Eric Noulard wrote: If so, I still don't quite get the usage pattern in, e.g., CheckIncludeFile.cmake. What are they trying to check? Better ask the author of this file :-) This was a hack left from before the 'DEFINED' option was available from the if() command. The code if(VAR MATCHES "

Re: [CMake] [New Module] FindHDF5.cmake

Will Dicharry wrote: > Mike Jackson wrote: >> Can you post your module or attach it to a bug/feature request? I also >> have a FindHDF5 module and I would like to compare the two. > > Sorry about that, I meant to attach the module to the first email. It > is attached to this one. After you two h

Re: [CMake] Processing the output from CMake build

Dieter Oberkofler wrote: > This does sound very interesting but I'm not sure if I understand how this > might replace my need for a wrapper. > To better understand, it would be most helpful, if you could eventually post > a short CMakeLists.txt snipped on how to capture the output from a > compile/

Re: [CMake] OPTION-like combobox

Pau Garcia i Quiles wrote: > Hello, > > Is there anything like OPTION but which allows to select one value > from a limited list of values (a combobox). Something like: > > OPTION( CRYPTOBACKEND "Select a cryptography backend" VALUES "OpenSSL" > "LibTomCrypt" "LibDES" DEFAULT "OpenSSL" ) There i

Re: [CMake] CMakeCache changing due to PDB

Ashwin Chandra wrote: Notice the pdb file changed in case. I think what is happening is that the compiler is generating the pdb file in all lower case on the first build run and when doing a second build run, it somehow knows the file is in lowercase now and it updates the build.make files (whi

Re: [CMake] cmake under OpenBSD: rpath support misconfigured

Frank Mertens wrote: > I started using cmake (2.6.3) under OpenBSD (4.5) and found it unwillingly to > link my software correctly. > The issue had been described some time ago: > http://www.cmake.org/pipermail/cmake/2006-November/011851.html. > I figured out that cmake-2.6.3/Modules/Platform/NetB

Re: [CMake] cmake under OpenBSD: rpath support misconfigured

Brad King wrote: > Frank Mertens wrote: >> The solution was simple: cp NetBSD.cmake OpenBSD.cmake. >> I think those two files can be kept safely identical. > > Currently OpenBSD.cmake has this line: > > SET_PROPERTY(GLOBAL PROPERTY FIND_LIBRARY_USE_OPENBSD_VERS

Re: [CMake] cmake on the BGP

John R. Cary wrote: > I am trying to build cmake on a Blue Gene P. > Configuration starts with > > > login1.surveyor$ ./bootstrap > - > CMake 2.6-4, Copyright (c) 2007 Kitware, Inc., Insight Consortium [snip] > http://www.cmake.org/pipermail/cmake/2006-

Re: [CMake] linking with .so w/ non-standard names

Bill Hoffman wrote: > So, it must be that the library is built with no soname. Brad will be > back in a few days, and should have a better idea of how to fix it. This is probably the problem. You can confirm this by running readelf -d /home/kchang/sandbox/thost/thostmduserapi.so |grep SONAME

Re: [CMake] cmake on the BGP

John R. Cary wrote: > env CC=xlc_r CXX=xlC_r [snip] > -- The C compiler identification is GNU Be sure to create a fresh build tree when changing compilers. CMake cached the 'cc' (gnu) compiler it found the first time and did not pay attention to the environment later. > /gpfs/software/linux-sles1

Re: [CMake] F90 and legacy F77

Arjen Markus wrote: > I do not think this is going to work: object files created with g77 > and gfortran are not compatible as far as I know. > > What constructs are they? F90/95 has one or two deleted features > but most compilers will simply accept them, perhaps grudgingly. [snip] >> How can thi

Re: [CMake] [New Module] FindHDF5.cmake

Will Dicharry wrote: > Sorry for the month of delay, but I've addressed Mike Jackson's concerns > below and I think I'm close to having the HDF5 find module ready for > submission. Excellent. I have a few comments from quickly glancing at them, but I don't have time for thorough testing. Overall

Re: [CMake] [New Module] FindHDF5.cmake

Will Dicharry wrote: > What is the convention for keeping a macro out of the public interface? Leave it out of the documentation and name it with a '_hdf5_' prefix (starting in '_'). -Brad ___ Powered by www.kitware.com Visit other Kitware open-source

Re: [CMake] [New Module] FindHDF5.cmake

Will Dicharry wrote: John R. Cary wrote: I am a real newbie here (exploring cmake) so my words should be taken with a grain of salt. But we find (in our current autotools setup), that it is good to have a flag that tells one whether the hdf5 was compiled with --enable-parallel. I agree that

Re: [CMake] [New Module] FindHDF5.cmake

John R. Cary wrote: > Brad King wrote: >> John, how do autotools detect this? > > hdf5par=`grep "HAVE_PARALLEL 1" $HDF5_INCDIR/H5config.h` > > I suppose there are other ways, but we have been doing this through > several versions of hdf5. Great, thanks John. W

Re: [CMake] Fortan and C++

Dominik Szczerba wrote: > I want to compile one file with fortran compiler (intel) and link with > the rest of my project. Will the latest cmake allow to fully cmakify > such scenario? FYI, CMake HEAD from CVS has a whole bunch of new features for mixed Fortran/C++ support. The main feature is th

Re: [CMake] Fortan and C++

Michael Wild wrote: > > On 24. Aug, 2009, at 14:30, Brad King wrote: >> FYI, CMake HEAD from CVS has a whole bunch of new features for mixed >> Fortran/C++ support. The main feature is that CMake now automatically >> detects the implicit language runtime libraries used b

Re: [CMake] [New Module] FindHDF5.cmake

Will Dicharry wrote: > All, > > I've committed the FindHDF5 and SelectLibraryConfigurations modules to > the CMake CVS repository. > > Thanks for your input and feel free to contact me with questions > regarding the modules. Great. Thanks for your contribution!

Re: [CMake] Unable to run cmake using absoft f95 Fortran compiler

venugopal gudimetla wrote: > I am using CMake 2.6.4 on Linux 64 bit platform. We are using absoft f95 > compiler. I am trying to build cgns3.0 which uses CMake for building the > package. FYI, to my knowledge no one has ever used CMake with that compiler. We need to teach CMake about the compiler'

Re: [CMake] Unable to run cmake using absoft f95 Fortran compiler

venugopal gudimetla wrote: > Thank you very much for your quick response. BTW, Fortran support is greatly improved in CMake's development version. If you can try the latest version from CVS HEAD, please do so. > Yeah I noticed too that for > some reason Cmakes is assuming f95 to be a GNU compiler

Re: [CMake] cmake on the BGP

Mathieu Malaterre wrote: > [ 4%] Built target cmsys > Linking C shared module libcmsysTestDynload.so > /usr/lib/gcc/powerpc64-suse-linux/4.1.2/../../../../lib/crt1.o:(.rodata+0x4): > undefined reference to `main' What does "make VERBOSE=1" say? Clearly this linker line is missing the flag to mak

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