[cmake-developers] [CMake 0013623]: MSBuild.exe doesn't see a project in solution (MSVC 2012 express)
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=13623 == Reported By:Michael Broutin Assigned To: == Project:CMake Issue ID: 13623 Category: CMake Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2012-10-31 04:31 EDT Last Modified: 2012-10-31 04:31 EDT == Summary:MSBuild.exe doesn't see a project in solution (MSVC 2012 express) Description: Hi, I'm no sure whether it's a CMake or MSVC issue, but here is the case : I use a nightly build of CMake which has MSVC 2012 express support (2.8.9 doesn't support it, AFAIK) In the generated solution, I have a custom target to build doxygen doc (Cmake script is here : http://code.google.com/p/ogre-procedural/source/browse/docs/CMakeLists.txt) I can build successfully this target from within the IDE. But, when I try to run it from a batch, either using CMake --build or MSBuild.exe things get a bit messy : when I specify the target doc, MSBuild or CMake just say that this target doesn't exist in the solution. Other targets with code in it, or building with no target specified seem to work properly, it's just this target which fails... Steps to Reproduce: Build the Ogre SDK from source for MSVC11 express Get this project : http://code.google.com/p/ogre-procedural/source/checkout Generate it with CMake, then call CMake --build with target doc. Additional Information: In the past, I used MSVC 2010 and it properly built the doc target. But I used devenv.exe (or VCExpress.exe for the express version), didn't try with MSBuild. == Issue History Date ModifiedUsername FieldChange == 2012-10-31 04:31 Michael BroutinNew Issue == -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] Fwd: Bug#691948: cmake: Insists on using non-existent (when cross-compiling) -rdynamic flag
FYI
Original Message
Subject: Bug#691948: cmake: Insists on using non-existent (when
cross-compiling) -rdynamic flag
Resent-Date: Wed, 31 Oct 2012 16:09:02 +
Resent-From: Sam Morris s...@robots.org.uk
Resent-To: debian-bugs-d...@lists.debian.org
Resent-CC: Modestas Vainius mo...@debian.org
Date: Wed, 31 Oct 2012 16:04:04 +
From: Sam Morris s...@robots.org.uk
Reply-To: Sam Morris s...@robots.org.uk, 691...@bugs.debian.org
To: Debian Bug Tracking System sub...@bugs.debian.org
Package: cmake
Version: 2.8.9-1
Severity: important
The -rdynamic flag is being picked up from Platform/Linux-GNU.cmake,
even though CMAKE_SYSTEM_NAME is set to Windows.
Test case:
#!/bin/bash
set -ex
cat CMakeLists.txt EOF
cmake_minimum_required (VERSION 2.8)
project (test)
add_executable (test test.c)
EOF
cat main.c EOF
int main (void) {}
EOF
mkdir build
cd build
cmake -G 'Unix Makefiles' -DCMAKE_SYSTEM_NAME=Windows
-DCMAKE_C_COMPILER=i686-w64-mingw32-gcc
-DCMAKE_RC_COMPILER=i686-w64-mingw32-windres ..
Output:
-- The C compiler identification is GNU 4.6.3
-- The CXX compiler identification is GNU 4.6.3
-- Check for working C compiler: /usr/bin/i686-w64-mingw32-gcc
-- Check for working C compiler: /usr/bin/i686-w64-mingw32-gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/i686-w64-mingw32-c++
-- Check for working CXX compiler: /usr/bin/i686-w64-mingw32-c++ --
works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Configuring done
You have changed variables that require your cache to be deleted.
Configure will be re-run and you may have to reset some variables.
The following variables have changed:
CMAKE_RC_COMPILER= i686-w64-mingw32-windres
-- The C compiler identification is GNU 4.6.3
-- The CXX compiler identification is GNU 4.6.3
-- Check for working C compiler: /usr/bin/i686-w64-mingw32-gcc
-- Check for working C compiler: /usr/bin/i686-w64-mingw32-gcc -- broken
CMake Error at /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:52
(MESSAGE):
The C compiler /usr/bin/i686-w64-mingw32-gcc is not able to compile
a
simple test program.
It fails with the following output:
Change Dir: /tmp/x/build/CMakeFiles/CMakeTmp
Run Build Command:/usr/bin/make cmTryCompileExec793991569/fast
/usr/bin/make -f CMakeFiles/cmTryCompileExec793991569.dir/build.make
CMakeFiles/cmTryCompileExec793991569.dir/build
make[1]: Entering directory `/tmp/x/build/CMakeFiles/CMakeTmp'
/usr/bin/cmake -E cmake_progress_report
/tmp/x/build/CMakeFiles/CMakeTmp/CMakeFiles 1
Building C object
CMakeFiles/cmTryCompileExec793991569.dir/testCCompiler.c.obj
/usr/bin/i686-w64-mingw32-gcc -o
CMakeFiles/cmTryCompileExec793991569.dir/testCCompiler.c.obj -c
/tmp/x/build/CMakeFiles/CMakeTmp/testCCompiler.c
Linking C executable cmTryCompileExec793991569
/usr/bin/cmake -E cmake_link_script
CMakeFiles/cmTryCompileExec793991569.dir/link.txt --verbose=1
/usr/bin/i686-w64-mingw32-gcc
CMakeFiles/cmTryCompileExec793991569.dir/testCCompiler.c.obj -o
cmTryCompileExec793991569 -rdynamic
i686-w64-mingw32-gcc: error: unrecognized option ‘-rdynamic’
make[1]: Leaving directory `/tmp/x/build/CMakeFiles/CMakeTmp'
make[1]: *** [cmTryCompileExec793991569] Error 1
make: *** [cmTryCompileExec793991569/fast] Error 2
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:2 (project)
-- Configuring incomplete, errors occurred!
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages cmake depends on:
ii cmake-data 2.8.9-1
ii libarchive12 3.0.4-2
ii libc6 2.13-35
ii libcurl3-gnutls7.26.0-1
ii libexpat1 2.1.0-1
ii libgcc11:4.7.1-7
ii libstdc++6 4.7.1-7
ii libxmlrpc-core-c3 1.16.33-3.2
ii procps 1:3.3.3-2
ii zlib1g 1:1.2.7.dfsg-13
cmake recommends no packages.
Versions of packages cmake suggests:
ii gcc 4:4.7.1-1
ii make 3.81-8.2
-- no debconf information
--
Powered by www.kitware.com
Visit other Kitware
[cmake-developers] FOSDEM CrossDesktop DevRoom 2013 - Call for Talks
Hello, The Call for Talks for the CrossDesktop DevRoom at FOSDEM 2013 is now officially open. Please do not wait till the last minute! --8--- * FOSDEM is one of the largest gatherings of Free Software contributors in the world and happens each February in Brussels (Belgium). One of the tracks will be the CrossDesktop DevRoom, which will host Desktop-related talks. We are now inviting proposals for talks about Free/Libre/Open-source Software on the topics of Desktop development, Desktop applications and interoperativity amongst Desktop Environments. This is a unique opportunity to show novel ideas and developments to a wide technical audience. Topics accepted include, but are not limited to: Enlightenment, Gnome, KDE, Unity, XFCE, Windows, Mac OS X, general desktop matters, applications that enhance desktops and web (when related to desktop). Talks can be very specific, such as developing mobile applications with Qt Quick; or as general as predictions for the fusion of Desktop and web in 5 years time. Topics that are of interest to the users and developers of all desktop environments are especially welcome. The FOSDEM 2012 schedule might give you some inspiration: https://archive.fosdem.org/2012/schedule/track/crossdesktop_devroom.html https://archive.fosdem.org/2012/schedule/track/crossdesktop_devroom.html Please include the following information when submitting a proposal: - Your name - The title of your talk (please be descriptive, as titles will be listed with around 250 from other projects) - Short abstract of one or two paragraphs - Short bio - Requested time: from 15 to 45 minutes. Normal duration is 30 minutes. Longer duration requests must be properly justified. The deadline for submissions is December 14th 2012. FOSDEM will be held on the weekend of 2-3 February 2013. Please submit your proposals to crossdesktop-devr...@lists.fosdem.org (subscribtion page for the mailing list: https://lists.fosdem.org/listinfo/crossdesktop-devroom ) -- The CrossDesktop DevRoom 2013 Organization Team* --8--- -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] patch for cmake that adds a new timestamp command
Has anybody tried this anywhere else? I'm going to merge it to 'next' tomorrow, so that it will get tested on the dashboards after that. Just curious if there are any other known problems with it that I should squash in before doing that... Thanks, David On Tue, Oct 16, 2012 at 1:57 PM, David Cole david.c...@kitware.com wrote: I have amended the commit and pushed this branch to the stage. If anybody else would like to try it out they can grab the add-timestamp-subcommands branch from the CMake stage repo. I did not merge it to 'next' yet, but I will do that when we're ready to get it tested on the dashboards. Thanks for your work on this Nils. David On Tue, Oct 16, 2012 at 11:48 AM, Nils Gladitz glad...@sci-vis.de wrote: Ah that might explain it ... I may have been using nmake on Windows and ninja on linux. Thanks! Nils On 10/16/2012 05:27 PM, David Cole wrote: On Tue, Oct 16, 2012 at 10:12 AM, Nils Gladitz glad...@sci-vis.de wrote: I certainly wouldn't mind though I'm not sure what that means. Do the changes in next still potentially make it into 2.8.10? Going into 'next' is how stuff gets tested on the dashboards, and then later Brad and I merge things to 'master' when they're ready. After something is merged to 'master' it will be in the CMake release that follows that. Brad mentioned this would be on the TODO list for after 2.8.10. We can put it in 'next' to vet it and correct any dashboard issues that show up (errors/warnings on other platforms, other platform test failures) at any time. But it will probably not go into 'master' until after 2.8.10. We don't typically add significant features or take risky changes after we start doing release candidates. I've tried to run all tests successfully before submitting but I can't tell if any of those were called BootstrapTest. Is there anything special required to run it? The BootstrapTest test only runs on Unix Makefiles based builds, so if you're using a different generator, it does not get added as a test. Nils On 10/16/2012 02:49 PM, David Cole wrote: I had to do this to get the bootstrap version of CMake to work (and the BootstrapTest to pass): $ git diff diff --git a/Source/CMakeLists.txt b/Source/CMakeLists.txt index 9d46355..8bf6c40 100644 --- a/Source/CMakeLists.txt +++ b/Source/CMakeLists.txt @@ -264,8 +264,6 @@ set(SRCS cmTarget.cxx cmTarget.h cmTargetExport.h - cmTimestamp.h - cmTimestamp.cxx cmTest.cxx cmTest.h cmTestGenerator.cxx diff --git a/Source/cmBootstrapCommands.cxx b/Source/cmBootstrapCommands.cxx index 9097a74..e3a2ad4 100644 --- a/Source/cmBootstrapCommands.cxx +++ b/Source/cmBootstrapCommands.cxx @@ -89,6 +89,7 @@ #include cmStringCommand.cxx #include cmSubdirCommand.cxx #include cmTargetLinkLibrariesCommand.cxx +#include cmTimestamp.cxx #include cmTryCompileCommand.cxx #include cmTryRunCommand.cxx #include cmUnsetCommand.cxx After amending this, I'll push to next later today unless somebody objects to this?? Thanks, David On Fri, Oct 5, 2012 at 4:16 PM, Nils Gladitz glad...@sci-vis.de wrote: I've updated the patch (attached) to return empty string on failure. I also tried to use the time definitions from global namespace rather than std::. Nils On 10/05/2012 09:17 PM, Brad King wrote: On 10/05/2012 02:53 PM, Nils Gladitz wrote: My initial thought was that NOTFOUND would be a good idea since it evaluates to false and the get_*_property commands also seem to use it. I wrote the more general get_property command to replace those and the newer command uses empty string rather than NOTFOUND. It is more useful when computing pieces of a string to put together, perhaps when appending to a property value. Looking at the documentation for if() again only -NOTFOUND as a suffix should evaluate to false though (I assume the documentation is incomplete here?). Yes, thanks for pointing it out. Fixed: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f63304d9 On second though relying on timestamps to evaluate to false on failure is probably a bad idea since I could have a format string of e.g. %w (day of the week) which might produce a valid timestamp 0 which would also evaluate to false. Yes, so a comparison against would be more reliable. Thanks, -Brad -- Nils Gladitz, B.Sc. DICOM, Konnektivität und Entwicklung Scivis wissenschaftliche Bildverarbeitung GmbH Bertha-von-Suttner-Str. 5 D-37085 Göttingen GERMANY Handelsregister Nr. / Trade Register No. B3100 Göttingen Geschäftsführer / Managing Directors Dr. Gernot Ebel, Dr. Uwe Engeland Tel: 0049 (0)551 634181-28 E-Mail: glad...@scivis.de Web: www.scivis.de -- Powered by www.kitware.com Visit other Kitware
[cmake-developers] CMake 2.8.10 available for download
On behalf of myself, Ken, Bill, Brad, Alex, Eike, Steve, Eric, Zach, Ben and the rest of the CMake team from all around the world, we are pleased to announce that CMake 2.8.10 is now available for download at: http://www.cmake.org/files/v2.8/?C=M;O=D It is also available from the usual download links found on the CMake web site: http://www.cmake.org/cmake/resources/software.html Some of the notable changes in this release are: - file(DOWNLOAD now handles https URLs -- the pre-built binaries available from Kitware link to OpenSSL - support for the latest available versions of Visual Studio (11 / 2012) and Xcode (4.3, 4.4, 4.5, developer previews) - uniform compiler id and version number variables available for nearly all known compilers and platforms - new way to arrange exported targets that depend on other targets into export sets - new generator expressions - generator expressions available in more contexts, namely in the INCLUDE_DIRECTORIES and COMPILE_DEFINITIONS target properties - new target properties for PDB_OUTPUT_DIRECTORY and PDB_NAME, implemented for Visual Studio 7 and up - and, as always, various minor bug fixes The bug tracker change log page for this version is at: http://public.kitware.com/Bug/changelog_page.php?version_id=100 Following is the complete list of changes in this release, including changes introduced in every release candidate. Please upgrade to this latest and greatest version of CMake for building your projects. Thanks! -Dave Changes in CMake 2.8.10 (since 2.8.10-rc3) -- None Changes in CMake 2.8.10-rc3 (since 2.8.10-rc2) -- Rolf Eike Beer (2): SelectLibraryConfigurations: add testcase SelectLibraryConfigurations: fix for release and debug libs being the same Stephen Kelly (5): BasicConfigVersion: Make docs refer to the macro, not the module name Document LOCATION undefined behavior with use of LINKER_LANGUAGE. GenEx: Add an accessor for imported targets in a makefile. GenEx: Create cmGeneratorTargets for imported targets. GexEx: Validate Target names and property names differently. Thomas Arcila (1): SelectLibraryConfigurations: Fix foreach(x IN LISTS ...) syntax Changes in CMake 2.8.10-rc2 (since 2.8.10-rc1) -- Alex Neundorf (2): Document CMAKE_FIND_PACKAGE_NAME Automoc: fix #13572: issue with symbolic links Brad King (4): cmCTestSVN: Fix compilation with Sun CC 5.1 if: Document that plain 'NOTFOUND' is a false constant string: Clarify regex documentation of '-' behavior FortranCInterface: Pass all flags to VERIFY project (#13579) David Cole (1): NSIS: Fix incorrect uninstall registry key name (#13578) Eric NOULARD (3): CPACK_XX_ON_ABSOLUTE_INSTALL_DESTINATION is now properly checked for ON/OFF Document CPACK_COMPONENT_INCLUDE_TOPLEVEL_DIRECTORY and fix some typo. Make CPACK_SET_DESTDIR work with archive generator + component-based packaging Jean-Christophe Fillion-Robin (1): CTest: Ensure CTEST_USE_LAUNCHERS behaves nicely in Superbuild setup Pere Nubiola i Radigales (1): Find PostgreSQL headers on Debian Peter Kümmel (4): Ninja: also set OBJECT_DIR when compiling Ninja: don't pollute current dir when using gui (#13495) Ninja: implicit dependency for custom command files Fix regression: write compile definitions if any Philip Lowman (4): FindGTK2: Rollback lib64 changes which broke header file finding FindGTK2: #12049 fix detection of header files on multiarch systems FindGTK2: #12596 Missing paths for FindGTK2 on NetBSD FindGTK2: Update local changelog Rolf Eike Beer (6): CTest: fix usage of memory checker with spaces in path CTest: fix pre and post test commands with spaces CTest: add tests that simulate memcheck runs CTest: improve memory checker type detection CTest: add a test for CTEST_CUSTOM_MEMCHECK_IGNORE CTest: add a check with a quoted memory checker Stephen Kelly (18): GenEx: It is not an error to specify an empty parameter GenEx: Return after error reported. GenEx: Report actual target name not found, not 0 each time. GenEx: Parse comma after colon tokens specially GenEx: Validate target and property names. GenEx: Ensure that the empty CONFIGURATION can be used conditionally. GenEx: Add test for $BOOL: with empty parameter. GenEx: Add tests for 0 and 1 expressions with literal commas. GenEx: Don't use std::vector::at(int). Attempt to fix the compile of cmake on Sun CC. GenEx: Parse colon after arguments separator colon specially. GenEx: Test the use of generator expressions to generate lists. GenEx: Fix termination bugs in generator expression parser. GenEx: Break if there are no more commas in the
