[cmake-developers] [CMake 0011722]: CMake.desktop: wrong Exec field
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=11722 == Reported By:arrowdodger Assigned To: == Project:CMake Issue ID: 11722 Category: QtDialog Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2011-01-19 05:27 EST Last Modified: 2011-01-19 05:27 EST == Summary:CMake.desktop: wrong Exec field Description: cmake-gui uses a path to build as it's argument, not CMakeCache.txt itself. So, %f should be replaced with %d. Steps to Reproduce: Using Dolphin or any other file manager program try to open CMakeCache.txt file using CMake program. It will open last used project, not the excepted one. == Issue History Date ModifiedUsername FieldChange == 2011-01-19 05:27 arrowdodgerNew Issue == ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0011723]: eclipse build
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11723
==
Reported By:Galeazzi
Assigned To:
==
Project:CMake
Issue ID: 11723
Category: CMake
Reproducibility:always
Severity: minor
Priority: normal
Status: new
==
Date Submitted: 2011-01-19 11:58 EST
Last Modified: 2011-01-19 11:58 EST
==
Summary:eclipse build
Description:
suppose I have a project with:
add_subdirectory(path/lib1 ${CMAKE_CURRENT_BINARY_DIR}/ib1)
when I change a source of lib1 and click on build over the eclipse project,
eclipse doesn't build anything.
If I change a source of the main project it launches the build correctly.
I also tried to test the same thing with a simple MinGW Makefile (instead of
Eclipse CDT 4 - MinGW Makefile) and it works properly in both two cases.
Steps to Reproduce:
Just create a project with the same structure above
==
Issue History
Date ModifiedUsername FieldChange
==
2011-01-19 11:58 Galeazzi New Issue
==
___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0011725]: CMAKE_USER_MAKE_RULES_OVERRIDE path no longer works if unqualified
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11725
==
Reported By:Daniel R. Gomez
Assigned To:
==
Project:CMake
Issue ID: 11725
Category: CMake
Reproducibility:always
Severity: minor
Priority: normal
Status: new
==
Date Submitted: 2011-01-19 17:03 EST
Last Modified: 2011-01-19 17:03 EST
==
Summary:CMAKE_USER_MAKE_RULES_OVERRIDE path no longer works
if unqualified
Description:
At the top of my top-level CMakeLists.txt file, I have
SET(CMAKE_USER_MAKE_RULES_OVERRIDE CMakeCommon.txt)
My CMakeCommon.txt file lives right alongside the aforementioned listfile, and
things worked dandily like this for the last few years (up to 2.8.1).
With 2.8.3, however, I get this:
(cut here)
-- The C compiler identification is Intel
-- Using predefined Intel compiler flags
-- Check for working C compiler: C:/Program Files
(x86)/Intel/Compiler/C++/9.1/EM64T/Bin/icl.exe
CMake Error at
X:/freeport/arch/win64_icl_mt/share/cmake-2.8/Modules/CMakeCInformation.cmake:79
(INCLUDE):
include could not find load file:
CMakeCommon.txt
Call Stack (most recent call first):
CMakeLists.txt:3 (PROJECT)
(cut here)
Things work again if I edit the line to
SET(CMAKE_USER_MAKE_RULES_OVERRIDE ${CMAKE_SOURCE_DIR}/CMakeCommon.txt)
However, I believe the previous behavior was reasonable, where this variable
would implicitly be interpreted relative to ${CMAKE_SOURCE_DIR} rather than
anywhere else.
==
Issue History
Date ModifiedUsername FieldChange
==
2011-01-19 17:03 Daniel R. GomezNew Issue
==
___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] [CMake] xcode project and static library dependencies
BTW, it might make more sense to move this to the cmake-developers mailing
list.
I've transfered this thread to the developer list. See below for continuation..
On Jan 18, 2011, at 12:42 PM, Bill Hoffman wrote:
On 1/18/2011 2:40 PM, Brad King wrote:
On 1/18/2011 2:12 PM, Nick Kledzik wrote:
When I use cmake to create a Makefile, the resulting main executable
is placed in the build directory tree next to the Makefile.
This is where CMake puts files in single-configuration generators.
When I use cmake to create a xcode project, the resulting main
executable is placed in a subdirectory named Debug of the build
directory tree.
This is where CMake puts files in multi-configuration generators.
Both of the above are expected default behaviors. Both can be
changed by CMake properties like RUNTIME_OUTPUT_DIRECTORY and
its per-configuration equivalent. All CMake generators must
honor these.
None of these locations are the native location
where Xcode would put a build result.
Xcode has settings like CONFIGURATION_BUILD_DIR to control
where the build outputs go. This already works. Is there
some reason your changes cannot use these?
My understanding is that the main problem with the current generator
is all the extra build phases and OTHER_LDFLAGS stuff used to deal
with link line ordering and static libraries. This is what Bill
summarized:
On 1/13/2011 3:41 PM, Bill Hoffman wrote:
- have a static library show up more than once on a link line
- be able to specify the order of static libraries on the link line
- be able to relink and executable when a static library that it
depends on is rebuilt.
I'm more interested in a solution to implementation issues like these
than in interface details like where output files go.
-Brad
So, for Xcode and VS IDE, CMake will place things in directories like Debug,
Release.
For example, you should get something like this:
${RUNTIME_OUTPUT_DIRECTORY}/Debug/myexe
Xcode does support building multiple configurations like Debug, Release, etc.
Where is the native location for those files?
As I said, it is per-user xcode settings. You cannot infer the location from
source tree cmake has access to.
At build time, the location is known within xcode. So, I added a copy-file
phase to have xocde copy the resulting binary from the native location to the
standard location the cmake expects. There is little overhead for this.
I've now have a patch which:
1) preserves link order
2) builds libraries into the xcode native location
4) removes pre and post shell script phases previously used to fix dependency
problems
3) xcode projects now have proper dependencies
WIth this cmake patch, I can build CMake.xcodeproject, open it in xcode,
build-all, set the current target to be cmake, make a source change, hit
build, and have xcode just compile that one file, re-archive the library, then
re-link cmake tool. I also debugged all this in Xcode by setting arguments for
the cmake tool and hitting the build-and-debug within xcode!
Attached is the patch from cmake-2.8.3 sources:
cmake-xcode.patch
Description: Binary data
This cmake also creates an xcode project that builds LLVM. It is still not
quite optimal because there are a bunch of cases where custom rules cause a
custom make file to be generated which is executed from within xcode via a
shell script phase. Xcode does not now which files the script might modify, so
xcode has to be conservative and re-check all timestamps. There are ways to
add custom scripts with specified input and output files in xcode. I may get
to fixing that someday...
How does one run the test suite? I saw the instructions about building cmake
for make, then executing make Experimental. I did that and all 184 or 184
tests passed. But it looks like this is running the cmake generated makefiles
- not cmake generated xcode projects.
-Nick
___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] [CMake] xcode project and static library dependencies
On Wed, Jan 19, 2011 at 8:08 PM, Nick Kledzik kled...@apple.com wrote:
BTW, it might make more sense to move this to the cmake-developers mailing
list.
I've transfered this thread to the developer list. See below for
continuation..
On Jan 18, 2011, at 12:42 PM, Bill Hoffman wrote:
On 1/18/2011 2:40 PM, Brad King wrote:
On 1/18/2011 2:12 PM, Nick Kledzik wrote:
When I use cmake to create a Makefile, the resulting main executable
is placed in the build directory tree next to the Makefile.
This is where CMake puts files in single-configuration generators.
When I use cmake to create a xcode project, the resulting main
executable is placed in a subdirectory named Debug of the build
directory tree.
This is where CMake puts files in multi-configuration generators.
Both of the above are expected default behaviors. Both can be
changed by CMake properties like RUNTIME_OUTPUT_DIRECTORY and
its per-configuration equivalent. All CMake generators must
honor these.
None of these locations are the native location
where Xcode would put a build result.
Xcode has settings like CONFIGURATION_BUILD_DIR to control
where the build outputs go. This already works. Is there
some reason your changes cannot use these?
My understanding is that the main problem with the current generator
is all the extra build phases and OTHER_LDFLAGS stuff used to deal
with link line ordering and static libraries. This is what Bill
summarized:
On 1/13/2011 3:41 PM, Bill Hoffman wrote:
- have a static library show up more than once on a link line
- be able to specify the order of static libraries on the link line
- be able to relink and executable when a static library that it
depends on is rebuilt.
I'm more interested in a solution to implementation issues like these
than in interface details like where output files go.
-Brad
So, for Xcode and VS IDE, CMake will place things in directories like Debug,
Release.
For example, you should get something like this:
${RUNTIME_OUTPUT_DIRECTORY}/Debug/myexe
Xcode does support building multiple configurations like Debug, Release,
etc. Where is the native location for those files?
As I said, it is per-user xcode settings. You cannot infer the location from
source tree cmake has access to.
At build time, the location is known within xcode. So, I added a copy-file
phase to have xocde copy the resulting binary from the native location to
the standard location the cmake expects. There is little overhead for this.
I am still not sure why you need the extra copy. That is a concern.
If Xcode were to put things in a predictable place, we could just
have CMake look there, just like in VS when we look in the Debug,
Release, etc, directories.
I've now have a patch which:
1) preserves link order
2) builds libraries into the xcode native location
4) removes pre and post shell script phases previously used to fix dependency
problems
3) xcode projects now have proper dependencies
That sounds great.
WIth this cmake patch, I can build CMake.xcodeproject, open it in xcode,
build-all, set the current target to be cmake, make a source change, hit
build, and have xcode just compile that one file, re-archive the library,
then re-link cmake tool. I also debugged all this in Xcode by setting
arguments for the cmake tool and hitting the build-and-debug within xcode!
Attached is the patch from cmake-2.8.3 sources:
This cmake also creates an xcode project that builds LLVM. It is still not
quite optimal because there are a bunch of cases where custom rules cause a
custom make file to be generated which is executed from within xcode via a
shell script phase. Xcode does not now which files the script might modify,
so xcode has to be conservative and re-check all timestamps. There are ways
to add custom scripts with specified input and output files in xcode. I may
get to fixing that someday...
How does one run the test suite? I saw the instructions about building cmake
for make, then executing make Experimental. I did that and all 184 or 184
tests passed. But it looks like this is running the cmake generated
makefiles - not cmake generated xcode projects.
To run the tests, do this:
1. build your modified CMake
2. build a second CMake with the one from step 1, with -GXcode
3. run ./bin/Release/ctest -C Release from the binary tree of CMake.
That will use the Xcode generator for the tests, also will verify that
CMake itself can be built with your modified CMake.
So, something like this:
mkdir CMakeTest; cd CMakeTest
/path/to/your/modified/cmake/bin/cmake -GXcode ../CMake
/path/to/your/modified/cmake/bin/cmake --build . --config Release
./bin/Release/ctest
-Bill
___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Generating information for C++ tools in cmake (patch)
On Tue, Jan 18, 2011 at 11:08 AM, David Cole david.c...@kitware.com wrote: On Tue, Jan 18, 2011 at 1:53 PM, Brad King brad.k...@kitware.com wrote: On 1/18/2011 1:50 PM, Manuel Klimek wrote: Since this is a big integration style test, is it also possible to integrate a python test? (the whole test would fit into a few lines of python then) We'd prefer not to depend on python, but certainly a prototype in python would be a good start. -Brad ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers Brad's being polite when he says we'd prefer not to depend on python. CMake itself *will not* depend on python. And for any test that is expected to be run on all of our dashboard clients before it's accepted into CMake 'master', such a test cannot depend on python either. So the question is: do you want to run this test as part of the dashboard clients? I'm happy to comply with whatever decision you make, given the trade-off between maintainability of the test and dependency on python. Cheers, /Manuel ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[CMake] How to query compiler definitions?
Hello,
I know that some source code will only be needed in my example project if the
preprocessor symbol NDEBUG is not defined.
This is usual for conditional compilation. The corresponding bit of debug code
calls functions which are implemented in a few other source files.
Now I am looking for ways whether these files can be added on demand to the
build process.
I try to query the settings by a programming interface from CMake 2.8.3 on my
openSUSE 11.3 system.
get_directory_property(info COMPILE_DEFINITIONS)
message(STATUS info: ${info})
The corresponding display indicates that this variable is empty. I guess that
this fact should be interpreted also in the way that the specified property is
not defined in my situation.
Now I wonder why this approach does not work as expected. (A few definitions are
passed to my compiler of course.)
I would appreciate your advices.
Regards,
Markus
___
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 query compiler definitions?
On 01/19/2011 09:30 AM, SF Markus Elfring wrote:
Hello,
I know that some source code will only be needed in my example project
if the preprocessor symbol NDEBUG is not defined.
This is usual for conditional compilation. The corresponding bit of
debug code calls functions which are implemented in a few other source
files.
Now I am looking for ways whether these files can be added on demand to
the build process.
I try to query the settings by a programming interface from CMake 2.8.3
on my openSUSE 11.3 system.
get_directory_property(info COMPILE_DEFINITIONS)
message(STATUS info: ${info})
The corresponding display indicates that this variable is empty. I guess
that this fact should be interpreted also in the way that the specified
property is not defined in my situation.
Now I wonder why this approach does not work as expected. (A few
definitions are passed to my compiler of course.)
I would appreciate your advices.
Regards,
Markus
The NDEBUG flag is special and gets set by CMake for non-debug builds
automagically. Also, such an approach as you propose would work for
Makefile generators, but would completely fail for multi-config IDE
generators, such as Xcode or VisualStudio. Why don't you include the
check for NDEBUG in in your debug-sources? Like this:
debug-functions.c:
--8--
#ifndef NDEBUG
void some_debug_function(void)
{
/* whathever */
}
#endif
--8--
The time you'll waste compiling these files will be negligible, and it
would work with mult-config IDE's.
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
Re: [CMake] Problems with MinGW + BundleUtilities
The code I use to create the bundle is as followed
SET(DIRS ${QT_BINARY_DIR} ${QT_LIBRARY_DIR})
SET(APPS ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${PROJECT_NAME}.exe)
# Not working (Also when trying this in the INSTALL(CODE
# SET(APPS ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${PROJECT_NAME}.exe)
# SET(APPS ${CMAKE_INSTALL_PREFIX}/${PROJECT_NAME}.exe)
# SET(APPS \${CMAKE_INSTALL_PREFIX}/${PROJECT_NAME}.exe)
SET(PLUGINS plugins)
INSTALL(FILES ${QT_PLUGINS_DIR}/sqldrivers/qsqlited4.dll
DESTINATION ${PLUGINS}/sqldrivers COMPONENT ${PROJECT_NAME})
INSTALL(CODE
file(GLOB_RECURSE QTPLUGINS
\${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${PLUGINS}/sqldrivers/*${CMAKE_SHARED_LI
BRARY_SUFFIX}\)
include(BundleUtilities)
fixup_bundle(\${APPS}\ \\${QTPLUGINS}\ \${DIRS}\)
COMPONENT ${PROJECT_NAME})
The install command for the application is:
INSTALL(TARGETS ${PROJECT_NAME}
BUNDLE DESTINATION . COMPONENT ${PROJECT_NAME}
RUNTIME DESTINATION . COMPONENT ${PROJECT_NAME})
Thanks in advance
Best Regards
NoRulez
Von: David Cole [mailto:david.c...@kitware.com]
Gesendet: Mittwoch, 19. Jänner 2011 00:26
An: NoRulez
Cc: CMake MailingList
Betreff: Re: [CMake] Problems with MinGW + BundleUtilities
Providing code samples and/or copy/pasted output from doing your build would
be more effective.
I don't really know what you mean by give two destinations
On Tue, Jan 18, 2011 at 5:51 PM, NoRulez noru...@me.com wrote:
Thanks for the answer
I already added ${QT_LIBRARY_DIR} and ${QT_BINARY_DIR}, but if I give two
destinations, I get the error that it isn't a valid bundle.
Best Regards
NoRulez
Am 18.01.2011 um 23:43 schrieb David Cole david.c...@kitware.com:
On Windows, you have to tell fixup_bundle where to find the Qt dll's (and
the others) by passing in a list of directories as the last argument. Or,
alternatively, simply add those directories to the PATH as well.
HTH,
David
On Tue, Jan 18, 2011 at 4:34 PM, NoRulez noru...@me.com wrote:
Hello,
I build my Qt project successfully on linux/mac with the great
BundleUtilities.
On Windows the required Qt dlls and also libgcc_s_dw2-1.dll and
mingwm10.dll arent packaged.
The dumpbin.exe is in the path and the dumpbin.exe is under
C:\masm32\bin\dumpbin.exe
How can I solve this?
Thanks in advance
Best Regards
NoRulez
___
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
___
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 query compiler definitions?
Why don't you include the check for NDEBUG in in your debug-sources? This is the case already. The time you'll waste compiling these files will be negligible, and it would work with mult-config IDE's. I find this view debatable. I would appreciate if I can express in the build specification that a few source file are optional for the compilation because of this well-known preprocessor symbol. Regards, Markus ___ 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 query compiler definitions?
On 01/19/2011 09:50 AM, SF Markus Elfring wrote: Why don't you include the check for NDEBUG in in your debug-sources? This is the case already. The time you'll waste compiling these files will be negligible, and it would work with mult-config IDE's. I find this view debatable. I would appreciate if I can express in the build specification that a few source file are optional for the compilation because of this well-known preprocessor symbol. Regards, Markus But that's exactly the problem. For multi-config IDE's you *don't know* whether NDEBUG is defined or not at CMake-time. And AFAIK there's no way to specify that a source file is conditional on the build configuration. The only other way I can see how to handle this, is to create a static library (say debug_funcs) and then link that conditionally. E.g: --8-- add_library(debug_funcs STATIC EXCLUDE_FROM_ALL debug_funcs.c) add_executable(super super.c) target_link_libraries(super debug debug_funcs) --8-- This way, as I understand it, debug_funcs will only be built if the executable super links against it, which it only does for the Debug configuration. 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
Re: [CMake] check_function_exists frailty
2011/1/19 Jack Poulson jack.poul...@gmail.com:
I have no idea why this would occur, but with CMake 2.8.2 on x86_64 I'm
getting strange behavior with check_function_exists. Namely, if I perform
the sequence
set(CMAKE_REQUIRED_LIBRARIES ${MATH_LIBS})
check_function_exists(daxpy HAVE_DAXPY)
whether or not /usr/lib/libpthread.a or /usr/lib/libpthread.so is in the
list changes the answer, even though daxpy is defined in a completely
different library!
Output with libpthread.so:
--
MATH_LIBS=/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_scalapack_lp64.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_blacs_lp64.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_intel_lp64.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_intel_thread.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_core.a;/opt/intel/Compiler/11.1/072/lib/intel64/libguide.a;/opt/intel/Compiler/11.1/072/lib/intel64/libiomp5.a;/usr/lib/libpthread.so
-- Looking for daxpy
-- Looking for daxpy - found
Output with libpthread.a:
--
MATH_LIBS=/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_scalapack_lp64.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_blacs_lp64.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_intel_lp64.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_intel_thread.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_core.a;/opt/intel/Compiler/11.1/072/lib/intel64/libguide.a;/opt/intel/Compiler/11.1/072/lib/intel64/libiomp5.a;/usr/lib/libpthread.a
-- Looking for daxpy
-- Looking for daxpy - not found
Any ideas what would be causing this strange behavior? And while I'm on the
subject, should check_function_exist work with dynamic libraries? I had to
give up some portability and force find_library to search for the static MKL
libraries just to get the libpthread.so case to work.
I apologize in advance if I've missed something obvious...
May be you have an implicit dependency on dynamic pthread somewhere.
Are you using icc or gcc ?
As far as I remember check_function_exists is using try_compile.
May be you can try to run CMake with
--debug-trycompile and look into files
I don't remember where they are... but I'm sure someone will tell you that.
--
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] Problems with MinGW + BundleUtilities
And what is the value of DIRS?
On Wed, Jan 19, 2011 at 3:40 AM, NoRulez noru...@me.com wrote:
The code I use to create the bundle is as followed
SET(DIRS ${QT_BINARY_DIR} ${QT_LIBRARY_DIR})
SET(APPS ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${PROJECT_NAME}.exe)
# Not working (Also when trying this in the INSTALL(CODE
# SET(APPS ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${PROJECT_NAME}.exe)
# SET(APPS ${CMAKE_INSTALL_PREFIX}/${PROJECT_NAME}.exe)
# SET(APPS \${CMAKE_INSTALL_PREFIX}/${PROJECT_NAME}.exe)
SET(PLUGINS plugins)
INSTALL(FILES ${QT_PLUGINS_DIR}/sqldrivers/qsqlited4.dllDESTINATION
${PLUGINS}/sqldrivers COMPONENT ${PROJECT_NAME})
INSTALL(CODE
file(GLOB_RECURSE QTPLUGINS
\${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${PLUGINS}/sqldrivers/*
${CMAKE_SHARED_LIBRARY_SUFFIX}\)
include(BundleUtilities)
fixup_bundle(\${APPS}\ \\${QTPLUGINS}\ \${DIRS}\)
COMPONENT ${PROJECT_NAME})
The install command for the application is:
INSTALL(TARGETS ${PROJECT_NAME}
BUNDLE DESTINATION . COMPONENT ${PROJECT_NAME}
RUNTIME DESTINATION . COMPONENT ${PROJECT_NAME})
Thanks in advance
Best Regards
NoRulez
*Von:* David Cole [mailto:david.c...@kitware.com]
*Gesendet:* Mittwoch, 19. Jänner 2011 00:26
*An:* NoRulez
*Cc:* CMake MailingList
*Betreff:* Re: [CMake] Problems with MinGW + BundleUtilities
Providing code samples and/or copy/pasted output from doing your build
would be more effective.
I don't really know what you mean by give two destinations
On Tue, Jan 18, 2011 at 5:51 PM, NoRulez noru...@me.com wrote:
Thanks for the answer
I already added ${QT_LIBRARY_DIR} and ${QT_BINARY_DIR}, but if I give two
destinations, I get the error that it isn't a valid bundle.
Best Regards
NoRulez
Am 18.01.2011 um 23:43 schrieb David Cole david.c...@kitware.com:
On Windows, you have to tell fixup_bundle where to find the Qt dll's (and
the others) by passing in a list of directories as the last argument. Or,
alternatively, simply add those directories to the PATH as well.
HTH,
David
On Tue, Jan 18, 2011 at 4:34 PM, NoRulez noru...@me.com wrote:
Hello,
I build my Qt project successfully on linux/mac with the great
BundleUtilities.
On Windows the required Qt dll’s and also “libgcc_s_dw2-1.dll” and
“mingwm10.dll” aren’t packaged.
The dumpbin.exe is in the path and the dumpbin.exe is under
C:\masm32\bin\dumpbin.exe
How can I solve this?
Thanks in advance
Best Regards
NoRulez
___
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
___
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] Problems with MinGW + BundleUtilities
Never mind. It's QT_BINARY_DIR and QT_LIBRARY_DIR, right there in the first
line of code.
So add to that variable the actual directories where all of your dlls live
and it should work.
i.e. -- what directories are the following files in?
libgcc_s_dw2-1.dll
mingwm10.dll
They also need to be included in DIRS for fixup_bundle and get_prerequisites
to find them.
On Wed, Jan 19, 2011 at 5:21 AM, David Cole david.c...@kitware.com wrote:
And what is the value of DIRS?
On Wed, Jan 19, 2011 at 3:40 AM, NoRulez noru...@me.com wrote:
The code I use to create the bundle is as followed
SET(DIRS ${QT_BINARY_DIR} ${QT_LIBRARY_DIR})
SET(APPS ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${PROJECT_NAME}.exe)
# Not working (Also when trying this in the INSTALL(CODE
# SET(APPS ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${PROJECT_NAME}.exe)
# SET(APPS ${CMAKE_INSTALL_PREFIX}/${PROJECT_NAME}.exe)
# SET(APPS \${CMAKE_INSTALL_PREFIX}/${PROJECT_NAME}.exe)
SET(PLUGINS plugins)
INSTALL(FILES ${QT_PLUGINS_DIR}/sqldrivers/qsqlited4.dllDESTINATION
${PLUGINS}/sqldrivers COMPONENT ${PROJECT_NAME})
INSTALL(CODE
file(GLOB_RECURSE QTPLUGINS
\${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${PLUGINS}/sqldrivers/*
${CMAKE_SHARED_LIBRARY_SUFFIX}\)
include(BundleUtilities)
fixup_bundle(\${APPS}\ \\${QTPLUGINS}\ \${DIRS}\)
COMPONENT ${PROJECT_NAME})
The install command for the application is:
INSTALL(TARGETS ${PROJECT_NAME}
BUNDLE DESTINATION . COMPONENT ${PROJECT_NAME}
RUNTIME DESTINATION . COMPONENT ${PROJECT_NAME})
Thanks in advance
Best Regards
NoRulez
*Von:* David Cole [mailto:david.c...@kitware.com]
*Gesendet:* Mittwoch, 19. Jänner 2011 00:26
*An:* NoRulez
*Cc:* CMake MailingList
*Betreff:* Re: [CMake] Problems with MinGW + BundleUtilities
Providing code samples and/or copy/pasted output from doing your build
would be more effective.
I don't really know what you mean by give two destinations
On Tue, Jan 18, 2011 at 5:51 PM, NoRulez noru...@me.com wrote:
Thanks for the answer
I already added ${QT_LIBRARY_DIR} and ${QT_BINARY_DIR}, but if I give two
destinations, I get the error that it isn't a valid bundle.
Best Regards
NoRulez
Am 18.01.2011 um 23:43 schrieb David Cole david.c...@kitware.com:
On Windows, you have to tell fixup_bundle where to find the Qt dll's (and
the others) by passing in a list of directories as the last argument. Or,
alternatively, simply add those directories to the PATH as well.
HTH,
David
On Tue, Jan 18, 2011 at 4:34 PM, NoRulez noru...@me.com wrote:
Hello,
I build my Qt project successfully on linux/mac with the great
BundleUtilities.
On Windows the required Qt dll’s and also “libgcc_s_dw2-1.dll” and
“mingwm10.dll” aren’t packaged.
The dumpbin.exe is in the path and the dumpbin.exe is under
C:\masm32\bin\dumpbin.exe
How can I solve this?
Thanks in advance
Best Regards
NoRulez
___
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
___
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] Problems with MinGW + BundleUtilities
The two files are also in the QT_BINARY_DIR
The two directories (QT_BINARY_DIR and QT_LIBRARY_DIR ) are the directories
where the dlls are stored.
So, what should I do now to get it working?
Von: David Cole [mailto:david.c...@kitware.com]
Gesendet: Mittwoch, 19. Jänner 2011 11:23
An: NoRulez
Cc: CMake MailingList
Betreff: Re: [CMake] Problems with MinGW + BundleUtilities
Never mind. It's QT_BINARY_DIR and QT_LIBRARY_DIR, right there in the first
line of code.
So add to that variable the actual directories where all of your dlls live
and it should work.
i.e. -- what directories are the following files in?
libgcc_s_dw2-1.dll
mingwm10.dll
They also need to be included in DIRS for fixup_bundle and get_prerequisites
to find them.
On Wed, Jan 19, 2011 at 5:21 AM, David Cole david.c...@kitware.com wrote:
And what is the value of DIRS?
On Wed, Jan 19, 2011 at 3:40 AM, NoRulez noru...@me.com wrote:
The code I use to create the bundle is as followed
SET(DIRS ${QT_BINARY_DIR} ${QT_LIBRARY_DIR})
SET(APPS ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${PROJECT_NAME}.exe)
# Not working (Also when trying this in the INSTALL(CODE
# SET(APPS ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${PROJECT_NAME}.exe)
# SET(APPS ${CMAKE_INSTALL_PREFIX}/${PROJECT_NAME}.exe)
# SET(APPS \${CMAKE_INSTALL_PREFIX}/${PROJECT_NAME}.exe)
SET(PLUGINS plugins)
INSTALL(FILES ${QT_PLUGINS_DIR}/sqldrivers/qsqlited4.dll
DESTINATION ${PLUGINS}/sqldrivers COMPONENT ${PROJECT_NAME})
INSTALL(CODE
file(GLOB_RECURSE QTPLUGINS
\${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${PLUGINS}/sqldrivers/*${CMAKE_SHARED_LI
BRARY_SUFFIX}\)
include(BundleUtilities)
fixup_bundle(\${APPS}\ \\${QTPLUGINS}\ \${DIRS}\)
COMPONENT ${PROJECT_NAME})
The install command for the application is:
INSTALL(TARGETS ${PROJECT_NAME}
BUNDLE DESTINATION . COMPONENT ${PROJECT_NAME}
RUNTIME DESTINATION . COMPONENT ${PROJECT_NAME})
Thanks in advance
Best Regards
NoRulez
Von: David Cole [mailto:david.c...@kitware.com]
Gesendet: Mittwoch, 19. Jänner 2011 00:26
An: NoRulez
Cc: CMake MailingList
Betreff: Re: [CMake] Problems with MinGW + BundleUtilities
Providing code samples and/or copy/pasted output from doing your build would
be more effective.
I don't really know what you mean by give two destinations
On Tue, Jan 18, 2011 at 5:51 PM, NoRulez noru...@me.com wrote:
Thanks for the answer
I already added ${QT_LIBRARY_DIR} and ${QT_BINARY_DIR}, but if I give two
destinations, I get the error that it isn't a valid bundle.
Best Regards
NoRulez
Am 18.01.2011 um 23:43 schrieb David Cole david.c...@kitware.com:
On Windows, you have to tell fixup_bundle where to find the Qt dll's (and
the others) by passing in a list of directories as the last argument. Or,
alternatively, simply add those directories to the PATH as well.
HTH,
David
On Tue, Jan 18, 2011 at 4:34 PM, NoRulez noru...@me.com wrote:
Hello,
I build my Qt project successfully on linux/mac with the great
BundleUtilities.
On Windows the required Qt dlls and also libgcc_s_dw2-1.dll and
mingwm10.dll arent packaged.
The dumpbin.exe is in the path and the dumpbin.exe is under
C:\masm32\bin\dumpbin.exe
How can I solve this?
Thanks in advance
Best Regards
NoRulez
___
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
___
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] How to query compiler definitions?
For multi-config IDE's you *don't know* whether NDEBUG is defined or not at CMake-time. I imagine that the build system could keep control on all passed compilation parameters if calls for generation commands would be intercepted (by CMake). Does it get any feedback for changes of this preprocessor symbol? And AFAIK there's no way to specify that a source file is conditional on the build configuration. I can try an approximation. - Do I need to apply the variable CMAKE_BUILD_TYPE instead if I can not reuse the symbol's value? add_executable(super super.c) I would like to construct the source file list that is passed to this command dynamically. Can unneeded stuff be avoided? Regards, Markus ___ 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] Fixed ProjectGUID
Okay.
As it seems it's very simpel to change see GUID without any patch:
set_property(CACHE ${target_name}_GUID_CMAKE PROPERTY VALUE ${MY_GUID} )
Original-Nachricht
Datum: Fri, 7 Jan 2011 22:26:31 +0100
Von: Pau Garcia i Quiles pgqui...@elpauer.org
An: David Cole david.c...@kitware.com
CC: Sören Freudiger muffmo...@gmx.de, cmake@cmake.org
Betreff: Re: [CMake] Fixed ProjectGUID
Hello,
In Visual Studio 2010, ProjectGUID is a global. This bug provides a
patch to add global definitions to CMake, but only up to Visual Studio
2008. It shouldn't be difficult to update the patch to add support for
Visual C++ 2010. Setting the ProjectGUID would then be as easy as:
set_target_properties( thetarget PROPERTIES VS_GLOBAL_ProjectGUID
{384A545C-A6F2-4833-9260-F05C46557610} )
I opened the bug and provided the code almost two years ago, so it's
not like I expect CMake developers to suddenly implement it...
2011/1/7 David Cole david.c...@kitware.com:
The guids should remain constant in a given build tree for the life of
the
CMakeCache.txt file.
But after you delete that and start in a fresh build tree, you'll get
fresh
guids.
If you want constant guids in your vcproj files, they should be built by
hand, not with CMake.
HTH,
David
2011/1/7 Sören Freudiger muffmo...@gmx.de
Hello
Is it possible to set the ProjectGUID by CMake? Every time I generate a
vcproj file with CMake the ProjectGUID changes. But we need to have a
fixed
one (because other projects are including the vcproj).
Best regards
SirAnn
--
GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit
gratis Handy-Flat! http://portal.gmx.net/de/go/dsl
___
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
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
--
NEU: FreePhone - kostenlos mobil telefonieren und surfen!
Jetzt informieren: http://www.gmx.net/de/go/freephone
___
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] Weird behaviour of functions with list arguments
On 01/18/2011 at 20:51, Alexander Neundorf a.neundorf-w...@gmx.net wrote: On Saturday 11 December 2010, Johannes Zarl wrote: So ARGV0 is not the same as the first argument of ARGV. Why? Is it that the ARGV and ARGN lists get flattened, but the ARGVx are assigned before that? How can I safely access the values of ARGN, if they might contain lists? Do I understand correctly that you want to pass two lists of things to a macro/function ? To do this, you have to separate them with keywords. Since version 2.8.3 (or was it 2.8.2 ?) CMake comes with the module CMakeParseArguments.cmake which helps with evaluating such lists of arguments. There you can find also documentation. It turned out that the thing I wanted to do is not quite possible. AFAIK CMakeParseArguments can't handle keywords that appear more than once. My basic idea for a workaround was to use one keyword with several list-arguments and have CMakeParseArguments return a list of lists for that keyword. In the end, I did find another solution, though... Cheers, Johannes -- Johannes Zarl Virtual Reality Services Johannes Kepler University Informationsmanagement Altenbergerstrasze 69 4040 Linz, Austria Phone: +43 732 2468-8321 johannes.z...@jku.at http://vrc.zid.jku.at ___ 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] Component support in FindPackageHandleStandardArgs
On 01/18/2011 at 20:54, Alexander Neundorf a.neundorf-w...@gmx.net wrote: On Monday 13 December 2010, Johannes Zarl wrote: The three FPHSA calls from above could be written using this syntax as: FPHSA(XXX REQUIRED_VARS XXX_LIBRARY XXX_INCLUDE_DIR COMPONENTS COMPONENT YYY XXX_YYY_LIBRARY XXX_YYY_INCLUDE_DIR COMPONENT ZZZ XXX_ZZZ_LIBRARY XXX_ZZZ_INCLUDE_DIR ) The attached patch implements this syntax for FPHSA. Is this a desirable extension to FPHSA? Can you please add that to http://public.kitware.com/Bug/view.php?id=5920 Done. I'm not sure the current version of CMakeParseArguments.cmake supports listing the same keyword multiple times. That's true. In fact, the signature uses a single multiVAlueArg COMPONENTS and then evaluates the COMPONENT ... entries using a loop. Cheers, Johannes -- Johannes Zarl Virtual Reality Services Johannes Kepler University Informationsmanagement Altenbergerstrasze 69 4040 Linz, Austria Phone: +43 732 2468-8321 johannes.z...@jku.at http://vrc.zid.jku.at ___ 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] eclipse possible bug
suppose I have a project with:
add_subdirectory(path/lib1 ${CMAKE_CURRENT_BINARY_DIR}/ib1)
when I change a source of lib1 and click on build over the eclipse
project, eclipse doesn't build anything.
If I change a source of the main project it launches the build correctly.
I also tried to test the same thing with a simple MinGW Makefile
(instead of Eclipse CDT 4 - MinGW Makefile) and it works properly in
both two cases.
___
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] cpack bundle on osx
Dear fellow cmake users,
I am trying to create a bundle of my project that I build using CMake. I
have tried using the DragNDrop generator, which works to some extent. I
do manage to create a .app folder which contains the one binary that is
the outcome of the project in the Contents/MacOS folder. I do also
create a .dmg file. However:
- When clicking the .dmg I am first presented with the license (great!)
before the dmg is mounted and I see an empty folder (??)
- When clicking on the package.app nothing happens. However, clicking
on the binary in Contents/MacOS works as expected.
- I would also like to know how to include the shared libraries (dylib)
that I need. I currently depend on stuff that is installed with
MacPorts, and I don't want to require that the user have to install all
that stuff. Isn't the bundle supposed to be self-contained? Ideally I
would like the bundle to automatically include the libraries that are
listed with the otools -L binary command...
Question: Where do I find the DragNDrop documentation/examples? On the
wiki (
http://www.paraview.org/Wiki/CMake:CPackPackageGenerators#DragNDrop_.28OSX_only.29
) there are only two small lines, and my googling skills are apparently
not good enough..
Here is an extraction of the relevant part of my CMakeLists.txt:
...
if(APPLE)
add_executable(madx${BINARY_POSTFIX} MACOSX_BUNDLE ${srcfiles})
SET_TARGET_PROPERTIES(madx${BINARY_POSTFIX} PROPERTIES
CPACK_BUNDLE_STARTUP_COMMAND madx${BINARY_POSTFIX})
SET_TARGET_PROPERTIES(madx${BINARY_POSTFIX} PROPERTIES
CPACK_BUNDLE_ICON ${CMAKE_CURRENT_SOURCE_DIR}/cmakesrc/MadX.icns)
else(APPLE)
add_executable(madx${BINARY_POSTFIX} ${srcfiles})
endif(APPLE)
...
I also set some CPACK_BUNDLE properties because I earlier on tried to
use the BUNDLE generator, but from what I understand this should have
nothing to do with the DragNDrop generator?
Thank you all for reading and thanks in advance for all help you might
provide!
Cheers,
Yngve
___
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 query compiler definitions?
Just tried out my last approach, and found out that it doesn't work. The executable target always depends on the library target, irrespective of the build configuration. On 01/19/2011 11:50 AM, SF Markus Elfring wrote: For multi-config IDE's you *don't know* whether NDEBUG is defined or not at CMake-time. I imagine that the build system could keep control on all passed compilation parameters if calls for generation commands would be intercepted (by CMake). Does it get any feedback for changes of this preprocessor symbol? You don't seem to understand the difference between CMake-time and Make- (or build-) time. CMake-time is when you run CMake to generate the actual build system (Makefiles, Xcode project, VisualStudio project, etc.). This is when your CMake code runs, when you have to specify all the source files etc. Build-time is when the actual build system runs. Everything is static here (except for custom commands). In particular, you can't change the list of source files any more. And AFAIK there's no way to specify that a source file is conditional on the build configuration. I can try an approximation. - Do I need to apply the variable CMAKE_BUILD_TYPE instead if I can not reuse the symbol's value? Again, that variable is useless for multi-config generators as it is only meaningful for Makefile and other single-config generators. add_executable(super super.c) I would like to construct the source file list that is passed to this command dynamically. Can unneeded stuff be avoided? The problem is, you want to assemble that list at build-time, which is not possible, because then CMake wouldn't know about them. Regards, Markus I don't quite understand why it is so important to you that these files aren't passed to the compiler. If you exclude all of their contents with #ifndef NDEBUG, then each file should take less than a second to compile, so you'd need a lot of those debug-only files for it to matter. 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
Re: [CMake] How to query compiler definitions?
You don't seem to understand the difference between CMake-time and Make- (or build-) time. I understand that there can be differences between the time of configuration and the applied generation. I guess that we have got different expectations about the introspection capabilities of the CMake build system. Build-time is when the actual build system runs. Everything is static here (except for custom commands). I do not want it this way for my use case. In particular, you can't change the list of source files any more. I imagine that the build system can still accommodate to some changes from other sources like preprocessor symbols. The problem is, you want to assemble that list at build-time, which is not possible, because then CMake wouldn't know about them. Can instructions from CMake scripts also be executed at generation time? I don't quite understand why it is so important to you that these files aren't passed to the compiler. If you exclude all of their contents with #ifndef NDEBUG, then each file should take less than a second to compile, so you'd need a lot of those debug-only files for it to matter. I hope that a more detailed description will clarify my use case. Example: A source file toy.cxx contains already the preprocessor switch that you mentioned. The marked debug code works with objects from a C++ class library for XML processing which has got its bunch of source files bundled in this project. Now I would like to omit this dependency if the software will be built for release mode. I would also like to be sure and want to check before the call of a compiler if this special symbol is really set. Regards, Markus ___ 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 query compiler definitions?
On 01/19/2011 02:41 PM, SF Markus Elfring wrote:
You don't seem to understand the difference between CMake-time and Make-
(or build-) time.
I understand that there can be differences between the time of
configuration and the applied generation. I guess that we have got
different expectations about the introspection capabilities of the CMake
build system.
Build-time is when the actual build system runs.
Everything is static here (except for custom commands).
I do not want it this way for my use case.
Then CMake is not the right tool for you ;-) This would require the
configure+generation step to occur at the same time as the build step.
In particular, you can't change the list of source files any more.
I imagine that the build system can still accommodate to some changes
from other sources like preprocessor symbols.
You could ask for a source-file property to that effect. E.g.
set_source_files_properties(debug_funcs.c PROPERTIES
EXCLUDE_FROM_CONFIGURATIONS Release;MinSizeRel)
which would cause debug_funcs.c only to be compiled for the not-excluded
configurations. I don't think it would make to do this based on
preprocessor definitions.
The problem is, you want to assemble that list at build-time, which is
not possible, because then CMake wouldn't know about them.
Can instructions from CMake scripts also be executed at generation time?
Only scripts that are run through add_custom_command or
add_custom_target, but they are really isolated scripts (think bash or
python), they don't have any feedback on the build system.
I don't quite understand why it is so important to you that these files
aren't passed to the compiler. If you exclude all of their contents with
#ifndef NDEBUG, then each file should take less than a second to
compile, so you'd need a lot of those debug-only files for it to matter.
I hope that a more detailed description will clarify my use case.
Example:
A source file toy.cxx contains already the preprocessor switch that
you mentioned. The marked debug code works with objects from a C++ class
library for XML processing which has got its bunch of source files
bundled in this project. Now I would like to omit this dependency if the
software will be built for release mode. I would also like to be sure
and want to check before the call of a compiler if this special symbol
is really set.
Regards,
Markus
So, toy.cxx is not actually the problem, but you don't want to link
against the XML library. Do you need the library anyways (e.g. for other
targets) or does the whole project only require this library for this
debugging code? The question is, would something like this do for you
(here I assume the library you need is libxml)?
---8
find_package(FindLibXml2 REQUIRED)
include_directories(${LIBXML2_INCLUDE_DIR})
if(LIBXML2_DEFINITIONS)
add_definitions(${LIBXML2_DEFINITIONS})
endif()
add_executable(super a.cxx b.cxx c.cxx toy.cxx)
target_link_libraries(super foo bar debug ${LIBXML2_LIBRARIES})
add_executable(duper d.cxx e.cxx)
target_link_libraries(duper ${LIBXML2_LIBRARIES})
---8
Like this you only link the target super against the libxml libraries
for debug configurations. Since target duper always needs libxml, it's
ok to require it always.
However, if libxml is required for debugging only and you don't want to
require it unconditionally, you have a problem and I can't see an easy
way around it.
___
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] VS Preprocessor Definitions
ok I found it: set_property( TARGET my_target PROPERTY COMPILE_DEFINITIONS IL_STD ) Nehme On Tue, Jan 18, 2011 at 11:44 AM, Nehme Bilal nehmebi...@gmail.com wrote: Hello, I am trying to use CMake to build a project that uses CPLEX. The cplex compiling instructions says: o Add IL_STD to the Preprocessor Definitions field. This defines the macro IL_STD which is needed to use the STL. for linux, it says to add the following command to the Makefile: # - # Compiler options # - CCOPT = -m32 -O -fPIC -fexceptions -DNDEBUG -DIL_STD Is there a command in CMake that can achieve this and make it work for both windows and linux ? Thank you ! Nehme ___ 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 query compiler definitions?
set_source_files_properties(debug_funcs.c PROPERTIES EXCLUDE_FROM_CONFIGURATIONS Release;MinSizeRel) I do not want to exclude this file based on the value of the variable CMAKE_BUILD_TYPE. ;-) I don't think it would make to do this based on preprocessor definitions. It seems that our ideas converge. :-) So, toy.cxx is not actually the problem, Correct. but you don't want to link against the XML library. Partly. yes. I am affected by a general issue from C++ class libraries. The corresponding free source files were copied to a subdirectory of the project I am interested in because a public shared library (*.so/*.dll) seems to be missing for it. (The project has got its own bundle of external software.) Library features are used in a limited way so far. This has got the consequence that its compilation should be optional for specific application parts. Do you need the library anyways (e.g. for other targets) [...] ? The software test part depends on the C++ class library unconditionally. However, if libxml is required for debugging only and you don't want to require it unconditionally, you have a problem and I can't see an easy way around it. The utility http://grinninglizard.com/tinyxml/index.html; is needed in my case. Regards, Markus ___ 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 query compiler definitions?
On 01/19/2011 03:45 PM, SF Markus Elfring wrote: set_source_files_properties(debug_funcs.c PROPERTIES EXCLUDE_FROM_CONFIGURATIONS Release;MinSizeRel) I do not want to exclude this file based on the value of the variable CMAKE_BUILD_TYPE. ;-) Why not? That's mostly equivalent to doing it based on -DNDEBUG (which is automatically defined for Release and MinSizeRel). Or is it actually another criterion (such as whether testing is enabled)? I don't think it would make to do this based on preprocessor definitions. It seems that our ideas converge. :-) So, toy.cxx is not actually the problem, Correct. but you don't want to link against the XML library. Partly. yes. I am affected by a general issue from C++ class libraries. The corresponding free source files were copied to a subdirectory of the project I am interested in because a public shared library (*.so/*.dll) seems to be missing for it. (The project has got its own bundle of external software.) Library features are used in a limited way so far. This has got the consequence that its compilation should be optional for specific application parts. Do you need the library anyways (e.g. for other targets) [...] ? The software test part depends on the C++ class library unconditionally. So, you always build tinyxml? In that case, simply use this: 8 add_library(tinyxml STATIC tinyxml/tinystr.cpp tinyxml/tinyxml.cpp tinyxml/tinyxmlerror.cpp tinyxml/tinyxmlparser.cpp) 8 add_executable(super a.cpp b.cpp c.cpp toy.cpp) target_link_libraries(super debug tinyxml) In that case, super will be linked against the tinyxml target only for the debugging configurations. However, if libxml is required for debugging only and you don't want to require it unconditionally, you have a problem and I can't see an easy way around it. The utility http://grinninglizard.com/tinyxml/index.html; is needed in my case. Regards, Markus 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] cpack and install locations
Hi,
I have a strange and non consistent behavior using cmake and cpack. Here is my
'install' config:
install ( TARGETS ${target}
LIBRARY DESTINATION lib
ARCHIVE DESTINATION lib
PUBLIC_HEADER DESTINATION include/myFolder
)
the target is a shared library with associated public headers that I want to
put in a specific folder.
When I run 'sudo make install' on my Ubuntu 10.10 (Maverick 64 bits),
everything is ok and my stuff is installed in '/usr/local/lib' and
'/usr/local/include/myFolder'. Note that 'myFolder' is created by the 'install'
target.
Now I build a .deb package with 'sudo cpack -G DEB'. Again, everything is ok
and I get a .deb file that looks nice but with a change in the files
destinations that are now '/usr/lib' and '/usr/include/myFolder'.
That's my first question: why is there a difference in the install locations?
The next problem is that installation of the package fails when the specific
include folder ('myFolder') doesn't exists. That's also a difference with 'make
install'. How can I put my stuff in a folder that doesn't exists and that needs
to be created by the installer?
Sorry if the questions have been already answered: I've looked in the list
archives but without finding a solution.
--
Dom
ps: I'm using cmake and cpack version 2.8.2 on Ubuntu 10.10 (Maverick 64 bits)
If necessary, I can post my CPackConfig.cmake file.
___
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 query compiler definitions?
Why not? That's mostly equivalent to doing it based on -DNDEBUG (which is automatically defined for Release and MinSizeRel). I would like to be precise here. Do any configurations exist in the software development world where the build type Release does not include a definition for this preprocessor symbol? So, you always build tinyxml? Its compilation should depend on the application part that uses objects and corresponding member functions from this C++ class library. add_library(tinyxml STATIC By the way: How do you think about the attachment for the feature request Use CMake for build system? https://sourceforge.net/tracker/?func=detailaid=3151377group_id=13559atid=363559 I imagine that you might be affected with your project FreeFOAM in a similar way if I would dare to bundle its source files into an other project. I am curious if we will find more useful ideas for the involved issues. Regards, Markus ___ 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] Adding support for Absoft Fortran compilers in CMake
My apologies in advance if this is not the correct place to start my inquiry. I am looking for information on getting support for Absoft's Fortran compilers on Linux, Windows and OS X added to a future release of CMake. Ideally, the Absoft compilers would be supported in the same manner that other vendor's Fortran compilers. Can someone provide me with the appropriate channel to get this process started? Absoft is willing to a provide no cost copy of the compilers as well as making modifications to our compiler drivers if required. Tony Goelz Absoft Corporation ___ 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 bundle on osx
You will need to look into the BundleUtilities functionality, specifically
the fixup_bundle() function. This will copy and fixup dependent
dylibs/frameworks needed by your project. There is a short example that uses Qt
that you can download.
You will also probably need to properly configure a plist that resides in
your Application bundle. THere are CMake variables for this that you can set
then CMake will create a default plist for you.
There are a number of examples, CMake itself is one, that uses the
fixup_bundle() in its own code.
Separate from all of that is all the CPack variables that you probably need
to set.
Here is a macro that I wrote for one of my own projects:
#---
# This macro will set all the variables necessary to have a good OS X
Application
# bundle. The variables are as follows:
# PROJECT_NAME - which can be taken from the ${PROJECT_NAME} variable is needed
# DEBUG_EXTENSION - The extension used to denote a debug built Application.
Typically
# this is '_debug'
# ICON_FILE_PATH - The complete path to the bundle icon file
# VERSION_STRING - The version string that you wish to use for the bundle. For
OS X
# this string is usually .YY.ZZ in type. Look at the Apple docs for more
info
#---
macro(ConfigureMacOSXBundlePlist PROJECT_NAME DEBUG_EXTENSION ICON_FILE_PATH
VERSION_STRING)
# message(STATUS ConfigureMacOSXBundlePlist for ${PROJECT_NAME} )
IF(CMAKE_BUILD_TYPE MATCHES Release)
SET(DBG_EXTENSION )
else()
set(DBG_EXTENSION ${DEBUG_EXTENSION})
endif()
get_filename_component(ICON_FILE_NAME ${ICON_FILE_PATH} NAME)
#CFBundleGetInfoString
SET(MACOSX_BUNDLE_INFO_STRING ${PROJECT_NAME}${DBG_EXTENSION} Version
${VERSION_STRING}, Copyright 2009 BlueQuartz Software.)
SET(MACOSX_BUNDLE_ICON_FILE ${ICON_FILE_NAME})
SET(MACOSX_BUNDLE_GUI_IDENTIFIER ${PROJECT_NAME}${DBG_EXTENSION})
#CFBundleLongVersionString
SET(MACOSX_BUNDLE_LONG_VERSION_STRING ${PROJECT_NAME}${DBG_EXTENSION} Version
${VERSION_STRING})
SET(MACOSX_BUNDLE_BUNDLE_NAME ${PROJECT_NAME}${DBG_EXTENSION})
SET(MACOSX_BUNDLE_SHORT_VERSION_STRING ${VERSION_STRING})
SET(MACOSX_BUNDLE_BUNDLE_VERSION ${VERSION_STRING})
SET(MACOSX_BUNDLE_COPYRIGHT Copyright 2010, BlueQuartz Software. All Rights
Reserved.)
SET(${PROJECT_NAME}_PROJECT_SRCS ${${PROJECT_NAME}_PROJECT_SRCS}
${ICON_FILE_PATH})
SET_SOURCE_FILES_PROPERTIES(${ICON_FILE_PATH} PROPERTIES
MACOSX_PACKAGE_LOCATION Resources)
endmacro()
Hope that helps
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software Dayton, Ohio
On Jan 19, 2011, at 7:08 AM, Yngve Inntjore Levinsen wrote:
Dear fellow cmake users,
I am trying to create a bundle of my project that I build using CMake. I have
tried using the DragNDrop generator, which works to some extent. I do manage
to create a .app folder which contains the one binary that is the outcome of
the project in the Contents/MacOS folder. I do also create a .dmg file.
However:
- When clicking the .dmg I am first presented with the license (great!)
before the dmg is mounted and I see an empty folder (??)
- When clicking on the package.app nothing happens. However, clicking on
the binary in Contents/MacOS works as expected.
- I would also like to know how to include the shared libraries (dylib) that
I need. I currently depend on stuff that is installed with MacPorts, and I
don't want to require that the user have to install all that stuff. Isn't the
bundle supposed to be self-contained? Ideally I would like the bundle to
automatically include the libraries that are listed with the otools -L
binary command...
Question: Where do I find the DragNDrop documentation/examples? On the wiki (
http://www.paraview.org/Wiki/CMake:CPackPackageGenerators#DragNDrop_.28OSX_only.29
) there are only two small lines, and my googling skills are apparently not
good enough..
Here is an extraction of the relevant part of my CMakeLists.txt:
...
if(APPLE)
add_executable(madx${BINARY_POSTFIX} MACOSX_BUNDLE ${srcfiles})
SET_TARGET_PROPERTIES(madx${BINARY_POSTFIX} PROPERTIES
CPACK_BUNDLE_STARTUP_COMMAND madx${BINARY_POSTFIX})
SET_TARGET_PROPERTIES(madx${BINARY_POSTFIX} PROPERTIES CPACK_BUNDLE_ICON
${CMAKE_CURRENT_SOURCE_DIR}/cmakesrc/MadX.icns)
else(APPLE)
add_executable(madx${BINARY_POSTFIX} ${srcfiles})
endif(APPLE)
...
I also set some CPACK_BUNDLE properties because I earlier on tried to use the
BUNDLE generator, but from what I understand this should have nothing to do
with the DragNDrop generator?
Thank you all for reading and thanks in advance for all help you might
provide!
Re: [CMake] Adding support for Absoft Fortran compilers in CMake
That is awesome that you want to support CMake. I have some collaborators that use Absoft and want to switch to CMake but can not due to some issues. I think a great place to start would be this link: http://www.cmake.org/pipermail/cmake/2009-September/031730.html ___ Mike Jackson www.bluequartz.net Principal Software Engineer mike.jack...@bluequartz.net BlueQuartz Software Dayton, Ohio On Jan 19, 2011, at 10:32 AM, Tony Goelz wrote: My apologies in advance if this is not the correct place to start my inquiry. I am looking for information on getting support for Absoft's Fortran compilers on Linux, Windows and OS X added to a future release of CMake. Ideally, the Absoft compilers would be supported in the same manner that other vendor's Fortran compilers. Can someone provide me with the appropriate channel to get this process started? Absoft is willing to a provide no cost copy of the compilers as well as making modifications to our compiler drivers if required. Tony Goelz Absoft Corporation ___ 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] Adding support for Absoft Fortran compilers in CMake
On 01/19/2011 10:32 AM, Tony Goelz wrote: My apologies in advance if this is not the correct place to start my inquiry. This is a good place to start. This was discussed briefly: http://www.cmake.org/pipermail/cmake/2009-August/031688.html but left off here: http://www.cmake.org/pipermail/cmake/2009-September/031728.html Bill Hoffman and I are two of the core CMake developers at Kitware and are interested. I am looking for information on getting support for Absoft's Fortran compilers on Linux, Windows and OS X added to a future release of CMake. Ideally, the Absoft compilers would be supported in the same manner that other vendor's Fortran compilers. This is certainly possible, especially with your help. Can someone provide me with the appropriate channel to get this process started? Absoft is willing to a provide no cost copy of the compilers as well as making modifications to our compiler drivers if required. That will help tremendously. Bill and I will get in touch with you off-list. Thanks for your interest! -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] check_function_exists frailty
On Wed, Jan 19, 2011 at 3:27 AM, Eric Noulard eric.noul...@gmail.comwrote:
2011/1/19 Jack Poulson jack.poul...@gmail.com:
I have no idea why this would occur, but with CMake 2.8.2 on x86_64 I'm
getting strange behavior with check_function_exists. Namely, if I perform
the sequence
set(CMAKE_REQUIRED_LIBRARIES ${MATH_LIBS})
check_function_exists(daxpy HAVE_DAXPY)
whether or not /usr/lib/libpthread.a or /usr/lib/libpthread.so is in the
list changes the answer, even though daxpy is defined in a completely
different library!
Output with libpthread.so:
--
MATH_LIBS=/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_scalapack_lp64.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_blacs_lp64.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_intel_lp64.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_intel_thread.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_core.a;/opt/intel/Compiler/11.1/072/lib/intel64/libguide.a;/opt/intel/Compiler/11.1/072/lib/intel64/libiomp5.a;/usr/lib/libpthread.so
-- Looking for daxpy
-- Looking for daxpy - found
Output with libpthread.a:
--
MATH_LIBS=/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_scalapack_lp64.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_blacs_lp64.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_intel_lp64.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_intel_thread.a;/opt/intel/Compiler/11.1/072/mkl/lib/em64t/libmkl_core.a;/opt/intel/Compiler/11.1/072/lib/intel64/libguide.a;/opt/intel/Compiler/11.1/072/lib/intel64/libiomp5.a;/usr/lib/libpthread.a
-- Looking for daxpy
-- Looking for daxpy - not found
Any ideas what would be causing this strange behavior? And while I'm on
the
subject, should check_function_exist work with dynamic libraries? I had
to
give up some portability and force find_library to search for the static
MKL
libraries just to get the libpthread.so case to work.
I apologize in advance if I've missed something obvious...
May be you have an implicit dependency on dynamic pthread somewhere.
Are you using icc or gcc ?
I was using icc for C++ for the project, but it appears
check_function_exists was defaulting to gcc for the C compilation.
As far as I remember check_function_exists is using try_compile.
May be you can try to run CMake with
--debug-trycompile and look into files
I don't remember where they are... but I'm sure someone will tell you that.
I used your suggestion of --debug-trycompile and found that there was an
undefined reference for _dl_stack_flags in libpthread.a. The output of
check_function_exists was fairly misleading in this case...perhaps it should
output just 'found' or 'not found'.
Thank you for the help!
Jack
___
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 make a ProjectConfig.cmake
On Thursday 30 December 2010, Michael Wild wrote:
On 12/30/2010 11:33 AM, Ian Monroe wrote:
To create my QyotoConfig.cmake I need to know the full path of a
library so that I can set a variable like QYOTO_LIBRARY.
This is pretty standard requirement right? Its what we're supposed to
do in *Config.cmake's?
So anyways, how do I that? The only target property that hasn't
returned NOTFOUND is LOCATION, which unhelpfully returns the location
of the library in the build directory. I could parse this to get the
file name, and then append it to the library install location... but
that seems like such a hack. Feels like I'm doing something wrong if I
need to use a hack to do something standard.
I looked at install(EXPORT which could work, but it seems to include a
lot more information then is needed. I just want to set a variable
with the full path to a library.
Ian
That's not how *Config.cmake modules work. They're NOT Find*.cmake
modules. You should:
- add the targets to an export-set for usage from the build tree:
export(TARGETS ...
FILE ${CMAKE_BINARY_DIR}/${PROJECT_NAME}LibraryDepends.cmake)
- add the targets to an export-set for installation:
install(TARGETS ... EXPORT ${CMAKE_PROJECT_NAME}LibraryDepends ...)
- export the package for usage from the build tree (enter into some
global registry):
export(PACKAGE ${PROJECT_NAME})
- create a *Config.cmake file for the use from the build tree:
set(QYOTO_INCLUDE_DIR ${CMAKE_SOURCE_DIR})
set(QYOTO_LIB_DIR ${CMAKE_BINARY_DIR}/lib)
set(QYOTO_CMAKE_DIR ${CMAKE_BINARY_DIR})
configure_file(${CMAKE_PROJECT_NAME}Config.cmake.in
${CMAKE_BINARY_DIR}/${CMAKE_PROJECT_NAME}Config.cmake @ONLY)
- install the export set:
install(EXPORT ${CMAKE_PROJECT_NAME}LibraryDepends DESTINATION
share/${CMAKE_PROJECT_NAME}/CMake)
- create a *Config.cmake file for the use from the install tree and
install it:
set(QYOTO_INCLUDE_DIR ${CMAKE_INSTALL_PREFIX}/include)
set(QYOTO_LIB_DIR ${CMAKE_INSTALL_PREFIX}/lib)
set(QYOTO_CMAKE_DIR
${CMAKE_INSTALL_PREFIX}/share/${CMAKE_PROJECT_NAME}/CMake)
configure_file(${CMAKE_PROJECT_NAME}Config.cmake.in
${CMAKE_BINARY_DIR}/InstallFiles/${CMAKE_PROJECT_NAME}Config.cmake
@ONLY)
install(FILES
${CMAKE_BINARY_DIR}/InstallFiles/${CMAKE_PROJECT_NAME}Config.cmake
DESTINATION share/${CMAKE_PROJECT_NAME}/CMake)
- The *Config.cmake.in could look like this:
###
# Tell the user project where to find our headers and libraries
set(QYOTO_INCLUDE_DIR @QYOTO_INCLUDE_DIR@)
set(QYOTO_INCLUDE_DIRS ${QYOTO_INCLUDE_DIR})
set(QYOTO_LIBRARY_DIRS @QYOTO_LIB_DIR@)
# Our library dependencies (contains definitions for IMPORTED targets)
include(@QYOTO_CMAKE_DIR@/@PROJECT_NAME@LibraryDepends.cmake)
# Defines (if required)
set(QYOTO_DEFINITIONS @QYOTO_COMPILE_DEFINITIONS@)
# USE file (if you have one)
set(QYOTO_USE_FILE
@QYOTO_CMAKE_DIR@/@PROJECT_NAME@Use.cmake
)
###
As you can see, the QYOTO_INCLUDE_DIR, QYOTO_LIB_DIR and QYOTO_CMAKE_DIR
values will differ between build and install tree, which is why you
should configure it twice, once for installation and once for the use
from the build tree.
- If you want to get fancy, you can also provide a *ConfigVersion.cmake
file. This file should set the following variables, depending on the
variables PACKAGE_FIND_NAME, PACKAGE_FIND_VERSION,
PACKAGE_FIND_VERSION_{MAJOR,MINOR,PATCH,TWEAK,COUNT}:
- PACKAGE_VERSION (version string)
- PACKAGE_VERSION_EXACT (TRUE or FALSE)
- PACKAGE_VERSION_COMPATIBLE (TRUE or FALSE)
- PACKAGE_VERSION_UNSUITABLE (TRUE or FALSE)
Wow, good summary.
Can you please put that in a wiki page on http://www.cmake.org/Wiki/CMake ?
Thanks :-)
Alex
___
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 make a ProjectConfig.cmake
On Thursday 30 December 2010, Ian Monroe wrote: On Thu, Dec 30, 2010 at 08:08, Michael Hertling mhertl...@online.de wrote: On 12/30/2010 11:33 AM, Ian Monroe wrote: To create my QyotoConfig.cmake I need to know the full path of a library so that I can set a variable like QYOTO_LIBRARY. This is pretty standard requirement right? Its what we're supposed to do in *Config.cmake's? Yes. So anyways, how do I that? The only target property that hasn't returned NOTFOUND is LOCATION, which unhelpfully returns the location of the library in the build directory. I could parse this to get the file name, and then append it to the library install location... but that seems like such a hack. Feels like I'm doing something wrong if I need to use a hack to do something standard. Usually, I'd have a template QyotoConfig.cmake.in which contains FIND_LIBRARY(QYOTO_LIBRARY qyoto PATHS @CMAKE_INSTALL_PREFIX@/lib NO_DEFAULT_PATH ) and is processed by CONFIGURE_FILE(). If the library is installed with INSTALL(TARGETS qyoto RUNTIME DESTINATION bin LIBRARY DESTINATION lib ARCHIVE DESTINATION lib ) the FIND_LIBRARY() in the resulting QyotoConfig.cmake file will find the library right at the installation location but nowhere else, and the platform-dependent file names, e.g. libqyoto.so versus qyoto.dll, are also handled correctly. I looked at install(EXPORT which could work, but it seems to include a lot more information then is needed. I just want to set a variable with the full path to a library. Nevertheless, the imported-targets approach, i.e. the combination of INSTALL(TARGETS ... EXPORT ...) and INSTALL(EXPORT ...) along with an appropriately set up config file, is much more powerful and should be preferred, IMO; see [1] for more information. BTW, as the export file defines the imported targets, its inclusion in the config file should possibly be protected in a suitable way to avoid fatal redefinitions. The context I'm coming from is that I'm developing stuff that is distributed by Linux distributions. The export file has information about what the target is dependent on, including full paths. That feels like a bad thing to me. What was true about dependencies when a package was being built on a build server might not be true later. ...or maybe its fine? Can someone point me to an example of a package distributed by linux distros that uses this feature? Would make me feel better to know that I'm not the first person to use it. :) KDE since 4.2: http://techbase.kde.org/Development/CMake_KDE_4_2#New:_Exporting_and_importing_targets :-) It installs a FindKDE4Internal.cmake (which is basically what a KDELibs4Conf.cmake should be, if that feature would have existed already at KDE 4.0 time), which is searched by FindKDE4.cmake which comes with CMake. This file then includes KDELibsDependencies.cmake, KDEPlatformProfile.cmake, KDELibs4ToolsTargets.cmake and KDELibs4LibraryTargets.cmake. If you look at KDELibs4LibraryTargets.cmake, you'll see that it includes the configuration specific targets-file, KDELibs4LibraryTargets-relwithdebinfo.cmake in my case. This has stuff like the following: # Import target KDE4__kdeui for configuration RelWithDebInfo ... SET_TARGET_PROPERTIES(KDE4__kdeui PROPERTIES IMPORTED_LINK_INTERFACE_LIBRARIES_RELWITHDEBINFO KDE4__kdecore;Qt4::QtSvg;Qt4::QtGui IMPORTED_LOCATION_RELWITHDEBINFO /home/alex/Dashboards/installs/2.8.1/kdelibs/lib/libkdeui.so.5.5.0 IMPORTED_SONAME_RELWITHDEBINFO libkdeui.so.5 ) The line for IMPORTED_LINK_INTERFACE_LIBRARIES_RELWITHDEBINFO is interesting. You can see that it lists e.g. KDE4__kdecore and Qt4::QtGui. KDE4__kdecore is a library target which has been added just a few lines earlier, along with its own installed location. Qt4::QtGui is also a target name. Where does this target come from ? When FindKDE4.cmake is executed, Qt4 will be searched. Since some time FindQt4.cmake now also creates imported targets for its installed libraries, named as you can see above. So cmake will see that kdeui depends on Qt4::QtGui, look for the target Qt4::QtGui, and this will have the location set which has been found by FindQt4.cmake. FindQt4.cmake currently does a normal search for the Qt libraries, so this will be the current location. If Qt would install a Qt4Config.cmake, the targets imported there would also have the correct current locations. So, in the long run, imported targets should be created in the Find-modules, which will solve the fixed-path issue you see. Our (KDE's) Windows developers stumbled already over this issue, since in their installer you can choose where to install KDE and Qt, so the hardcoded paths broke for them. With the new way, where the Qt libs are referenced by their imported
Re: [CMake] Help building static libs w/cmake 2.8 and llvm/clang on Windows
On Tuesday 04 January 2011, Michael Maul wrote: Build is eclipse-cdt/nmake on windows 7 C:\Program Files (x86)\CMake 2.8\bin\cmake.exe -E cmake_link_script CMakeFiles\MathFunctions.dir\link.txt --verbose=yes CMAKE_AR-NOTFOUND cr MathFunctions.lib CMakeFiles/MathFunctions.dir/mysqrt.c.ob Error running link command: The system cannot find the file specified I specified CMAKE_AR as llvm-ar in the cache. I looked at some earlier posts related to similar problems w/cmake 2.6 and dashes link executables and tried renaming llvm-ar to llvm_ar but still am having the same issue. What is the exact cmake version ? I think I fixed something with regard to llvm not too long ago... Alex ___ 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] control order of custom target as a sub-part of a customized KDE build
On Tuesday 04 January 2011, Shawn Rutledge wrote:
I am building a KDE control panel plugin, and there is a requirement
to use a different translation mechanism rather than the default Qt
tr macros. So I want to post-process my ui_*.h files to replace
lines like this
ClearSiteDataDialog-setWindowTitle(tr2i18n(foo, 0));
with the replacement code like this
ClearSiteDataDialog-setWindowTitle(Translator::instance().lookupString(CSD
_DIALOG_TITLE));
I wrote a python script to do that, and I'm calling it like this from
cmakelists.txt:
cmake_minimum_required (VERSION 2.6.0)
set (CMAKE_VERBOSE_MAKEFILE true)
find_package(KDE4 REQUIRED)
file(GLOB SRC_FILES *.cpp)
set(kcm_my_plugin_PART_SRCS ${SRC_FILES})
message(STATUS build type ${CMAKE_BUILD_TYPE})
file(GLOB UI_FILES *.ui)
message(STATUS ui files ${UI_FILES})
kde4_add_ui_files(kcm_my_plugin_PART_SRCS ${UI_FILES})
kde4_add_plugin(kcm_my_plugin ${kcm_my_plugin_PART_SRCS}
${LINUX_COMMON_SOURCE} ${COMMON_SOURCE} ${COMMON_SOURCE_IMPL})
target_link_libraries(kcm_my_plugin ${KDE4_KDEUI_LIBS}
${KDE4_KCMUTILS_LIBS} ${X11_LIBRARIES} kutils)
# post-process the ui_*.h header files AFTER they have been generated
but BEFORE compiling anything
add_custom_target(ui_translate
COMMAND ${CMAKE_SOURCE_DIR}/tools/convert-tr2-all.py
WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR})
ADD_DEPENDENCIES(kcm_my_plugin ui_translate)
ADD_DEPENDENCIES(kcm_my_plugin_automoc ui_translate)
Have a look at the kde4_add_ui_files() macro.
It executes the kde4uic.cmake script. There some tools are called, the text of
a generated file is read into a cmake variable, and there using cmake regexp
some strings are replaced.
I think you can do it in a similar way for your problem.
Alex
___
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] control order of custom target as a sub-part of a customized KDE build
Thanks for the suggestions! I was in a hurry to get something
working, and the first working solution I found was to write a uic
wrapper script which calls uic and then modifies the output. This
line makes it substitute my wrapper for uic:
set(QT_UIC_EXECUTABLE ${CMAKE_SOURCE_DIR}/tools/uic-wrapper.py)
___
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] CMake, CUDA, VS build issues
On Fri, Jan 14, 2011 at 11:05 AM, Patrick Charrier patrick.charr...@igd.fraunhofer.de wrote: Hi all, I am experiencing some (random) reloading of VS-project files and rebuilding when using the combination of CMake, Visual Studio and CUDA. Particularly when performing the following steps. 1. Project has been built before. 2. Perform an SVN update. 3. Start CMake. Configure and Generate. 4. Open the generated VS Solution. 5. Build in Debug Mode. (Or Rebuild All.) 6. Build in Release Mode. (Or Rebuild All.) After Point 6 the fun part starts. 7. At this point VS runs CMake Configuration and Generation. Why this in the first place? 8. VS will then ask to reload the newly generated VS-project files for all the CUDA VS-projects (libraries) in the solution. 9. I hit yes and the project is being built. 10. When trying to start the application, VS will prompt me to reload the VS-project files again, as in step 8. 11. I hit yes again, but this time VS just says: 1-- Skipped Build: Project: PACKAGE, Configuration: Release Win32 -- 1Project not selected to build for this solution configuration 2-- Skipped Build: Project: INSTALL, Configuration: Release Win32 -- 2Project not selected to build for this solution configuration == Build: 0 succeeded, 0 failed, 7 up-to-date, 2 skipped == The problem only occurs with CUDA and VS from what I know. My main question is, why is there a Reconfiguration and Regeneration in step 7, and how can I avoid it? There should be no need for it, since step 3 should assure that the project files are fresh. Also why did it build smoothly in Debug (step 5), but not Release (step 6)? Also, what does the second Regenerate in step 11 mean? My guess is, that step 7 is somehow caused by Debug and Release sharing the same CUDA .depend and .cmake files in the CMakeFiles subdirectory of each CUDA VS-project. But how exactly, and how could I fix that? Thank you and Best Regards, Patrick This is the expected behavior and is a product of the FindCUDA script's ability to generate the file level dependencies. Here's what happens. 1. Start with fresh build directory. Configure with CMake. At this point we don't know that file.cu depends on header.h. We generate the VS project file anyway with not dependencies for file.cu. 2. Build your project. At this point when file.cu is compiled it generates file.cu.obj.depend which is created with nvcc -M similarly to how gcc -M is run. At this point, your configuration is stale, because file.cu.obj.depend has changed. 3. If you click build or run CMake will want to reconfigure, because file.cu.obj.depend has changed. 4. When CMake configures again it will generate a new vcproj file listing header.h as a dependency for file.cu. If you change header.h, then file.cuwill automatically be recompiled just as if file.cu were a C file. 5. Whenever the dependencies of file.cu change, file.cu.obj.depend will change signaling CMake that it needs to reconfigure the VS project. 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
[CMake] Should CMake use /etc/ld.so.conf.d for find_library's CMAKE_SYSTEM_LIBRARY_PATH?
I'm noticing that on some systems they package the NVIDIA driver into different directories than the driver is typically installed. In order to make stuff link properly at run time these non-standard locations are added to /etc/ld.so.conf.d. I'm wondering if there is a reason not to use this information to add paths to CMAKE_SYSTEM_LIBRARY_PATH? It would certainly help in finding libraries that are installed in diverse places. 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
[CMake] add_custom_target and Code Blocks generator
Greetings, the Code Blocks generator is not adding to the project the sources, specified in the command. In order to add a group of header files to my project tree, I'm trying to implement the solution posted here: http://www.cmake.org/pipermail/cmake/2010-November/040537.html The target itself is added to the Code Blocks project, however the source files are not. Should I file a bug report? Are there any other workarounds for that use case, besides adding the headers to some other existing executable or library target? This is under linux, with CMake release 2.8.3. Regards, Dimitri ___ 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-500-g1a0ff79
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 1a0ff79898d6ccd7e1dafad384a8b1a7461d3424 (commit) via 3cba29d2203760b2b8e64c34309e764dd2e2c4f2 (commit) from cbd40b3b7cd569c87ebcdac03ec0931a6f47771d (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=1a0ff79898d6ccd7e1dafad384a8b1a7461d3424 commit 1a0ff79898d6ccd7e1dafad384a8b1a7461d3424 Merge: cbd40b3 3cba29d Author: Brad King brad.k...@kitware.com AuthorDate: Wed Jan 19 14:01:57 2011 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Wed Jan 19 14:01:57 2011 -0500 Merge topic 'bootstrap-enable-ccache-issue-11707' 3cba29d bootstrap: Add --enable-ccache option (#11707) --- Summary of changes: bootstrap |9 + 1 files changed, 9 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-503-g9ae65b8
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 9ae65b866e4de737be00d3518da36aedca322278 (commit) via c64d1385b763b7529a19a6f11c816339479dc3dc (commit) via 668ce6b1e88c1732bc677413033552994c951709 (commit) from 1a0ff79898d6ccd7e1dafad384a8b1a7461d3424 (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=9ae65b866e4de737be00d3518da36aedca322278 commit 9ae65b866e4de737be00d3518da36aedca322278 Merge: 1a0ff79 c64d138 Author: Brad King brad.k...@kitware.com AuthorDate: Wed Jan 19 14:02:04 2011 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Wed Jan 19 14:02:04 2011 -0500 Merge topic 'doc-hard-preprocessor-characters' c64d138 Document COMPILE_DEFINITIONS known limitations (#11660, #11712) 668ce6b Combine duplicate COMPILE_DEFINITIONS disclaimer --- Summary of changes: Source/CMakeLists.txt |1 + Source/cmDocumentCompileDefinitions.h | 34 + Source/cmMakefile.cxx | 10 +--- Source/cmSourceFile.cxx | 11 + Source/cmTarget.cxx | 10 +--- 5 files changed, 41 insertions(+), 25 deletions(-) create mode 100644 Source/cmDocumentCompileDefinitions.h 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-506-g27039e6
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 27039e62f9b01578e0cb23029bc7ffc3963f5634 (commit) via cabb6cd00e2c7424d2be2b8c4103ab2bb2940832 (commit) via 4da2a5687be6ec91f8001ba0366776f775531431 (commit) from 9ae65b866e4de737be00d3518da36aedca322278 (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=27039e62f9b01578e0cb23029bc7ffc3963f5634 commit 27039e62f9b01578e0cb23029bc7ffc3963f5634 Merge: 9ae65b8 cabb6cd Author: Brad King brad.k...@kitware.com AuthorDate: Wed Jan 19 14:02:11 2011 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Wed Jan 19 14:02:11 2011 -0500 Merge topic 'doc-try_compile-clarification' cabb6cd Document Check(C|CXX)SourceCompiles behavior more clearly (#11688) 4da2a56 Document try_compile behavior more clearly (#11688) --- Summary of changes: Modules/CheckCSourceCompiles.cmake |4 +- Modules/CheckCXXSourceCompiles.cmake |4 +- Source/cmTryCompileCommand.h | 41 +++--- 3 files changed, 27 insertions(+), 22 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-509-gc6cb693
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 c6cb693147b9e97b4d5529e38a3f81bcaa4bef37 (commit) via 4c980e36bb065e2b877fe8c50067a50346ef0f7c (commit) via 0d7cf4951a5f3e375096ba4426a6cb503266f9df (commit) from 27039e62f9b01578e0cb23029bc7ffc3963f5634 (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=c6cb693147b9e97b4d5529e38a3f81bcaa4bef37 commit c6cb693147b9e97b4d5529e38a3f81bcaa4bef37 Merge: 27039e6 4c980e3 Author: Brad King brad.k...@kitware.com AuthorDate: Wed Jan 19 14:02:20 2011 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Wed Jan 19 14:02:20 2011 -0500 Merge topic 'doc-old-get_X_property-commands' 4c980e3 Reference get_property() from old get_*_property() commands 0d7cf49 Fix get_(cmake|test)_property documentation (#11703) --- Summary of changes: Source/cmGetCMakePropertyCommand.h | 11 +++ Source/cmGetDirectoryPropertyCommand.h |3 ++- Source/cmGetSourceFilePropertyCommand.h |4 +++- Source/cmGetTargetPropertyCommand.h |4 +++- Source/cmGetTestPropertyCommand.h | 12 +++- 5 files changed, 22 insertions(+), 12 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-512-gdb276e4
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 db276e48c41abb0c8dcbf9c2d0726d16fc3e4871 (commit) via 7d9b903756bcb5a7e210b78c5ab9551dab6ab538 (commit) via e4e14e856800020febf770221cb0593fa72e5c1b (commit) from c6cb693147b9e97b4d5529e38a3f81bcaa4bef37 (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=db276e48c41abb0c8dcbf9c2d0726d16fc3e4871 commit db276e48c41abb0c8dcbf9c2d0726d16fc3e4871 Merge: c6cb693 7d9b903 Author: Brad King brad.k...@kitware.com AuthorDate: Wed Jan 19 14:02:26 2011 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Wed Jan 19 14:02:26 2011 -0500 Merge topic 'doc-if-dereferencing-issue-10773' 7d9b903 Clarify auto-dereference cases in if() command (#11701) e4e14e8 Replace misleading example in the if() documentation (#10773) --- Summary of changes: Source/cmIfCommand.h | 89 +- 1 files changed, 37 insertions(+), 52 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-514-g3b900db
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 3b900dbd093e804c17ecee34c64b1380275f1138 (commit) via 114c3224a4934c8f5bbfa0330451583a05383062 (commit) from db276e48c41abb0c8dcbf9c2d0726d16fc3e4871 (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=3b900dbd093e804c17ecee34c64b1380275f1138 commit 3b900dbd093e804c17ecee34c64b1380275f1138 Merge: db276e4 114c322 Author: Brad King brad.k...@kitware.com AuthorDate: Wed Jan 19 14:02:33 2011 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Wed Jan 19 14:02:33 2011 -0500 Merge topic 'doc-CheckFunctionExists-clarify-issue-10044' 114c322 Document CheckFunctionExists more clearly (#10044) --- Summary of changes: Modules/CheckFunctionExists.cmake | 14 -- 1 files changed, 8 insertions(+), 6 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-526-gd0b4f13
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 d0b4f13521367748488a7b70211a4d2fe7da1d9c (commit) via 96cd16380af5f2633cf6283481eb414c626436d3 (commit) via fa4a3b04d0904a2e93242c0c3dd02a357d337f77 (commit) via fc144924a0782b37c320378ac76482f0534c7530 (commit) from a104712d41a997557a00a6e8950aeb761c84bf5b (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=d0b4f13521367748488a7b70211a4d2fe7da1d9c commit d0b4f13521367748488a7b70211a4d2fe7da1d9c Merge: a104712 96cd163 Author: Brad King brad.k...@kitware.com AuthorDate: Wed Jan 19 14:03:15 2011 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Wed Jan 19 14:03:15 2011 -0500 Merge topic 'fix-install-req-sys-libs' 96cd163 Add CPACK_NSIS_INSTALL_ROOT for CMake's own installer (#9148) fa4a3b0 Add CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_NO_WARNINGS variable fc14492 VS10: Fix problems with InstallRequiredSystemLibraries. --- Summary of changes: CMakeCPack.cmake | 51 ++ CMakeCPackOptions.cmake.in | 10 +++-- Modules/InstallRequiredSystemLibraries.cmake | 58 +++-- 3 files changed, 82 insertions(+), 37 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-529-gab8ea7c
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 ab8ea7c413e77fbd7fc0c5a00edddfad4928c8e3 (commit) via aeb6cd8a8920c398b923d3ce383c06ed4643727f (commit) via 20d87c8026d3e23d8f9f18b735bc0304ec80d046 (commit) from d0b4f13521367748488a7b70211a4d2fe7da1d9c (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=ab8ea7c413e77fbd7fc0c5a00edddfad4928c8e3 commit ab8ea7c413e77fbd7fc0c5a00edddfad4928c8e3 Merge: d0b4f13 aeb6cd8 Author: Brad King brad.k...@kitware.com AuthorDate: Wed Jan 19 14:03:41 2011 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Wed Jan 19 14:03:41 2011 -0500 Merge topic 'resolve/mingw-cross-compile-resources/honor-explicit-zero-timeout' aeb6cd8 Merge branch 'honor-explicit-zero-timeout' into resolve/mingw-cross-compile-resources/honor-explicit-zero-timeout 20d87c8 Teach Simple_Mingw_Linux2Win test to use windres --- Summary of changes: Tests/CMakeLists.txt | 15 --- 1 files changed, 8 insertions(+), 7 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-540-gef1f945
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 ef1f9456aafb7c037601c5d6efb124f3f4152d46 (commit)
via e60c8ec6c7dc2b9c963684ef37bc38c3db367ae2 (commit)
via db05da35d26b7b10a65b5330e1506582c29268ad (commit)
from 20d11b9a33e1d1c9d472b04d1b4f18cabdaecb2d (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=ef1f9456aafb7c037601c5d6efb124f3f4152d46
commit ef1f9456aafb7c037601c5d6efb124f3f4152d46
Merge: 20d11b9 e60c8ec
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Jan 19 14:28:19 2011 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Jan 19 14:28:19 2011 -0500
Merge topic 'sco-compiler'
e60c8ec Factor SCO compiler info out of platform file (#11700)
db05da3 Recognize SCO UnixWare C/C++ compilers (#11700)
---
Summary of changes:
Modules/CMakeCCompilerId.c.in |3 +++
Modules/CMakeCXXCompilerId.cpp.in |3 +++
Modules/Compiler/SCO-C.cmake |2 ++
Modules/Compiler/SCO-CXX.cmake |2 ++
.../{Platform/AIX-GNU.cmake = Compiler/SCO.cmake} | 12 +++-
Modules/Platform/SCO_SV.cmake |3 ---
6 files changed, 17 insertions(+), 8 deletions(-)
create mode 100644 Modules/Compiler/SCO-C.cmake
create mode 100644 Modules/Compiler/SCO-CXX.cmake
copy Modules/{Platform/AIX-GNU.cmake = Compiler/SCO.cmake} (72%)
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-551-g3e3af1f
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 3e3af1f507bcb43b7de35177cd694fe8124cae83 (commit) via 9859c64ffcc1450ce5dd23eb5c78fad58b030696 (commit) from 3a1975c529ee254277b86cc3f16920ac61c5f54e (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=3e3af1f507bcb43b7de35177cd694fe8124cae83 commit 3e3af1f507bcb43b7de35177cd694fe8124cae83 Merge: 3a1975c 9859c64 Author: Brad King brad.k...@kitware.com AuthorDate: Wed Jan 19 14:28:36 2011 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Wed Jan 19 14:28:36 2011 -0500 Merge topic 'vs-Fortran-SCC-issue-10237' 9859c64 Honor VS_SCC_* properties in Fortran targets (#10237) --- Summary of changes: Source/cmLocalVisualStudio7Generator.cxx | 29 ++--- Source/cmLocalVisualStudio7Generator.h |1 + 2 files changed, 19 insertions(+), 11 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-553-gaa2b3db
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 aa2b3db3221c1d01b4bf4541d90aa8a768937903 (commit) via 8dc7501d509738606e1d00d23e00a4d28a17e832 (commit) from 3e3af1f507bcb43b7de35177cd694fe8124cae83 (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=aa2b3db3221c1d01b4bf4541d90aa8a768937903 commit aa2b3db3221c1d01b4bf4541d90aa8a768937903 Merge: 3e3af1f 8dc7501 Author: Brad King brad.k...@kitware.com AuthorDate: Wed Jan 19 14:28:41 2011 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Wed Jan 19 14:28:41 2011 -0500 Merge topic 'depend-scan-backslash-issue-10281' 8dc7501 Normalize slashes in scanned #include lines (#10281) --- Summary of changes: Source/cmDependsC.cxx |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, next, updated. v2.8.3-1435-g18e0784
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, next has been updated via 18e07843c8416590c0cb444e8936a709d4a93862 (commit) via aa2b3db3221c1d01b4bf4541d90aa8a768937903 (commit) via 3e3af1f507bcb43b7de35177cd694fe8124cae83 (commit) via 3a1975c529ee254277b86cc3f16920ac61c5f54e (commit) via 863c7dfd881148da8a8ef6b24a5fee23ae8b3b8b (commit) via d9fb64088b8bbf2ab0ac8f6e50cd6188affeef8a (commit) via b9f9c90eaf16ecaa555f2012c2b4d7a27daf2937 (commit) via ef1f9456aafb7c037601c5d6efb124f3f4152d46 (commit) via 20d11b9a33e1d1c9d472b04d1b4f18cabdaecb2d (commit) via e4f2a9317a8cf9a2f7eb03c7f17a1f78f35a16bb (commit) via 9ea63c581b466e0bb31db1b5750e3b588e5a6497 (commit) via 6c075284f61b4abce8feb79779b6222987f26697 (commit) from fa86a35619423133b34da30788f06fa9b80f7f94 (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=18e07843c8416590c0cb444e8936a709d4a93862 commit 18e07843c8416590c0cb444e8936a709d4a93862 Merge: fa86a35 aa2b3db Author: Brad King brad.k...@kitware.com AuthorDate: Wed Jan 19 14:28:51 2011 -0500 Commit: Brad King brad.k...@kitware.com CommitDate: Wed Jan 19 14:28:51 2011 -0500 Merge branch 'master' into next --- Summary of changes: 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-554-g1c8787f
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 1c8787f387e9958e5ca4a9e5d268bb942966305f (commit) from aa2b3db3221c1d01b4bf4541d90aa8a768937903 (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=1c8787f387e9958e5ca4a9e5d268bb942966305f commit 1c8787f387e9958e5ca4a9e5d268bb942966305f Author: KWSys Robot kwro...@kitware.com AuthorDate: Thu Jan 20 00:01:03 2011 -0500 Commit: KWSys Robot kwro...@kitware.com CommitDate: Thu Jan 20 00:10:06 2011 -0500 KWSys Nightly Date Stamp diff --git a/Source/kwsys/kwsysDateStamp.cmake b/Source/kwsys/kwsysDateStamp.cmake index 64abcb3..bbc5938 100644 --- a/Source/kwsys/kwsysDateStamp.cmake +++ b/Source/kwsys/kwsysDateStamp.cmake @@ -18,4 +18,4 @@ SET(KWSYS_DATE_STAMP_YEAR 2011) SET(KWSYS_DATE_STAMP_MONTH 01) # KWSys version date day component. Format is DD. -SET(KWSYS_DATE_STAMP_DAY 19) +SET(KWSYS_DATE_STAMP_DAY 20) --- 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
