Re: [CMake] Can I make the dependency scanner only look in certain include directories?

On 10/04/2012 12:38 PM, Dan Furlani wrote: > Thanks for the response. I considered that, it would solve the > problem for the codegen, but then CMake wouldn't be aware of the > (legitimate) dependency when it builds the program code. If you hide it behind a function-like macro then you can use th

Re: [CMake] [cmake-developers] setting LINKER_LANGUAGE still adds -lstdc++

On 10/09/2012 01:59 AM, James Bigler wrote: > On Mon, Oct 8, 2012 at 10:40 PM, James Bigler > wrote: > In my project I need to manually link against a special version of libstdc++ > add_library(a SHARED a.cpp) > set_target_properties(a PROPERTIES LINKER_LANGUA

Re: [CMake] Need cmake to work on AIX 5.3

On 10/10/2012 06:11 AM, Arindam Mukherjee wrote: > Here are the files. The first line of this file is missing the leading '#': $ head -1 cmake_aix/CMakeFiles/CompilerIdC/CMakeCCompilerId.c ifdef __cplusplus That means you've hit the issue reported here: http://www.cmake.org/Bug/view.php?id=1

Re: [CMake] link errors using OpenMP

On 10/08/2012 05:30 PM, Matthew Woehlke wrote: > When I write a simple program using OpenMP, with a CMakeLists.txt like: > > find_package(OpenMP REQUIRED) > add_definitions(${OpenMP_CXX_FLAGS}) > add_executable(foo foo.cpp) The value of OpenMP_CXX_FLAGS is CXX flags, not definitions. Try: set(

Re: [CMake] Need cmake to work on AIX 5.3

On 10/10/2012 02:27 PM, Arindam Mukherjee wrote: > On Wed, Oct 10, 2012 at 8:51 PM, Brad King wrote: >> $ head -1 cmake_aix/CMakeFiles/CompilerIdC/CMakeCCompilerId.c >> ifdef __cplusplus >> >> http://www.cmake.org/Bug/view.php?id=13149 >> http://cmake.org/

[CMake] [PATCH] Optionally skip link dependencies on shared library files

Add target property LINK_DEPENDS_NO_SHARED and initialization variable CMAKE_LINK_DEPENDS_NO_SHARED to enable this behavior. Suggested-by: Leif Walsh --- On 08/03/2012 04:57 PM, Leif Walsh wrote: > On 3 Aug, 2012, at 4:44 PM, Andreas Pakulat wrote: >> Actually no, adding new public API, changin

Re: [CMake] [PATCH] Optionally skip link dependencies on shared library files

On 10/26/2012 09:43 AM, Leif Walsh wrote: > This is exactly what I wanted, and the results were incredible. Thanks for testing. I've merged it to our 'next' branch in Git: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ed976313 We still need to add a test before it can be merged for inclus

Re: [CMake] [PATCH] Optionally skip link dependencies on shared library files

On 10/26/2012 10:39 AM, Leif Walsh wrote: > Sure thing. Can you let me know where to find an example test? I'll pattern > match one over the weekend. Most CMake tests just verify that binaries build correctly. The "Tests/BuildDepends" test is the only one that actually tests rebuild behavior. I

Re: [CMake] OSX deployment target confusion for 2.8.10

On 11/04/2012 07:59 PM, Bradley Giesbrecht wrote: > The problem is in commit e7e613e. Patching Darwin.cmake back to revision > 43b74793 solves the problem. > > The breakage is here: > http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e7e613efbf1da45a2a9e51d11a4022589d79c642 Thanks for tracking

Re: [CMake] OSX deployment target confusion for 2.8.10

On 11/05/2012 08:31 PM, Matthew Brett wrote: > Linking CXX executable shiboken > ld: framework not found QtCore > collect2: ld returned 1 exit status > make[2]: *** [generator/shiboken] Error 1 > make[1]: *** [generator/CMakeFiles/shiboken.dir/all] Error 2 > make: *** [all] Error 2 > > I get no su

Re: [CMake] OSX deployment target confusion for 2.8.10

On 11/06/2012 01:37 PM, Matthew Brett wrote: > I've attached the diff of the configs. The diff for generator/CMakeFiles/shiboken.dir/link.txt shows identical link lines except that 2.8.10 adds -isysroot /Developer/SDKs/MacOSX10.6.sdk to honor the CMAKE_OSX_SYSROOT. The change was here: http:

Re: [CMake] OSX deployment target confusion for 2.8.10

On 11/06/2012 03:29 PM, Matthew Brett wrote: > $ ls /Library/Frameworks | grep Qt > Qt3Support.framework > QtCore.framework Okay. > $ ls -al /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks/ > total 8 > drwxr-xr-x 4 root wheel 136 Jul 13 21:21 . > drwxr-xr-t 3 root wheel 102 Feb 14 2011 .

Re: [CMake] OSX deployment target confusion for 2.8.10

On 11/07/2012 03:14 PM, Matthew Brett wrote: > http://bugs.python.org/issue14018 Great, that is exactly this issue. > - I guess that explains it... Hum, how frustrating to have to worry > about the bad symlink. Yes. You'll have to fix them locally. Thanks for reporting back. -Brad -- Powere

Re: [CMake] OSX deployment target confusion for 2.8.10

On 11/07/2012 03:41 PM, Matthew Brett wrote: > I was probably thinking of the problem in the same way as you are, > which is: how can I make sure that the build works or fails gracefully > for someone else if they have the same problem? I'm not interested in spending much time trying to make the b

Re: [CMake] OSX deployment target confusion for 2.8.10

On 11/07/2012 04:13 PM, Matthew Brett wrote: >> We can warn about it though. Try adding something like this to the end >> of CMake's Modules/Platform/Darwin.cmake: >> >> if(IS_DIRECTORY "${CMAKE_OSX_SYSROOT}/Library/Frameworks" AND >>IS_SYMLINK "${CMAKE_OSX_SYSROOT}/Library/Frameworks/Framewor

Re: [CMake] [PATCH] Optionally skip link dependencies on shared library files

On 10/26/2012 11:22 AM, Leif Walsh wrote: > On Oct 26, 2012, at 11:13, Brad King wrote: > >> On 10/26/2012 10:39 AM, Leif Walsh wrote: >>> Sure thing. Can you let me know where to find an example test? I'll pattern >>> match one over the weekend. >> >

Re: [CMake] CC, CXX (& Fortran) compiler version - CMake macros wanted

On 12/11/2012 04:20 PM, Ilias Miroslav wrote: > I appreciate your efforts resulting into the introduction of > the CMAKE_[C|CXX]_COMPILER_VERSION variables Thanks. > However, I would need also the CMAKE_Fortran_COMPILER_VERSION variable. It was not left out by accident. It cannot be computed u

Re: [CMake] Object library doesn't work with CMake 2.8.10.2 Xcode generator

On 01/03/2013 04:33 PM, Bin Chen wrote: > clang: error: no such file or directory: > '/Users/bchen/share/temp/cmake-obj-lib/b-xcode/Debug/liba.a' > clang: error: no such file or directory: > '/Users/bchen/share/temp/cmake-obj-lib/b-xcode/Debug/libb.a' Xcode does not seem to recognize targets tha

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

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

<    4   5   6   7   8   9   10   11   12   13   >