Re: [CMake] Searching for an undefined symbol in library
On 11/15/2010 06:41 PM, Marek Szuba wrote: On Mon, 15 Nov 2010 12:00:04 -0500 cmake-requ...@cmake.org wrote: How do you select which of the libraries to use? Based on your Fortran compiler? To be exact, based on the Fortran compiler used to build the binary-only library. If so, I would check for the CMAKE_Fortran_COMPILER_ID variable and then go on from there. Hmm. I've looked at CMakeDetermineFortranCompiler.cmake and it seems to me the variable you've mentioned is related to the compiler available in the system. Is that correct? If so, I am afraid this is not what I need. Consider the following two scenarios: - the system has got both the GNU and the PGI compiler, the library variant is for the latter, CMake chooses the former. The program fails to build due to resolved PGI symbols; - the system has got both the GNU and the PGI compiler, the library variant is for the former, CMake chooses the latter. The program ends up unnecessarily linked against PGI run-time libraries, possibly causing binary-portability problems. I am of course aware I could override CMake's detection routines to choose a specific compiler. However, what I would like to do here is have the selection happen automatically depending on the variant of the binary-only library... Our user base is of the semi-educated sort, familiar with the concept of building the software from source but tending to run to us with questions when such building doesn't just go. Cheers, That's kind of recursive... I was asking for the criteria by which you select the binary-only library. But apparently that choice is made by the user, right? You have to detect which of the versions he has installed? Either go along with Alex' suggestion (or a variation thereof) or do it the easy way: Define a cache variable (e.g. LIBX_REQUIRES_PGI) and make it the responsibility of the user to make the choice. Another way would be to simply require that the user selects the appropriate compiler according to the library he has. Then you could do a simple try_compile to find out whether things work and otherwise error out. The user can select the compiler in various ways, the easiest is to set the FC environment variable when invoking CMake, e.g: $ FC=pgf90 cmake /path/to/source HTH Michael ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Eciipse and multiple configuration
I followed the tutorial at http://www.cmake.org/Wiki/Eclipse_CDT4_Generator in order to generate an Eclipse project. The only difference is that I select eclipseCDT - MiinGW Makefiles instead of eclipseCDT -Unix Makefiles. What I don't understand is how can I manage multiple configurations in the same project (for example Debug/Release) if the cmake-gui requires a specific CMAKE_BUILD_TYPE. Sorry but I'm a CMake newbie.. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack general question and example
Great, it's working. The only thing that was required was: SET(CPACK_DEBIAN_PACKAGE_MAINTAINER David Doria) Here is the working example: http://www.cmake.org/Wiki/CMake/CPack/Examples/Linux/DEB The page you sent (http://www.vtk.org/Wiki/CMake:CPackPackageGenerators#DEB_.28UNIX_only.29) has a lot of variables marked mandatory, but they all seem to have reasonable defaults except the MAINTAINER. Could this terminology be modified? Also, (I think) there are some typos that I don't feel confident correcting myself: if CPACK_DEBIAN_PACKAGE_VERSION is not set CPACK_PACKAGE_VERSION - If CPACK_DEBIAN_PACKAGE_VERSION is not set, it will default to CPACK_PACKAGE_VERSION if CPACK_DEBIAN_PACKAGE_NAME is not set, CPACK_PACKAGE_NAME (lower case) will be used I strongly suggest that we create http://www.cmake.org/Wiki/CMake/CPack/Examples/Linux/RPM http://www.cmake.org/Wiki/CMake/CPack/Examples/Linux/TAR http://www.cmake.org/Wiki/CMake/CPack/Examples/Windows/EXE (or whatever it is called) etc. so that it is very clear (one can copy/paste a solution) how to do this. Thanks for the help! David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] BundleUtilities
Hi all, I found the Qt example here: http://www.itk.org/Wiki/BundleUtilitiesExample http://www.itk.org/Wiki/images/2/25/QtTest-Package-Example.zip The two INSTALL commands seem fairly complicated - is there not a way to do all of that in the project-to-be-included's cmake configuration so that a command like INSTALL(Qt) could do the job? I think Qt may be a complicated place to start (all of the MOC/etc stuff seems to be an extra 30 lines distracting from the point of the BundleUtilities). Does anyone have an example that will bundle VTK with their executable? This seems like it should be easier, and equally as consumed by people around this wiki/list :) Thanks, David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Eciipse and multiple configuration
You really can't, unfortunately because only one configuration is possible per CMake build directory with the Makefile generator. Most people set CMAKE_BUILD_TYPE to Debug when using the Eclipse CDT4 Generator so they can debug. If you need to test regularly with release binaries, one solution is to create a second build directory with CMAKE_BUILD_TYPE set to Release pointing it to the same source tree as your Debug build. On Tue, Nov 16, 2010 at 7:09 AM, Andrea Galeazzi galea...@korg.it wrote: I followed the tutorial at http://www.cmake.org/Wiki/Eclipse_CDT4_Generator in order to generate an Eclipse project. The only difference is that I select eclipseCDT - MiinGW Makefiles instead of eclipseCDT -Unix Makefiles. What I don't understand is how can I manage multiple configurations in the same project (for example Debug/Release) if the cmake-gui requires a specific CMAKE_BUILD_TYPE. Sorry but I'm a CMake newbie.. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake -- Philip Lowman ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack general question and example
2010/11/16 David Doria daviddo...@gmail.com: Great, it's working. The only thing that was required was: SET(CPACK_DEBIAN_PACKAGE_MAINTAINER David Doria) Here is the working example: http://www.cmake.org/Wiki/CMake/CPack/Examples/Linux/DEB The page you sent (http://www.vtk.org/Wiki/CMake:CPackPackageGenerators#DEB_.28UNIX_only.29) has a lot of variables marked mandatory, but they all seem to have reasonable defaults except the MAINTAINER. Could this terminology be modified? Yes it should, you may correct the Wiki yourself but check the CPackDeb.cmake file before doing modification. Normally the most up-to-date documentation is within the module itself (for the module which define the doc) You may see it using: cmake --help-module CPackDeb cmake --help-module CPackRPM Also, (I think) there are some typos that I don't feel confident correcting myself: if CPACK_DEBIAN_PACKAGE_VERSION is not set CPACK_PACKAGE_VERSION - If CPACK_DEBIAN_PACKAGE_VERSION is not set, it will default to CPACK_PACKAGE_VERSION if CPACK_DEBIAN_PACKAGE_NAME is not set, CPACK_PACKAGE_NAME (lower case) will be used I strongly suggest that we create http://www.cmake.org/Wiki/CMake/CPack/Examples/Linux/RPM http://www.cmake.org/Wiki/CMake/CPack/Examples/Linux/TAR http://www.cmake.org/Wiki/CMake/CPack/Examples/Windows/EXE (or whatever it is called) Go ahead do it. May be the name should be the same as the generator name, you may get the list of generators (supported on your platform) by running: cpack --help You may be interested to know that there is a feature request for enhancing CPack doc: http://public.kitware.com/Bug/view.php?id=10067 If you want to help I think you would be welcomed. so that it is very clear (one can copy/paste a solution) how to do this. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] ARCHIVE_OUTPUT_DIRECTORY seems to not work
I'm trying to compile a static library named libkernel.a into a custom
path. I tried to set ARCHIVE_OUTPUT_DIRECTORY in two ways:
1:
set_property(TARGET PROPERTY ARCHIVE_OUTPUT_DIRECTORY
O:/kernel/${CMAKE_SYSTEM_NAME}/${CMAKE_BUILD_TYPE})
message(library output: ${ARCHIVE_OUTPUT_DIRECTORY})
add_library( Kernel STATIC ${SOURCES} )
2:
set(ARCHIVE_OUTPUT_DIRECTORY
O:/kernel/${CMAKE_SYSTEM_NAME}/${CMAKE_BUILD_TYPE})
message(library output: ${ARCHIVE_OUTPUT_DIRECTORY})
add_library( Kernel STATIC ${SOURCES} )
but the file libkernel.a is always created into the build directory.
Furthermore in the first case the output of message(library output:
${ARCHIVE_OUTPUT_DIRECTORY}) is: library output.
I currently use eclipse CDT - MinGW.
Maybe I miss something but what?
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ARCHIVE_OUTPUT_DIRECTORY seems to not work
Am Dienstag, 16. November 2010 schrieb Andrea Galeazzi:
I'm trying to compile a static library named libkernel.a into a custom
path. I tried to set ARCHIVE_OUTPUT_DIRECTORY in two ways:
1:
set_property(TARGET PROPERTY ARCHIVE_OUTPUT_DIRECTORY
O:/kernel/${CMAKE_SYSTEM_NAME}/${CMAKE_BUILD_TYPE})
message(library output: ${ARCHIVE_OUTPUT_DIRECTORY})
add_library( Kernel STATIC ${SOURCES} )
2:
set(ARCHIVE_OUTPUT_DIRECTORY
O:/kernel/${CMAKE_SYSTEM_NAME}/${CMAKE_BUILD_TYPE})
message(library output: ${ARCHIVE_OUTPUT_DIRECTORY})
add_library( Kernel STATIC ${SOURCES} )
Have you tried this?
add_library(Kernel STATIC ${SOURCES} )
set_target_properties(Kernel PROPERTIES ARCHIVE_OUT...)
Eike
signature.asc
Description: This is a digitally signed message part.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Merging a project from autoconf and GNUMakefiles
On 2010-11-16 09:35-0500 Torri, Stephen CIV NSWCDD, W15 wrote:
I am trying to merge a project that was using autoconf and GNUMakefiles. When
you use automake you can build static libraries in sub directories and then
link them together into one shared library in the end that was install. This is
not possible with Visual Studio. In GNU Make for the project I can see that
there are GNMakefiles in the subdirectories that build the object files where
they are linked together in the top level GNUMakefile.
In projects I have done where I have had source files in subdirectories I could
include all of them in a variable in the single CMakeLists.txt file in the top
directory. This project has 1079 C++ and C files in a variety of
subdirectories. The only way I can see to make a single shared library with
CMake is to include all the source files into a single variable in the single
CMakeLists.txt file like I do in my own projects. So to do this same technique
with this project seems unreasonable to ask these developers to adopt.
So I am wondering if I can set a single variable used across a variety of
CMakeLists.txt files? So that way in subdirectoryA I can add files to a
variable called SOURCES that I append files in from subdirectoryB. Therefore in
the top level CMakeLists.txt file I can declare:
add_library ( target ${SOURCES} )
target_link_libraries ( target ${DEPENDENCY_LIBRARIES} )
In a similar way I can include those headers I want to install in all the
subdirectories.
CMake deliberately reduces scope to help reduce side effects. But
there are ways to beat that for needs like yours.
You should look at the documentation of PARENT_SCOPE in the set
command. It might be suitable for your needs, but a drawback is you
must have (I assume) an unbroken recursive chain of such set commands
to communicate data from some deep subdirectory to your top-level
directory, and I would think that is a pretty fragile structure
subject to hard-to-find bugs if some subdirectories are moved around
in the future. For my own similar needs, I far prefer setting a GLOBAL
property (see documentation of set_property(GLOBAL...[APPEND]...)).
Alan
__
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__
Linux-powered Science
__
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ARCHIVE_OUTPUT_DIRECTORY seems to not work
On 11/16/2010 06:18 PM, Andrea Galeazzi wrote:
I'm trying to compile a static library named libkernel.a into a custom
path. I tried to set ARCHIVE_OUTPUT_DIRECTORY in two ways:
1:
set_property(TARGET PROPERTY ARCHIVE_OUTPUT_DIRECTORY
O:/kernel/${CMAKE_SYSTEM_NAME}/${CMAKE_BUILD_TYPE})
message(library output: ${ARCHIVE_OUTPUT_DIRECTORY})
add_library( Kernel STATIC ${SOURCES} )
2:
set(ARCHIVE_OUTPUT_DIRECTORY
O:/kernel/${CMAKE_SYSTEM_NAME}/${CMAKE_BUILD_TYPE})
message(library output: ${ARCHIVE_OUTPUT_DIRECTORY})
add_library( Kernel STATIC ${SOURCES} )
but the file libkernel.a is always created into the build directory.
Furthermore in the first case the output of message(library output:
${ARCHIVE_OUTPUT_DIRECTORY}) is: library output.
I currently use eclipse CDT - MinGW.
Maybe I miss something but what?
In 1, you don't specify any targets the property is imposed on; try
SET_PROPERTY(TARGET Kernel PROPERTY ARCHIVE_OUTPUT_DIRECTORY ...) or
SET_TARGET_PROPERTIES(Kernel PROPERTIES ARCHIVE_OUTPUT_DIRECTORY ...)
after the ADD_LIBRARY(Kernel ...). Furthermore, there's no predefined
variable ARCHIVE_OUTPUT_DIRECTORY, thus it turns out to be empty, and
setting this variable in 2 has no effect. Rather, there is a variable
CMAKE_ARCHIVE_OUTPUT_DIRECTORY which initializes the target property
ARCHIVE_OUTPUT_DIRECTORY for all targets, cf. the documentation.
Regards,
Michael
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] Fortran 90 modules not rebuilt
Hi, I've attached my project's top-level Makefile. I'm trying to force all the modules in the project to build first so I created a single library called modules that contains all my Fortran 90 module files. I'm invoking the Makefile explicitly passing the modules as the target to build (so I can build a clean project in two steps: make modules ; make) Here's the short error when trying to build the modules explicitly. [kbe...@wsblade001 tools]$ make modules make[3]: *** No rule to make target `Modules/CMakeFiles/modules.dir/ m_const.mod.stamp', needed by `Util/CMakeFiles/util.dir/scratch/trunk/ Util/Da2col_NSI.o'. Stop. make[2]: *** [Util/CMakeFiles/util.dir/all] Error 2 make[1]: *** [Modules/CMakeFiles/modules.dir/rule] Error 2 make: *** [modules] Error 2 and here's the longer version. [kbe...@wsblade001 tools]$ make -n modules /scratch/CMake/bin/cmake -H/scratch/trunk/tools -B/scratch/trunk/ tools --check-build-system CMakeFiles/Makefile.cmake 0 make -f CMakeFiles/Makefile2 modules /scratch/CMake/bin/cmake -H/scratch/trunk/tools -B/scratch/trunk/ tools --check-build-system CMakeFiles/Makefile.cmake 0 /scratch/CMake/bin/cmake -E cmake_progress_start /scratch/trunk/tools/ CMakeFiles 35 make -f CMakeFiles/Makefile2 Modules/CMakeFiles/modules.dir/all make -f Util/CMakeFiles/util.dir/build.make Util/CMakeFiles/util.dir/ depend cd /scratch/trunk/tools /scratch/CMake/bin/cmake -E cmake_depends Unix Makefiles /scratch/trunk/tools /scratch/trunk/tools/Util / scratch/trunk/tools /scratch/trunk/tools/Util /scratch/trunk/tools/ Util/CMakeFiles/util.dir/DependInfo.cmake --color= make -f Util/CMakeFiles/util.dir/build.make Util/CMakeFiles/util.dir/ requires make -f Util/CMakeFiles/util.dir/build.make Util/CMakeFiles/util.dir/ build make[3]: *** No rule to make target `Modules/CMakeFiles/modules.dir/ m_const.mod.stamp', needed by `Util/CMakeFiles/util.dir/scratch/trunk/ Util/Da2col_NSI.o'. Stop. make[2]: *** [Util/CMakeFiles/util.dir/all] Error 2 make[1]: *** [Modules/CMakeFiles/modules.dir/rule] Error 2 make: *** [modules] Error 2 Can anyone see why instead of making the modules, CMake seems to move right on to the Util library? -- Noel Makefile.gz Description: application/applefile Makefile.gz Description: GNU Zip compressed data ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] BundleUtilities
I think we used Qt as a basis because lots of people at the time were asking for it. Probably the simplest to demonstrate would be an example that builds a dynamic library and an executable that uses that library so therefor it must be packaged with the executable. Were you wanting to write the example or wondering if someone else has one? ___ Mike Jackson www.bluequartz.net Principal Software Engineer mike.jack...@bluequartz.net BlueQuartz Software Dayton, Ohio On Nov 16, 2010, at 8:30 AM, David Doria wrote: Hi all, I found the Qt example here: http://www.itk.org/Wiki/BundleUtilitiesExample http://www.itk.org/Wiki/images/2/25/QtTest-Package-Example.zip The two INSTALL commands seem fairly complicated - is there not a way to do all of that in the project-to-be-included's cmake configuration so that a command like INSTALL(Qt) could do the job? I think Qt may be a complicated place to start (all of the MOC/etc stuff seems to be an extra 30 lines distracting from the point of the BundleUtilities). Does anyone have an example that will bundle VTK with their executable? This seems like it should be easier, and equally as consumed by people around this wiki/list :) Thanks, David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] help with cmake fortran envar
Greetings, I am learning cmake. I have a fortran only project with some source files with f77 routines to compile, My CMakeLists.txt in the projects base directory has the following lines set(CMAKE_Fortran_COMPILER gfortran) ENABLE_LANGUAGE(Fortran) but running cmake ends like so:- -- Checking whether /usr/bin/gfortran supports Fortran 90 -- Checking whether /usr/bin/gfortran supports Fortran 90 -- yes CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly. Missing variable is: CMAKE_FORTRAN_COMPILER_ENV_VAR CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly. Missing variable is: CMAKE_FORTRAN_COMPILER CMake Error: Could not find cmake module file: $SOURCES/build/CMakeFiles/CMakeFORTRANCompiler.cmake CMake Error: Could not find cmake module file:CMakeFORTRANInformation.cmake CMake Error: CMAKE_FORTRAN_COMPILER not set, after EnableLanguage -- Configuring incomplete, errors occurred! # I have set FC=gfortran and FFLAGS=flags/I/use/to/compile/stuff as envars so I am perplexed what the required envar is. advice would be appreciated sincerely luxInteg ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] help with cmake fortran envar
Am Dienstag, 16. November 2010 schrieb luxInteg: Greetings, I am learning cmake. I have a fortran only project with some source files with f77 routines to compile, My CMakeLists.txt in the projects base directory has the following lines set(CMAKE_Fortran_COMPILER gfortran) ENABLE_LANGUAGE(Fortran) but running cmake ends like so:- -- Checking whether /usr/bin/gfortran supports Fortran 90 -- Checking whether /usr/bin/gfortran supports Fortran 90 -- yes CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly. Missing variable is: CMAKE_FORTRAN_COMPILER_ENV_VAR CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly. Missing variable is: CMAKE_FORTRAN_COMPILER CMake Error: Could not find cmake module file: $SOURCES/build/CMakeFiles/CMakeFORTRANCompiler.cmake CMake Error: Could not find cmake module file:CMakeFORTRANInformation.cmake CMake Error: CMAKE_FORTRAN_COMPILER not set, after EnableLanguage -- Configuring incomplete, errors occurred! # I have set FC=gfortran and FFLAGS=flags/I/use/to/compile/stuff as envars so I am perplexed what the required envar is. advice would be appreciated Remove that stuff. Start your CMakeLists.txt with PROJECT(foobar FORTRAN) Eike signature.asc Description: This is a digitally signed message part. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Compiling header files
I am trying to use ADD_LIBRARY to create a .lib file from a collection
of .cpp and .h files.
If I do:
ADD_LIBRARY(LibraryName AllOfTheCPPFiles.cpp)
and then try to link against that library, I get many missing-function
type linker errors. I looked in the .h files and many of them have
actual function definitions:
(an example):
class UdpTransmitSocket : public UdpSocket{
public:
UdpTransmitSocket( const IpEndpointName remoteEndpoint )
{ Connect( remoteEndpoint ); }
};
I tried to tell CMake to compile the .h files into the library as well
by doing this:
set(CMAKE_CXX_SOURCE_FILE_EXTENSIONS ${CMAKE_CXX_SOURCE_FILE_EXTENSIONS} h)
ADD_LIBRARY(LibraryName AllOfTheCPPFiles.cpp AllOfTheHFiles.h)
but it didn't seem to change anything. Is there a way this is typically handled?
Thanks,
David
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] BundleUtilities
On Tue, Nov 16, 2010 at 1:35 PM, Michael Jackson mike.jack...@bluequartz.net wrote: I think we used Qt as a basis because lots of people at the time were asking for it. Probably the simplest to demonstrate would be an example that builds a dynamic library and an executable that uses that library so therefor it must be packaged with the executable. Were you wanting to write the example or wondering if someone else has one? ___ Mike Jackson www.bluequartz.net I was wondering if someone else has one :) / encouraging it to be produced if it does not already exist. Unfortunately I can't dig into the code to write it myself. I think your suggestion of the VERY simplest case is a great one. If we had that as well as how to do it with another big library (VTK), this would hopefully be a much more usable tool. I think these would be good homes for them: http://cmake.org/Wiki/CMake/Examples/BundleUtilities/Simple http://cmake.org/Wiki/CMake/Examples/BundleUtilities/VTK http://cmake.org/Wiki/CMake/Examples/BundleUtilities/Qt David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Compiling header files
Is this a library that has built successfully before with another build
system? Has this application been built successfully before?
For instances where the actual implementation is in the .h file, you usually
must make sure you #include that header file in a cpp in your own
application (the app linking against libraryname). .h files are not
compiled on their own: when included in other cpp files, however, their
contents are compiled and available to that object file. My hunch is you
aren't #include-ing the .h files that contain these implementations.
Ryan
On Tue, Nov 16, 2010 at 1:03 PM, David Doria daviddo...@gmail.com wrote:
I am trying to use ADD_LIBRARY to create a .lib file from a collection
of .cpp and .h files.
If I do:
ADD_LIBRARY(LibraryName AllOfTheCPPFiles.cpp)
and then try to link against that library, I get many missing-function
type linker errors. I looked in the .h files and many of them have
actual function definitions:
(an example):
class UdpTransmitSocket : public UdpSocket{
public:
UdpTransmitSocket( const IpEndpointName remoteEndpoint )
{ Connect( remoteEndpoint ); }
};
I tried to tell CMake to compile the .h files into the library as well
by doing this:
set(CMAKE_CXX_SOURCE_FILE_EXTENSIONS ${CMAKE_CXX_SOURCE_FILE_EXTENSIONS} h)
ADD_LIBRARY(LibraryName AllOfTheCPPFiles.cpp AllOfTheHFiles.h)
but it didn't seem to change anything. Is there a way this is typically
handled?
Thanks,
David
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
Ryan Pavlik
HCI Graduate Student
Virtual Reality Applications Center
Iowa State University
rpav...@iastate.edu
http://academic.cleardefinition.com
Internal VRAC/HCI Site: http://tinyurl.com/rpavlik
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Compiling header files
If you have unresolved external errors, then you are (most likely)
missing a target_link_libraries call -- find out what library those
symbols are built into, and link to that library.
On Tue, Nov 16, 2010 at 2:03 PM, David Doria daviddo...@gmail.com wrote:
I am trying to use ADD_LIBRARY to create a .lib file from a collection
of .cpp and .h files.
If I do:
ADD_LIBRARY(LibraryName AllOfTheCPPFiles.cpp)
and then try to link against that library, I get many missing-function
type linker errors. I looked in the .h files and many of them have
actual function definitions:
(an example):
class UdpTransmitSocket : public UdpSocket{
public:
UdpTransmitSocket( const IpEndpointName remoteEndpoint )
{ Connect( remoteEndpoint ); }
};
I tried to tell CMake to compile the .h files into the library as well
by doing this:
set(CMAKE_CXX_SOURCE_FILE_EXTENSIONS ${CMAKE_CXX_SOURCE_FILE_EXTENSIONS} h)
ADD_LIBRARY(LibraryName AllOfTheCPPFiles.cpp AllOfTheHFiles.h)
but it didn't seem to change anything. Is there a way this is typically
handled?
Thanks,
David
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] BundleUtilities
On Tue, Nov 16, 2010 at 2:06 PM, David Doria daviddo...@gmail.com wrote: On Tue, Nov 16, 2010 at 1:35 PM, Michael Jackson mike.jack...@bluequartz.net wrote: I think we used Qt as a basis because lots of people at the time were asking for it. Probably the simplest to demonstrate would be an example that builds a dynamic library and an executable that uses that library so therefor it must be packaged with the executable. Were you wanting to write the example or wondering if someone else has one? ___ Mike Jackson www.bluequartz.net I was wondering if someone else has one :) / encouraging it to be produced if it does not already exist. Unfortunately I can't dig into the code to write it myself. I think your suggestion of the VERY simplest case is a great one. If we had that as well as how to do it with another big library (VTK), this would hopefully be a much more usable tool. I think these would be good homes for them: http://cmake.org/Wiki/CMake/Examples/BundleUtilities/Simple http://cmake.org/Wiki/CMake/Examples/BundleUtilities/VTK http://cmake.org/Wiki/CMake/Examples/BundleUtilities/Qt David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake The Qt example is a great one to start with. It should be easy to extend that to one that includes VTK. CMake and ParaView are also Qt-based apps that use BundleUtilities to build their installers. Their open source code is available as an example as well, although not as simple as the simplest example. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Compiling header files
Ryan, The issue is that these headers are only used internally to this collection of files, so I don't want to have to include them in my code. Here is a skeleton: The files I've been given -- External.h External.cpp Internal.h (used by External) Internal.cpp My files MyCode.cpp So I wanted to ADD_LIBRARY(TheLibrary External.cpp Internal.cpp) Then ADD_EXECUTABLE(MyCode MyCode.cpp) target_link_libraries(MyCode TheLibrary) where MyCode.cpp has only an #include External.h See what I mean? David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] setting the COMPILE_FLAGS property causes VS to start compiling header files
On Tue, Nov 16, 2010 at 12:27 AM, Rolf Eike Beer e...@sf-mail.de wrote: Am Dienstag, 16. November 2010 schrieb Eric Noulard: 2010/11/15 James Bigler jamesbig...@gmail.com If I set a COMPILE_FLAGS property on a header file via set_source_files_properties, CMake decides that these header files now need to be compiled (i.e. not treated as header files). Is this the intended behavior? I'm using both 2.8.1 and 2.8.3 on Windows with VS 2008 SP 1. This linked with an already filed bug: http://www.vtk.org/Bug/view.php?id=11404 My fix is for the MSVC2010 generator, this is 2008. Could nevertheless be the same issue. Eike Yeah, reading the thread the bug points to, this is the exact same symptom. I'll update the bug with my symptoms. James ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Fortran 90 modules not rebuilt
Hi Noel, On 11/16/2010 01:11 PM, K. Noel Belcourt wrote: I've attached my project's top-level Makefile. I'm trying to force all the modules in the project to build first so I created a single library called modules that contains all my Fortran 90 module files. I'm invoking the Makefile explicitly passing the modules as the target to build (so I can build a clean project in two steps: make modules ; make) What CMake code are you using to create this modules target? The Fortran module dependencies implementation is hidden inside the Makefile generators. There is no API to access any of its timestamp files or scanning rules. -Brad ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Fortran 90 modules not rebuilt
On Nov 16, 2010, at 1:59 PM, Brad King wrote:
Hi Noel,
On 11/16/2010 01:11 PM, K. Noel Belcourt wrote:
I've attached my project's top-level Makefile. I'm trying to force
all the modules in the project to build first so I created a single
library called modules that contains all my Fortran 90 module files.
I'm invoking the Makefile explicitly passing the modules as the
target to build (so I can build a clean project in two steps: make
modules ; make)
What CMake code are you using to create this modules target?
The modules CMakeLists.txt is attached.
The Fortran module dependencies implementation is hidden inside the
Makefile generators. There is no API to access any of its timestamp
files or scanning rules.
I'm not doing anything special.
-- Noel
# Author K. Noel Belcourt
set( MODULES_DIR ${MELCOR_SRC_DIR}/Modules )
set( DCH_DIR ${MELCOR_SRC_DIR}/DCH )
set( SNAP_DIR ${MELCOR_SRC_DIR}/SNAPAdapter )
set( EXEC_DIR ${MELCOR_SRC_DIR}/exec )
set( UTIL_DIR ${MELCOR_SRC_DIR}/Util )
set( H2C_DIR ${MELCOR_SRC_DIR}/H2C )
# uncomment next line to enable Pardiso solver
# add_definitions(-DMKL)
SET(SRCS
${MODULES_DIR}/M_Arguments.f90
${MODULES_DIR}/M_BONUS.f90
${MODULES_DIR}/M_BONUS_MELCOR.f90
${MODULES_DIR}/M_BUR_SC.f90
${MODULES_DIR}/M_Bur.f90
${MODULES_DIR}/M_CAV.f90
${MODULES_DIR}/M_CAVProp.F90
${MODULES_DIR}/M_CAV_SC.f90
${MODULES_DIR}/M_CF-TF.f90
${MODULES_DIR}/m_cleanstop.f90
${MODULES_DIR}/M_COR.f90
${MODULES_DIR}/M_COR_SC.f90
${MODULES_DIR}/M_COR_Variant.f90
${MODULES_DIR}/M_CVH.f90
${MODULES_DIR}/M_CVHFP.f90
${MODULES_DIR}/M_CVH_SC.f90
${MODULES_DIR}/M_Const.f90
${MODULES_DIR}/M_DCH.f90
${MODULES_DIR}/M_DCH_SC.f90
${MODULES_DIR}/M_Debug.F90
${MODULES_DIR}/M_DefaultFlagGlobals.f90
${MODULES_DIR}/M_dif2.f90
${MODULES_DIR}/M_DisplayConfiguration.F90
${MODULES_DIR}/M_Drop.f90
${MODULES_DIR}/M_EDF.f90
${MODULES_DIR}/M_ESF.f90
${MODULES_DIR}/M_ESF_SC.f90
${MODULES_DIR}/M_EXEC.f90
${MODULES_DIR}/m_execrtn.f90
${MODULES_DIR}/M_FDI.f90
${MODULES_DIR}/M_FDI_SC.f90
${MODULES_DIR}/M_FP.f90
${MODULES_DIR}/M_H2O.f90
${MODULES_DIR}/M_H2OD1.f90
${MODULES_DIR}/M_H2OD2.f90
${MODULES_DIR}/M_H2OD3.f90
${MODULES_DIR}/M_H2OD4.f90
${MODULES_DIR}/M_H2O_SC.f90
${MODULES_DIR}/M_HS.f90
${MODULES_DIR}/M_HS_SC.f90
${MODULES_DIR}/M_Input.f90
${MODULES_DIR}/M_isnan.f90
${MODULES_DIR}/M_kind.f90
${MODULES_DIR}/M_MP.f90
${MODULES_DIR}/M_MatCVH.f90
${MODULES_DIR}/M_MatFP.f90
${MODULES_DIR}/M_Matrix.f90
${MODULES_DIR}/M_Melcor.F90
${MODULES_DIR}/M_MELCOR-MACCS.F90
${MODULES_DIR}/M_NCG.f90
${MODULES_DIR}/M_NCG_SC.f90
${MODULES_DIR}/M_Package.f90
${MODULES_DIR}/m_packagertn.f90
${MODULES_DIR}/M_parallel.f90
${MODULES_DIR}/M_Plot.f90
${MODULES_DIR}/M_PreFormat.f90
${MODULES_DIR}/M_PreProcess.F90
${MODULES_DIR}/M_RN1.F90
${MODULES_DIR}/M_RN1_SC.f90
${MODULES_DIR}/m_RstGlobals.f90
${MODULES_DIR}/M_RW_Restart.f90
${MODULES_DIR}/M_SHsupport.f
${MODULES_DIR}/M_SPR.f90
${MODULES_DIR}/M_SPR_SC.f90
${MODULES_DIR}/M_SouCVH.f90
${MODULES_DIR}/M_StrCmp.f90
${MODULES_DIR}/M_StrUp.f90
${MODULES_DIR}/M_TP.f90
${MODULES_DIR}/M_Table.f90
${MODULES_DIR}/M_timer.f90
${MODULES_DIR}/M_Values.f90
${MODULES_DIR}/M_isnan.f90
${MODULES_DIR}/M_util.F90
${MODULES_DIR}/m_easymessage.F90
#
# files from here down copied in from other directories
#
${SNAP_DIR}/CSnapFacesM.f90
${DCH_DIR}/DCH_RW.F90
${DCH_DIR}/ElemDB.F90
${UTIL_DIR}/ExecSuspend.f90
${UTIL_DIR}/FileRoutines.f90
${UTIL_DIR}/OutputTiming.f90
${EXEC_DIR}/replace.f90
${UTIL_DIR}/string.f90
${SNAP_DIR}/SnapGlobal.f90
${UTIL_DIR}/PARDISO3_NSI.f90
)
ADD_LIBRARY(modules ${SRCS})
target_link_libraries(modules bonus h2c rn1 rn2)
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Fortran 90 modules not rebuilt
On Nov 16, 2010, at 2:05 PM, Belcourt, K. Noel wrote: On Nov 16, 2010, at 1:59 PM, Brad King wrote: On 11/16/2010 01:11 PM, K. Noel Belcourt wrote: I've attached my project's top-level Makefile. I'm trying to force all the modules in the project to build first so I created a single library called modules that contains all my Fortran 90 module files. I'm invoking the Makefile explicitly passing the modules as the target to build (so I can build a clean project in two steps: make modules ; make) The Fortran module dependencies implementation is hidden inside the Makefile generators. There is no API to access any of its timestamp files or scanning rules. What's interesting is that in a project that's fully update to date, running the make modules command gives this curious output: S896822:tools kbelco$ make modules [ 16%] Built target util [ 19%] Built target tp [ 25%] Built target spr [ 35%] Built target rn2 [ 61%] Built target rn1 [ 61%] Built target mp [100%] Built target modules which is the same list of libraries in these SUBDIRS commands in the top-level CMakeLists.txt file (in reverse order). There's a single library in each of these subdirs of the same lower-cased name. ... SUBDIRS(Modules) SUBDIRS(MP) SUBDIRS(Rn1) SUBDIRS(RN2) SUBDIRS(SPR) SUBDIRS(TP) SUBDIRS(Util) So it looks like the subdirs command plays a role in this behavior. -- Noel ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Fortran 90 modules not rebuilt
2010/11/16 Belcourt, K. Noel kbe...@sandia.gov: On Nov 16, 2010, at 2:05 PM, Belcourt, K. Noel wrote: On Nov 16, 2010, at 1:59 PM, Brad King wrote: On 11/16/2010 01:11 PM, K. Noel Belcourt wrote: I've attached my project's top-level Makefile. I'm trying to force all the modules in the project to build first so I created a single library called modules that contains all my Fortran 90 module files. I'm invoking the Makefile explicitly passing the modules as the target to build (so I can build a clean project in two steps: make modules ; make) The Fortran module dependencies implementation is hidden inside the Makefile generators. There is no API to access any of its timestamp files or scanning rules. What's interesting is that in a project that's fully update to date, running the make modules command gives this curious output: S896822:tools kbelco$ make modules [ 16%] Built target util [ 19%] Built target tp [ 25%] Built target spr [ 35%] Built target rn2 [ 61%] Built target rn1 [ 61%] Built target mp [100%] Built target modules which is the same list of libraries in these SUBDIRS commands in the top-level CMakeLists.txt file (in reverse order). Is there any reason you are using SUBDIRS instead of ADD_SUBDIRECTORY? SUBDIRS is deprecated and as far as I remember it has a different search-ordering than add_subdirectory There's a single library in each of these subdirs of the same lower-cased name. ... SUBDIRS(Modules) SUBDIRS(MP) SUBDIRS(Rn1) SUBDIRS(RN2) SUBDIRS(SPR) SUBDIRS(TP) SUBDIRS(Util) So it looks like the subdirs command plays a role in this behavior. try replacing your SUBDIRS with add_subdirectory. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Fortran 90 modules not rebuilt
On 11/16/2010 04:24 PM, Belcourt, K. Noel wrote: which is the same list of libraries in these SUBDIRS commands in the top-level CMakeLists.txt file (in reverse order). There's a single library in each of these subdirs of the same lower-cased name. ... SUBDIRS(Modules) SUBDIRS(MP) SUBDIRS(Rn1) SUBDIRS(RN2) SUBDIRS(SPR) SUBDIRS(TP) SUBDIRS(Util) So it looks like the subdirs command plays a role in this behavior. Is this built on a case-insensitive filesystem by any chance? -Brad ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Fortran 90 modules not rebuilt
On Nov 16, 2010, at 2:50 PM, Brad King wrote: On 11/16/2010 04:24 PM, Belcourt, K. Noel wrote: which is the same list of libraries in these SUBDIRS commands in the top-level CMakeLists.txt file (in reverse order). There's a single library in each of these subdirs of the same lower-cased name. ... SUBDIRS(Modules) SUBDIRS(MP) SUBDIRS(Rn1) SUBDIRS(RN2) SUBDIRS(SPR) SUBDIRS(TP) SUBDIRS(Util) So it looks like the subdirs command plays a role in this behavior. Is this built on a case-insensitive filesystem by any chance? I get the same behavior on HFS+ Journaled on my Mac and my RHEL5 Linux blade. -- Noel ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Fortran 90 modules not rebuilt
On Nov 16, 2010, at 2:48 PM, Eric Noulard wrote: 2010/11/16 Belcourt, K. Noel kbe...@sandia.gov: On Nov 16, 2010, at 2:05 PM, Belcourt, K. Noel wrote: On Nov 16, 2010, at 1:59 PM, Brad King wrote: On 11/16/2010 01:11 PM, K. Noel Belcourt wrote: I've attached my project's top-level Makefile. I'm trying to force all the modules in the project to build first so I created a single library called modules that contains all my Fortran 90 module files. I'm invoking the Makefile explicitly passing the modules as the target to build (so I can build a clean project in two steps: make modules ; make) The Fortran module dependencies implementation is hidden inside the Makefile generators. There is no API to access any of its timestamp files or scanning rules. What's interesting is that in a project that's fully update to date, running the make modules command gives this curious output: S896822:tools kbelco$ make modules [ 16%] Built target util [ 19%] Built target tp [ 25%] Built target spr [ 35%] Built target rn2 [ 61%] Built target rn1 [ 61%] Built target mp [100%] Built target modules which is the same list of libraries in these SUBDIRS commands in the top-level CMakeLists.txt file (in reverse order). Is there any reason you are using SUBDIRS instead of ADD_SUBDIRECTORY? No, didn't know about this SUBDIRS is deprecated and as far as I remember it has a different search-ordering than add_subdirectory Good to know. try replacing your SUBDIRS with add_subdirectory. Will do. -- Noel ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Fortran 90 modules not rebuilt
On Nov 16, 2010, at 2:48 PM, Eric Noulard wrote: 2010/11/16 Belcourt, K. Noel kbe...@sandia.gov: On Nov 16, 2010, at 2:05 PM, Belcourt, K. Noel wrote: On Nov 16, 2010, at 1:59 PM, Brad King wrote: On 11/16/2010 01:11 PM, K. Noel Belcourt wrote: I've attached my project's top-level Makefile. I'm trying to force all the modules in the project to build first so I created a single library called modules that contains all my Fortran 90 module files. I'm invoking the Makefile explicitly passing the modules as the target to build (so I can build a clean project in two steps: make modules ; make) The Fortran module dependencies implementation is hidden inside the Makefile generators. There is no API to access any of its timestamp files or scanning rules. What's interesting is that in a project that's fully update to date, running the make modules command gives this curious output: S896822:tools kbelco$ make modules [ 16%] Built target util [ 19%] Built target tp [ 25%] Built target spr [ 35%] Built target rn2 [ 61%] Built target rn1 [ 61%] Built target mp [100%] Built target modules which is the same list of libraries in these SUBDIRS commands in the top-level CMakeLists.txt file (in reverse order). Is there any reason you are using SUBDIRS instead of ADD_SUBDIRECTORY? SUBDIRS is deprecated and as far as I remember it has a different search-ordering than add_subdirectory try replacing your SUBDIRS with add_subdirectory. Same exact behavior with add_subdirectory. -- Noel ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Fortran 90 modules not rebuilt
On 11/16/2010 04:52 PM, Belcourt, K. Noel wrote: On Nov 16, 2010, at 2:50 PM, Brad King wrote: On 11/16/2010 04:24 PM, Belcourt, K. Noel wrote: which is the same list of libraries in these SUBDIRS commands in the top-level CMakeLists.txt file (in reverse order). There's a single library in each of these subdirs of the same lower-cased name. ... SUBDIRS(Modules) SUBDIRS(MP) SUBDIRS(Rn1) SUBDIRS(RN2) SUBDIRS(SPR) SUBDIRS(TP) SUBDIRS(Util) So it looks like the subdirs command plays a role in this behavior. Is this built on a case-insensitive filesystem by any chance? I get the same behavior on HFS+ Journaled on my Mac and my RHEL5 Linux blade. Run make -d to get debugging output. It is *very* verbose but can tell you why make chooses to run certain rules. -Brad ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] header files with visual studio
Michael Jackson said the following on 11/15/2010 11:56 AM: Ahh. It is a bit clearer the tract you are taking. What I am suggesting is that you only have to run the scanner once and keep the results in CMake syntax files so that CMake can just simply re-use the list. As you add headers during development you can add headers to the lists that were generated. It is the first big lump of headers which is the daunting task. After that general maintenance of the CMake files is simple and straight forward. For example in the folder: +- Solution | +- Target 1 | | +- Sources | | +- Headers you can have a file Headers.cmake which contains set (TARGET_1_HEADERS foo.h bar.h other.h) which can be generated once by a script. And in the CMakelists.txt file for Target 1 you can have: include (Headers/Headers.cmake) It's not nearly that simple; Target1 might be the login server, which uses header files from login/, chat/, etc, etc, etc. And these dependencies change frequently. The primary purpose is not to provide an SCM list of header files, but an active dependency list of header files so that IDE functions like search this target only work. Our source layout has many modules, but module != target. Any given target will have both source and header files from numerous modules/folders. Sure, everytime we alter the #Include chain we're going to have to rebuild the project files from the CMakeLists, but with per-target dependency-generated header lists ... It becomes worth it. - Oliver ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] VS solution folder puts first project last
Has anyone else noticed situations where VS puts the first project (as determined alphabetically) in a project folder as the last project? CMakePredefinedTargets -- PACKAGE -- RUN_TESTS -- ZERO_CHECK -- INSTALL I'm using VS 2008 SP 1 with CMake 2.8.3. I've verified this with a simple project and my own production project. 2.8.3 release does this 2.8.3 RC3 does 2.8.3 RC2 does 2.8.3 RC1 does But this is strange, because I know I have a VS solution that was generated with RC 2 which was and still is fine. Thanks, James ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Compiling header files
Hm, it works correctly in Linux, but I still get a bunch of
error LNK2019: unresolved external symbol
errors in Windows.
The only difference I see is that the .lib file gets created in a
subdirectory of bin/
bin/Debug/OSC.lib (or bin/Release/OSC.lib)
vs the .a file which gets created in bin directly:
bin/OSC.a
Does something have to be done differently because of this? I guessed
no, because I thought it would have complained that it couldn't find
the OSC library rather than just produce linker errors.
Here is the CMakeLists.txt file:
cmake_minimum_required(VERSION 2.6)
PROJECT(TestOSC)
INCLUDE_DIRECTORIES(${CMAKE_SOURCE_DIR})
IF(WIN32)
set(SystemTypePath ip/win32)
ELSE(WIN32)
set(SystemTypePath ip/posix)
ENDIF(WIN32)
ADD_LIBRARY(OSC
ip/IpEndpointName.cpp
${SystemTypePath}/NetworkingUtils.cpp
${SystemTypePath}/UdpSocket.cpp
osc/OscPrintReceivedElements.cpp
osc/OscReceivedElements.cpp
osc/OscTypes.cpp
osc/OscOutboundPacketStream.cpp
)
ADD_EXECUTABLE(SimpleReceive examples/SimpleReceive.cpp)
TARGET_LINK_LIBRARIES(SimpleReceive OSC)
Everything look ok? Any thoughts?
Thanks,
David
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Compiling header files
On 11/16/2010 7:19 PM, David Doria wrote: Hm, it works correctly in Linux, but I still get a bunch of error LNK2019: unresolved external symbol What symbols? Try running dumpbin /symbols OSC.lib. Also use VS IDE to make sure the library is listed. Everything look ok? Any thoughts? Looks OK, but there is not enough information to debug this, could be many different issues at this point Does the code build on Win32 without CMake? What symbols are undefined? Where should they be defined? What symbols are in the .lib that is created? etc, etc... -Bill ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Compiling header files
Also use VS IDE to make sure the library is listed. The library is indeed listed in Additional Dependencies of the linker for the executable target. What symbols? Try running dumpbin /symbols OSC.lib. I figured it out - I had to link to winmm to get the symbol: symbol __imp__timeGetTime and Ws2_32 to get several symbols like: symbol __imp__ht...@4 I have never developed in Windows - I didn't know I needed to link to additional libraries sometimes. Now I know. Thanks for all of the pointers! David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] BundleUtilities
Is the goal simply to copy
...VTK/bin/libvtkHybrid.a
into the package?
I tried this:
INSTALL(CODE \${VTK_DIR}/bin/libvtkHybrid.a)
But I get:
Parse error. Expected a command name, got unquoted argument with text
${VTK_DIR}/bin/libvtkHybrid.a.
I made a home for this here:
http://www.vtk.org/Wiki/CMake/CPack/BundleUtilities/Examples/Linux/VTK
if anyone has a better suggestion.
David
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] BundleUtilities
On Tue, Nov 16, 2010 at 10:15:28PM -0500, David Doria wrote:
Is the goal simply to copy
...VTK/bin/libvtkHybrid.a
into the package?
I tried this:
INSTALL(CODE \${VTK_DIR}/bin/libvtkHybrid.a)
More like:
INSTALL(FILES ${VTK_DIR}/bin/libvtkHybrid.a)
tyler
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] How to install openbabel python bindings by using the new cmake installer (problem selecting a particular python version).
On 11/13/2010 03:08 PM, Marcus D. Hanwell wrote:
On Nov 13, 2010, at 8:57 AM, Michael Hertling wrote:
On 11/12/2010 02:13 PM, Hector Martinez-Seara wrote:
Dear all,
I'm trying to install openbabel in linux which in its last version
(2.3.0) uses cmake installer. I haven't been able to compile it with
biddings with python 3.1 when using the -DPYTHON_BINDINGS=ON option. I
have python 2.7 and 3.1 installed in my system and the python command
points to python 3.1. Still cmake only select python 2.7 despite it is
not set as preferred in my system in any way. I have made a small
search and I have seen that there is a lot of troubles selecting
python 3 with cmake. Most of the information was very technical and
honestly I'm not sure if there was any solution at the end.
AFAIK, the FindPython{Interp,Libs}.cmake modules are currently not
capable to find Python 3, so you should focus on a manual approach
at the moment, see below. With the scheduling of issue 8396 for the
2.8.4 roadmap, there's a perpective for the availability of version-
or pattern-aware find functions, so maybe, it is possible to improve
the find modules w.r.t. version selection in the near or medium term.
This is certainly something I would like to address before the 2.8.4 release,
but as you said there is no Python 3 awareness right now in the find modules.
Do the Open Babel Python modules work in Python 3? I work on that project,
and was not aware that Python 3 support was there, but do not work much on
the bindings.
On occasion of Hector's inquiry, I've just taken a look at Open Babel's
CMakeLists.txt files to see how they could possibly be made not search
for a Python 2 installation, but I don't know if it generally works
with Python 3. Perhaps, Hector can provide some information.
My question is rather easy:
a) Is there any way to force a specific python version (3.1) from the
cmake command line?
You might try to set the PYTHON_EXECUTABLE, PYTHON_INCLUDE_DIR and
PYTHON_LIBRARY variables to appropriate values for your Python 3.1
installation on the command line, i.e. by use of the -D option or
-C along with a prepared script. AFAICS, defining these variables
makes the FindPython{Interp,Libs}.cmake modules not look for the
interpreter, the include directory and the library by themselves,
so you possibly get by without any further modifications, but I
have not yet tested this with Open Babel.
or b) Is there variable which I could export, e.g. CC=gcc4.5, to force
python to select the python version I want?
None I'm aware of, but - as stated above - there're some undertakings
in the near future that might result in a comprehensive and flexible
FindPython.cmake module which receives the requested version through
FIND_PACKAGE()'s version parameter, including version 3.
That would certainly be the ideal solution.
Yes, absolutely, and I'm hopeful that addressing 8396 will pave the
way for this and related concerns. My vision of the objectives are:
- Instead of just considering FIND_LIBRARY(), one should enhance all
find functions, i.e. FIND_{LIBRARY,PROGRAM,FILE,PATH}(), as James
Bigler has proposed in issue 10856. In particular for Python, one
needs improved FIND_PROGRAM() and FIND_PATH() functions to search
for the versioned interpreter executables and module directories.
- Instead of implementing support for version selection, one should
add general regex pattern matching as proposed in 10856, too. IMO,
pattern matching does suit much better to the find functions than
version selection, is universally useful on its own and has been
requested several times before.
- Pattern-aware find functions should just return a list of matching
candidates whereas the selection of a specific version may be done
by a function implemented in CMake's scripting language, and this
function might use the VERSION_EQUAL/VERSION_GREATER/VERSION_LESS/
VERSION_GREATER_OR_EQUAL/VERSION LESS_OR_EQUAL parameters proposed
by Philip Lowman for FIND_LIBRARY().
- The enhanced find functions should be used along with that version
selection function to write a FindPython.cmake which makes use of
FIND_PACKAGE()'s version specification facility and is capable to
handle Python 2 and 3 in an equal manner.
- Finally, this advancement should be used to improve certain find
modules currently containing hardcoded version numbers, e.g. the
Tcl/Tk ones or FindPNG.cmake. Hence, the FIND_PACKAGE() version
parameter could be used to select a specific version, and those
modules' related need of repetitive maintenance vanishes. By
the way, issue 10718 would most probably become obsolete.
Of course, I'd be interested in opinions and comments on this topic.
Regards,
Michael
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ
Re: [CMake] VS solution folder puts first project last
Am Mittwoch, 17. November 2010 schrieb James Bigler: Has anyone else noticed situations where VS puts the first project (as determined alphabetically) in a project folder as the last project? Yes, I have seen this when using the new FOLDER property for targets. I see this behaviour within the folders. Eike signature.asc Description: This is a digitally signed message part. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[Cmake-commits] CMake branch, master, updated. v2.8.3-56-gf4f3c9f
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via f4f3c9ff493e41d10f31d8b143e396516311f6c2 (commit) via 1e26f7c68b9cc1bbaf173cb6a7c6137bb2d829f8 (commit) from e7674ae1f05e78314ab7419bb5577a5bfce41234 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f4f3c9ff493e41d10f31d8b143e396516311f6c2 commit f4f3c9ff493e41d10f31d8b143e396516311f6c2 Merge: e7674ae 1e26f7c Author: David Cole david.c...@kitware.com AuthorDate: Tue Nov 16 14:45:58 2010 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Nov 16 14:45:58 2010 -0500 Merge topic 'suppress-dashboard-warnings' 1e26f7c Suppress loop was vectorized warnings. --- Summary of changes: CTestCustom.cmake.in |1 + 1 files changed, 1 insertions(+), 0 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v2.8.3-58-gcaf680c
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via caf680c4d7115fb5e6e16f4a738a7f49346b5de3 (commit) via a39ee97c6cfe19e2170e0e5eccbfb8b1be3b1f48 (commit) from f4f3c9ff493e41d10f31d8b143e396516311f6c2 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=caf680c4d7115fb5e6e16f4a738a7f49346b5de3 commit caf680c4d7115fb5e6e16f4a738a7f49346b5de3 Merge: f4f3c9f a39ee97 Author: David Cole david.c...@kitware.com AuthorDate: Tue Nov 16 14:46:04 2010 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Nov 16 14:46:04 2010 -0500 Merge topic 'FixFindQt3REQUIRED' a39ee97 Fix #11421: FindQt3.cmake doesn't honor the REQUIRED keyword --- Summary of changes: Modules/FindQt3.cmake |6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v2.8.3-61-gb61c5be
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via b61c5be3d79bd890fc5d56ac8313bb84897cc1c1 (commit) via 22aec406e6df44dcde0fa98e694455306febeaf1 (commit) via 3d79e7d58ca0ebb63ffaba4ed16c1ea8c6bcf91d (commit) from caf680c4d7115fb5e6e16f4a738a7f49346b5de3 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b61c5be3d79bd890fc5d56ac8313bb84897cc1c1 commit b61c5be3d79bd890fc5d56ac8313bb84897cc1c1 Merge: caf680c 22aec40 Author: David Cole david.c...@kitware.com AuthorDate: Tue Nov 16 14:46:12 2010 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Nov 16 14:46:12 2010 -0500 Merge topic 'vs-intel-RuntimeLibrary' 22aec40 Set Intel .vfproj RuntimeLibrary attribute 3d79e7d Fix Intel .vfproj SubSystem attribute values --- Summary of changes: Source/cmLocalVisualStudio7Generator.cxx |7 +++- Source/cmVisualStudioGeneratorOptions.cxx | 51 + Source/cmVisualStudioGeneratorOptions.h |5 +++ 3 files changed, 61 insertions(+), 2 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v2.8.3-71-gc172ffe
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via c172ffef061c1bf412389fdf01275cf91aa2ff79 (commit) via 53e76c8f126fd2480c560cf2bb46a93eabbc91fa (commit) via 34e1ac2489778a854c3ffaa9c141a9a70416a47e (commit) from e19fa08ac9df21826b5427c4d4442a5eee45b9f9 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c172ffef061c1bf412389fdf01275cf91aa2ff79 commit c172ffef061c1bf412389fdf01275cf91aa2ff79 Merge: e19fa08 53e76c8 Author: David Cole david.c...@kitware.com AuthorDate: Tue Nov 16 14:46:30 2010 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Nov 16 14:46:30 2010 -0500 Merge topic 'cray-compiler' 53e76c8 Teach CMake about Cray C, C++, and Fortran compilers 34e1ac2 Create Fortran info variables for .mod behavior --- Summary of changes: Modules/CMakeCCompilerId.c.in|3 +++ Modules/CMakeCXXCompilerId.cpp.in|3 +++ Modules/CMakeFortranCompilerId.F.in |2 ++ Modules/Compiler/Cray-C.cmake|1 + Modules/Compiler/Cray-CXX.cmake |1 + Modules/Compiler/Cray-Fortran.cmake |4 Source/cmDocumentVariables.cxx | 23 +++ Source/cmMakefileTargetGenerator.cxx | 13 + 8 files changed, 50 insertions(+), 0 deletions(-) create mode 100644 Modules/Compiler/Cray-C.cmake create mode 100644 Modules/Compiler/Cray-CXX.cmake create mode 100644 Modules/Compiler/Cray-Fortran.cmake hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v2.8.3-75-g164b11d
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 164b11deb735e33e9dd14becac71288689617dda (commit) via 74e49aa441e4805b40b5e61348501f9143a5defe (commit) from cb727a20df7414c3c1d1f75153f73f93abe6ca07 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=164b11deb735e33e9dd14becac71288689617dda commit 164b11deb735e33e9dd14becac71288689617dda Merge: cb727a2 74e49aa Author: David Cole david.c...@kitware.com AuthorDate: Tue Nov 16 14:46:46 2010 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Nov 16 14:46:46 2010 -0500 Merge topic 'EP-extra-generator' 74e49aa BUG 11451 - pass CMAKE_EXTRA_GENERATOR down. --- Summary of changes: Modules/ExternalProject.cmake |7 ++- 1 files changed, 6 insertions(+), 1 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v2.8.3-76-gb541b12
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via b541b1213ac4bf95a186d9fa753ba2566e598d06 (commit) from 164b11deb735e33e9dd14becac71288689617dda (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b541b1213ac4bf95a186d9fa753ba2566e598d06 commit b541b1213ac4bf95a186d9fa753ba2566e598d06 Author: KWSys Robot kwro...@kitware.com AuthorDate: Wed Nov 17 00:01:05 2010 -0500 Commit: KWSys Robot kwro...@kitware.com CommitDate: Wed Nov 17 00:10:02 2010 -0500 KWSys Nightly Date Stamp diff --git a/Source/kwsys/kwsysDateStamp.cmake b/Source/kwsys/kwsysDateStamp.cmake index a47550b..0cb98f1 100644 --- a/Source/kwsys/kwsysDateStamp.cmake +++ b/Source/kwsys/kwsysDateStamp.cmake @@ -18,4 +18,4 @@ SET(KWSYS_DATE_STAMP_YEAR 2010) SET(KWSYS_DATE_STAMP_MONTH 11) # KWSys version date day component. Format is DD. -SET(KWSYS_DATE_STAMP_DAY 16) +SET(KWSYS_DATE_STAMP_DAY 17) --- Summary of changes: Source/kwsys/kwsysDateStamp.cmake |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
