Re: [CMake] flex/bison modules?

On Fri, Feb 27, 2009 at 7:37 PM, j s wrote: > Hi, > > Are there packages for finding Flex and Bison available? I'm starting a > porting effort to windows, and I am hoping there is a way for these to work > in visual studio? Depending on how often you change your grammar, you may want to consid

[CMake] flex/bison modules?

Hi, Are there packages for finding Flex and Bison available? I'm starting a porting effort to windows, and I am hoping there is a way for these to work in visual studio? Regards, Juan ___ Powered by www.kitware.com Visit other Kitware open-source pro

[CMake] Any experiences with ICU genrb?

Anybody out there know anything about ICU and genrb? I need to convert a build system that uses genrb. As I understand it, genrb is a tool that creates a static library from some input and you are supposed to link against it. So I have 2 different questions about this. 1) Using CMake, what is th

[CMake] making a FooConfig.cmake with components

I'm writing a FooConfig.cmake to support find_package(Foo COMPONENTS A B C) I see that Foo_FOUND is always TRUE no matter what I try to set to from FooConfig.cmake. How does a FooConfig.cmake tell the caller whether the components were all found? I can make my own variables, but I wanted to k

Re: [CMake] linking cmake targets to cpack targets

On Fri, Feb 27, 2009 at 7:36 AM, Eric Noulard wrote: > 2009/2/27 Aaron Turner : >> When I was using autotools, I'd hook up a target "version" to >> "dist-gzip" so that my version.c (which was auto-generated and had my >> svn repo revision in it) was always up to date when I built my source >> tarb

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] ASM support

Well, it seems that CMAKE_ASM_COMPILER is being invoked as a literal. If I copy dasm.exe to CMAKE_ASM_COMPILER.exe, it works, happily assembles files. So it's a bug in (a) what I did, (b) the instructions, or (c) the quasi-asm support in there already. I did notice that the ATT support (which

Re: [CMake] Avoiding a relink

On Fri, Feb 27, 2009 at 2:32 PM, Jed Brown wrote: > On Fri 2009-02-27 20:26, Jed Brown wrote: > > On Fri 2009-02-27 11:09, Bill O'Hara wrote: > > > Lets say I have a CMakeLists.txt like this: > > > > > > add_library(foo STATIC foo.c bar.c) > > > add_executable(test test.c) > > > target_link_libra

Re: [CMake] Avoiding a relink

On Fri 2009-02-27 20:26, Jed Brown wrote: > On Fri 2009-02-27 11:09, Bill O'Hara wrote: > > Lets say I have a CMakeLists.txt like this: > > > > add_library(foo STATIC foo.c bar.c) > > add_executable(test test.c) > > target_link_libraries(test foo) > > > > where test.c uses only functions defined

Re: [CMake] Avoiding a relink

On Fri 2009-02-27 11:09, Bill O'Hara wrote: > Lets say I have a CMakeLists.txt like this: > > add_library(foo STATIC foo.c bar.c) > add_executable(test test.c) > target_link_libraries(test foo) > > where test.c uses only functions defined in foo.c but not bar.c (assume some > other target will us

Re: [CMake] Avoiding a relink

On Fri, Feb 27, 2009 at 2:09 PM, Bill O'Hara wrote: > Lets say I have a CMakeLists.txt like this: > > add_library(foo STATIC foo.c bar.c) > add_executable(test test.c) > target_link_libraries(test foo) > > where test.c uses only functions defined in foo.c but not bar.c (assume > some other target

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

[CMake] Avoiding a relink

Lets say I have a CMakeLists.txt like this: add_library(foo STATIC foo.c bar.c) add_executable(test test.c) target_link_libraries(test foo) where test.c uses only functions defined in foo.c but not bar.c (assume some other target will use foo as well and use functions from both foo.c and bar.c).

Re: [CMake] Upper or lower case for package variables in FindXXX.cmake files?

On Fri, Feb 27, 2009 at 1:13 PM, Matt Williams wrote: > Based on the modules readme.txt [1] I have been assuming that if I have a > package called QtOgre (with that capitalisation) then the FindXXX.cmake > file > should be called FindQtOgre.cmake (alternatively there should be a > QtOgreConfig.cm

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

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, but I can't figure out how

[CMake] Upper or lower case for package variables in FindXXX.cmake files?

Based on the modules readme.txt [1] I have been assuming that if I have a package called QtOgre (with that capitalisation) then the FindXXX.cmake file should be called FindQtOgre.cmake (alternatively there should be a QtOgreConfig.cmake file). In order to maintain unambiguity, I have been calling t

Re: [CMake] Unlinking a library at run time for an executable

On Fri, Feb 27, 2009 at 4:49 AM, ankit jain wrote: > Hi , > > I have defined a variable for a set of libraries that i want to link with > some executables. > > But with one executble i dont want to use one of the library from the set > of libraries. > > Can i unlink that particular library for th

Re: [CMake] printing search paths?

Thanks all! b. On Fri, Feb 27, 2009 at 12:14 AM, Adolfo Rodríguez wrote: > I think you should try: > > get_directory_properties(output INCLUDE_DIRECTORIES) > message(STATUS ${output}) > > As the > docsays: > "Th

Re: [CMake] ADD_TEST(...) doesn't output any tests into CTestTestfile.cmake (cmake 2.6-patch 0)

Pavel Shevaev wrote: Can you create a complete but small example that shows the problem? Ok, I tried to extract the minimal non-working example from my CMakeLists.txt. foo/CMakeLists.txt: == cmake_minimum_required(VERSION 2.6 FATAL_ERROR) project(foo

Re: [CMake] linking cmake targets to cpack targets

2009/2/27 Aaron Turner : > When I was using autotools, I'd hook up a target "version" to > "dist-gzip" so that my version.c (which was auto-generated and had my > svn repo revision in it) was always up to date when I built my source > tarball.  Is there a way to do that with cpack's package_source

Re: [CMake] Technique for generating projects that depend on generated sources

I believe you can have cmake read the contents of a file into a variable. If the file that lists the generated files is a semi-colon or space delimited (assuming no spaces in the names or paths) then you can read the file directly into a cmake variable, then use that variable as the source

[CMake] install target and DEBUGRT_POSTFIX

Hi, I'm having problems with the install(TARGETS ... command. In my project i set the property DEBUGRT_POSTFIX "_d" on each target so the files ends with "_d". This works fine, but when the command INSTALL(TARGETS mytarget RUNTIME DESTINATION lib LIBRARY DE

Re: [CMake] ADD_TEST(...) doesn't output any tests into CTestTestfile.cmake (cmake 2.6-patch 0)

> Can you create a complete but small example that shows the problem? Ok, I tried to extract the minimal non-working example from my CMakeLists.txt. foo/CMakeLists.txt: == cmake_minimum_required(VERSION 2.6 FATAL_ERROR) project(foo) enable_testing() in

Re: [CMake] Technique for generating projects that depend on generated sources

Thanks for the advice, Bill. My situation is somewhat different, though. The output source files are not known ahead of time. Thus, the general scheme is: - build runs the source generator; one of the outputs is a file containing the names of the generated sources. - rerun cmake to regenerate the

Re: [CMake] ADD_TEST(...) doesn't output any tests into CTestTestfile.cmake (cmake 2.6-patch 0)

Pavel Shevaev wrote: Folks, any idea why this can be happening? I have the following lines in my CMakeLists.txt: ... ENABLE_TESTING() INCLUDE(CTest) ADD_TEST(AllTests {$project_SOURCE_DIR}/scripts/runtests) ... I also have properly configured CTestConfig.cmake in the same directory with CMakeL

[CMake] ADD_TEST(...) doesn't output any tests into CTestTestfile.cmake (cmake 2.6-patch 0)

Folks, any idea why this can be happening? I have the following lines in my CMakeLists.txt: ... ENABLE_TESTING() INCLUDE(CTest) ADD_TEST(AllTests {$project_SOURCE_DIR}/scripts/runtests) ... I also have properly configured CTestConfig.cmake in the same directory with CMakeLists.txt, however "cd b

Re: [CMake] adding extra resources to MACOSX package

Here is a code snippet from one of my own projects. IF(APPLE) SET(GUI_TYPE MACOSX_BUNDLE) SET(MACOSX_BUNDLE_ICON_FILE ${MXATools_RESOURCES_DIR}/QHDFViewer.icns) SET(PROJECT_SRCS ${PROJECT_SRCS} ${MACOSX_BUNDLE_ICON_FILE}) SET_SOURCE_FILES_PROPERTIES(${MACOSX_BUNDLE_ICON_FILE} PROPERTIES MA

[CMake] adding extra resources to MACOSX package

Hello, How can I copy external resources in the MACOSX bundle. I haven't seen any command to do this. I also need to change paths in a config file depending on the packaging (MACOSX or Linux or Windows). Is it possible to call some external program like sed ,awk or a custom script in CMAKE ?

Re: [CMake] MAC OXS linking problem : -lcrt1.10.5.o not found

Tanks, adding -mmacosx-version-min=10.4 to the CMAKE_CXX_FLAGS, it worked. But I had to change the compiler from c++ to g++. On Feb 26, 2009, at 4:17 PM, Sean McBride wrote: On 2/26/09 4:07 PM, Benoit Callebaut said: I end up with the following message: Linking CXX executable CubeMapping.ap

[CMake] Unlinking a library at run time for an executable

Hi , I have defined a variable for a set of libraries that i want to link with some executables. But with one executble i dont want to use one of the library from the set of libraries. Can i unlink that particular library for this executable since iam using a variable for all those libraries. E

Re: [CMake] printing search paths?

I think you should try: get_directory_properties(output INCLUDE_DIRECTORIES) message(STATUS ${output}) As the docsays: "This read-only property specifies the list of directories given so far to the include_directorie