Re: [cmake-developers] Ninja generator on Windows
On 2/1/2012 10:23 PM, Bill Hoffman wrote: On 2/1/2012 4:19 PM, Peter Kümmel wrote: We can't use cmd. Maybe ninja could be fixed. If not, you could come up with something that uses CMake scripts. cmake -E foo.cmake foo.cmake execute_process() Not ideal, but until ninja figures it out, cmake can become the shell for ninja. That won't handle the problem currently facing Ninja. A cross-platform make tool like Ninja should abstract the shell. -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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] CodeLite generator
On 2/1/2012 5:51 PM, Jim Goodnow II wrote: I am working on a CodeLite generator for CMake. Great! I assume you mean http://www.codelite.org/ ? Is there a set of tests that should be run CMake comes with an extensive test suite that covers the major interfaces plus many corner cases that have been encountered and fixed over the years. If you build CMake from source with the Makefile generator you can run bin/ctest from the top of the build tree to execute all the tests. We expect them to all pass for a new generator. They are contained in the Tests/ subdirectory. Once the feature is working we'd like to have a nightly build submitted to our testing dashboard: http://www.cdash.org/CDash/index.php?project=CMake to ensure that it keeps working. Thanks, -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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0012926]: FindPkgConfig module doesn't honor CMAKE_PREFIX_PATH.
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12926 == Reported By:arrowdodger Assigned To: == Project:CMake Issue ID: 12926 Category: Modules Reproducibility:N/A Severity: minor Priority: low Status: new == Date Submitted: 2012-02-02 10:29 EST Last Modified: 2012-02-02 10:29 EST == Summary:FindPkgConfig module doesn't honor CMAKE_PREFIX_PATH. Description: There is a environment variable PKG_CONFIG_PATH, which makes pkg-config to look for .pc's there first. For now, the only way to pass this variable to the FindPkgConfig i've found is to run cmake executable with this env var set. Wouldn't it be more consistent and neat to make FindPkgConfig to look at CMAKE_PREFIX_PATH? == Issue History Date ModifiedUsername FieldChange == 2012-02-02 10:29 arrowdodgerNew 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
Re: [cmake-developers] Ninja generator on Windows
On 2/2/2012 8:30 AM, Brad King wrote: On 2/1/2012 10:23 PM, Bill Hoffman wrote: On 2/1/2012 4:19 PM, Peter Kümmel wrote: We can't use cmd. Maybe ninja could be fixed. If not, you could come up with something that uses CMake scripts. cmake -E foo.cmake foo.cmake execute_process() Not ideal, but until ninja figures it out, cmake can become the shell for ninja. That won't handle the problem currently facing Ninja. Why not? CMake does not handle in custom commands either. It is expected that custom commands are run one by one. So, a CMake Ninja generator should be able to handle all cases, it might have to create some CMake scripts to do it, but I don't see why we would need anything more from Ninja than the ability to run a single command. -Bill -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Ninja generator on Windows
On Thu, Feb 2, 2012 at 4:34 PM, Bill Hoffman bill.hoff...@kitware.com wrote: On 2/2/2012 8:30 AM, Brad King wrote: On 2/1/2012 10:23 PM, Bill Hoffman wrote: On 2/1/2012 4:19 PM, Peter Kümmel wrote: We can't use cmd. Maybe ninja could be fixed. If not, you could come up with something that uses CMake scripts. cmake -E foo.cmake foo.cmake execute_process() Not ideal, but until ninja figures it out, cmake can become the shell for ninja. That won't handle the problem currently facing Ninja. Why not? CMake does not handle in custom commands either. It is expected that custom commands are run one by one. So, a CMake Ninja generator should be able to handle all cases, it might have to create some CMake scripts to do it, but I don't see why we would need anything more from Ninja than the ability to run a single command. When you use scripts or file like link.txt you lose the power of the special $in and $out variables or variable in general that are expanded in the rule. -- Nicolas Desprès -- 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] Ninja generator on Windows
On 2/2/2012 10:41 AM, Nicolas Desprès wrote: When you use scripts or file like link.txt you lose the power of the special $in and $out variables or variable in general that are expanded in the rule. I am not sure what those are, must be a Ninja thing... With windows, unless you have something like link.txt you are going to run into command line length issues. There is no way to use response files in ninja? -Bill -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Ninja generator on Windows
Sorry for asking a question without looking into the details first... But Why does the ninja generator need to use ? I am pretty sure the other CMake generators do not need to use . -Bill -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 bill.hoff...@kitware.com http://www.kitware.com 518 881-4905 (Direct) 518 371-3971 x105 Fax (518) 371-4573 -- 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] [CMake 0012928]: CMake silently ignores CPPFLAGS
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=12928 == Reported By:Aron Xu Assigned To: == Project:CMake Issue ID: 12928 Category: CMake Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2012-02-02 17:10 EST Last Modified: 2012-02-02 17:10 EST == Summary:CMake silently ignores CPPFLAGS Description: CMake silently ignores CPPFLAGS, which should be accepted from environmental variables. Steps to Reproduce: In top source directory: $ mkdir build cd build $ CPPFLAGS=-D_FORTIFY_SOURCE=2 cmake .. Then grep from all the generated files, there is no such keyword FORTIFY. $ make Again, we cannot find anything related to the CPPFLAGS in generated files after building, which means it's ignored completely. == Issue History Date ModifiedUsername FieldChange == 2012-02-02 17:10 Aron XuNew 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] [CMake 0012929]: The -shared gcc option is not provided for MODULE shared library if PROJECT command declares in ways
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=12929
==
Reported By:Zheng GONG
Assigned To:
==
Project:CMake
Issue ID: 12929
Category: CMake
Reproducibility:always
Severity: minor
Priority: low
Status: new
==
Date Submitted: 2012-02-02 18:52 EST
Last Modified: 2012-02-02 18:52 EST
==
Summary:The -shared gcc option is not provided for MODULE
shared library if PROJECT command declares in ways
Description:
The -shared gcc option is not provided for MODULE shared library, if PROJECT
command declares in some ways.
test cases:
PROJECT (${proj_name}) - OK
PROJECT (${proj_name}C CXX)- OK
without PROJECT command- OK
PROJECT (${proj_name}CXX) - FAIL
PROJECT (${proj_name}CXX C)- FAIL
CMAKE_SHARED_MODULE_CREATE_C_FLAGS gets its initial value in
CMakeCInformation.cmake from CMAKE_SHARED_LIBRARY_CREATE_C_FLAGS.
It seems that if CMakeCXXInformation.cmake is called before
CMakeCInformation.cmake, The variable CMAKE_SHARED_MODULE_CREATE_CXX_FLAGS will
take the default value of CMAKE_SHARED_MODULE_CREATE_C_FLAGS which is blank at
that moment.
As shown in CMakeCXXInformation.cmake files:
161 # repeat for modules
162 IF(NOT CMAKE_SHARED_MODULE_CREATE_CXX_FLAGS)
163 SET(CMAKE_SHARED_MODULE_CREATE_CXX_FLAGS
${CMAKE_SHARED_MODULE_CREATE_C_FLAGS})
164 ENDIF(NOT CMAKE_SHARED_MODULE_CREATE_CXX_FLAGS)
The -shared gcc option is provided for SHARED library in any case.
Since CMakeGenericSystem.cmake gives CMAKE_SHARED_LIBRARY_CREATE_C_FLAGS default
value -shared. And in CMakeCXXInformation.cmake, '-shared' is passed to
CMAKE_SHARED_LIBRARY_CREATE_CXX_FLAGS.
Steps to Reproduce:
CMakeLists.txt file:
PROJECT (test CXX)
ADD_LIBRARY(a MODULE a.cpp)
a.cpp file:
int a(void){ return 0;
}
compile with MinGW, related log:
Linking CXX shared module liba.dll
C:\cmake-2.8.7-win32-x86\bin\cmake.exe -E cmake_link_script
CMakeFiles\a.dir\link.txt --verbose=1
C:\cmake-2.8.7-win32-x86\bin\cmake.exe -E remove -f CMakeFiles\a.dir/objects.a
C:\MinGW\bin\ar.exe cr CMakeFiles\a.dir/objects.a @CMakeFiles\a.dir\objects1.rsp
C:\MinGW\bin\g++.exe -o liba.dll
-Wl,--major-image-version,0,--minor-image-version,0 -Wl,--whole-archive
CMakeFiles\a.dir/objects.a -Wl,--no-whole-archive -lkernel32 -luser32 -lgdi32
-lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32
c:/mingw/bin/../lib/gcc/mingw32/4.6.2/../../../libmingw32.a(main.o): In function
`main':
C:\MinGW\msys\1.0\src\mingwrt/../mingw/main.c:73: undefined reference to
`WinMain@16'
in which, CMAKE_SHARED_MODULE_CREATE_CXX_FLAGS is empty rather than '-shared'
which cause the failure.
==
Issue History
Date ModifiedUsername FieldChange
==
2012-02-02 18:52 Zheng GONG New 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
Re: [cmake-developers] Ninja generator on Windows
2012/2/2 Bill Hoffman bill.hoff...@kitware.com: Sorry for asking a question without looking into the details first... But No problem. Why does the ninja generator need to use ? I am pretty sure the other CMake generators do not need to use . Most of them come from the working directory: cd foo g++ They could be worked around easly by adding a new variable to the rules. Others comes from the support of PRE_BUILD, POST_BUILD, and custom target / commands with more than one command. In ninja, contrary to make, when specifying a build statement (e.g. foo.o: foo.c foo.h) you can attach only one rule (e.g. one command) and not several like in make. They have been several discussion thread for adding basic shell features like in Ninja: - redirection - environment variable - working directory - chainning There is no patch proposal yet AFAIK. Cheers, -- Nicolas Desprès -- 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] Install selected|group of targets
On 02/02/2012 08:44 AM, Joakim Hove wrote: First you should use the COMPONENT parameter of the INSTALL command. See: cmake --help-command install and http://www.cmake.org/Wiki/CMake:Component_Install_With_CPack then you may install all the target/files/... belonging to a particular component by doing: cd buildir cmake -DCOMPONENT=componentname -P cmake_install.cmake http://www.april.org OK; thank you. That was maybe slightly more involved than I had thougth - but certainly doable. Joakim I implemented the make install-foo feature some time ago, but didn't find the time to write the required tests, so it never got merged into CMake: http://cmake.org/Bug/view.php?id=10531 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] Install selected|group of targets
I implemented the make install-foo feature some time ago, but didn't find the time to write the required tests, so it never got merged into CMake: OK - I have never looked at the CMake source code, and am in general quite rusty in C++ - but in my opinion this would have been a very valuable addition to CMake. Joakim -- 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] Install selected|group of targets
2012/2/2 Joakim Hove joakim.h...@gmail.com: I implemented the make install-foo feature some time ago, but didn't find the time to write the required tests, so it never got merged into CMake: OK - I have never looked at the CMake source code, and am in general quite rusty in C++ - but in my opinion this would have been a very valuable addition to CMake. You can add yourself in the monitoring list of the feature request: http://cmake.org/Bug/view.php?id=10531 and comment in there. I suggested an alternative to Michael proposal, which may lead to a simpler implementation. but will replace make install-foo by make COMPONENT=foo install That said as Michael noted in the report, the feature is missing a test case, may be you can work on providing a simple test case for 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
[CMake] CheckIncludeFiles problem
Dear all, I have a problem with CheckIncludeFiles that I cannot figure out. I'm sure I'm just making a stupid mistake though, but I am unable to figure out what. The following code is in CMakeLists.txt: include(CheckIncludeFiles) check_include_files(readline/history.h HAVE_READLINE_HISTORY_H) check_include_files(sys/select.h HAVE_SYS_SELECT_H) And both headers are installed on my system: $ ls -lh /usr/include/sys/select.h /usr/include/readline/history.h -rw-r--r-- 1 root root 9,9K 21.07.2011 04:40 /usr/include/readline/history.h -rw-r--r-- 1 root root 4,1K 26.10.2011 20:03 /usr/include/sys/select.h CMake only finds sys/select.h though, and I don't see the difference. What might I be missing? I use cmake version 2.8.7. Thanks! 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] CheckIncludeFiles problem
May be, there is an error when the compiler process the header file. During CHECK_INCLUDE_FILES CMake invokes the Compiler to check whether the header file works fines. In most cases reason is a missing additional header files (but not always). So, check the log files of CMake in the binary directory of your project. Greetings Micha Am Donnerstag, den 02.02.2012, 11:58 +0100 schrieb Yngve Inntjore Levinsen: Dear all, I have a problem with CheckIncludeFiles that I cannot figure out. I'm sure I'm just making a stupid mistake though, but I am unable to figure out what. The following code is in CMakeLists.txt: include(CheckIncludeFiles) check_include_files(readline/history.h HAVE_READLINE_HISTORY_H) check_include_files(sys/select.h HAVE_SYS_SELECT_H) And both headers are installed on my system: $ ls -lh /usr/include/sys/select.h /usr/include/readline/history.h -rw-r--r-- 1 root root 9,9K 21.07.2011 04:40 /usr/include/readline/history.h -rw-r--r-- 1 root root 4,1K 26.10.2011 20:03 /usr/include/sys/select.h CMake only finds sys/select.h though, and I don't see the difference. What might I be missing? I use cmake version 2.8.7. Thanks! 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 -- 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] Enhancement to CHECK_C_RUNS_SOURCE
On Wednesday 01 February 2012, Clifford Yapp wrote: We currently have a minor local enhancement to CHECK_C_RUNS_SOURCE that I would like to contribute back to the main module, if it is acceptable to the developers of CMake: We often have our own .c file stored in our tree for TRY_RUN testing, and it is convenient to be able to use CHECK_C_RUNS_SOURCE for testing those .c files. At the moment, CHECK_C_RUNS_SOURCE assumes the incoming SOURCE variable actually holds the source code - our enhancement checks to see if SOURCE holds a valid file path first. If it DOES hold a valid file path, TRY_RUN then trys that .c file, otherwise the existing CHECK_C_RUNS_SOURCE is preserved. I don't know of any sane pathname that would be valid C code or vice versa, so there should be no danger of passing in a C source snippit and having it mistaken for a file path. The diff is below - would this be of interest for main-line CMake? I think so. In this case, this should also be added to CheckCXXSourceRuns, CheckCSourceCompiles and CheckCXXSourceCompiles. 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
[CMake] CMAKE 2.8.5 - CMAKE_GENERATOR Bug?
All, I was trying to use the external project add feature to add a 32-bit VC++ project on a 64-bit parent build system. However, I ran into problems while compiling the 32-bit project. devenv used to complain invalid solution configuration I tried to explicitly set CMAKE_BUILD_TYPE using -D option as well as in the CMakeLists.txt. Nothing changed. However, when I enabled CMAKE_VERBOSE_MAKEFILE, I found that CMAKE was not passing the -G option correctly. Instead of passing cmake -G Visual Studio 9 2008, cmake was actually configuring the project as cmake -G Visual Studio 9 2008 (Note that -G is inside the double-quote) When I isolate the build-step and build it manually using the correct syntax, everything works flawlessly. Specifying the generator via CMAKE_ARGS helps me compile. But CMAKE still appends the faulty -G syntax and hence is not producing the intended results for me. If this is indeed a bug, can some one tell me: 1.What is the temporary workaround for this? 2.If at all fixed, how long will it take the build to come out? Thanks, Best Regards, Sarnath ::DISCLAIMER:: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. --- -- 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 2.8.5 - CMAKE_GENERATOR Bug?
On Thu, Feb 2, 2012 at 12:33 PM, Sarnath K - ERS, HCLTech k_sarn...@hcl.com wrote: All, I was trying to use the external project add feature to add a 32-bit VC++ project on a 64-bit parent build system. However, I ran into problems while compiling the 32-bit project. “devenv” used to complain “invalid solution configuration” I tried to explicitly set “CMAKE_BUILD_TYPE” using –D option as well as in the CMakeLists.txt. Nothing changed. However, when I enabled “CMAKE_VERBOSE_MAKEFILE”, I found that “CMAKE” was “not” passing the –G option correctly. Instead of passing cmake –G “Visual Studio 9 2008”, cmake was actually configuring the project as cmake “-G Visual Studio 9 2008” (Note that –G is inside the double-quote) When I isolate the build-step and build it manually using the correct syntax, everything works flawlessly. Specifying the generator via “CMAKE_ARGS” helps me compile. But CMAKE still appends the faulty –G syntax and hence is not producing the intended results for me. If this is indeed a bug, can some one tell me: 1. What is the temporary workaround for this? 2. If at all fixed, how long will it take the build to come out? I am not seeing this breakage. However you are 2 versions behind in cmake. John -- 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] link library paths
I'm trying to link to libraries located in /usr/lib. This is a very simple example using boost::python and Qt. Here's my cmake file : http://codepad.org/tZxBzXVP I added the link_directories command only after the initial link failed. The docs say this is rarely needed since find_package returns absolute paths and these should be passed to target_link_libraries. As far as I can this is exactly what FindQt4 returns and is what's passed to target_link_libraries. Here's the output of the link command : http://codepad.org/lZg8N3l0 Output of the message commands : Running CMake to regenerate build system... QT_LIBRARIES = /usr/lib/libQtGui.so;/usr/lib/libQtCore.so QT_LIBRARY_DIR = /usr/lib Any ideas? 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] ICC + Windows
On 2/1/2012 2:05 PM, Roland Schulz wrote: what is the recommended Generator to compile on Windows with ICC on the shell? If I try to use the Visual Studio 2010 (or 2008) generator There is an open issue tracker entry requesting direct .icproj file generation: http://www.cmake.org/Bug/view.php?id=6929 So far we've not had resources available to implement it. If I try to use the NMake generator instead then I get: The NMake generator is expected to work when CMake is run from a command prompt with the proper environment configured. src\gmxlib\CMakeFiles\gmx.dir\flags.make(5) : fatal error U1001: syntax error : illegal character '-' in macro Somehow the NMake generator uses dashes instead of slashes for options. AFAIK most windows tools support either / or - for options. In order to diagnose this further I'd need to see the actual flags.make file or line in question. -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] Enhancement to CHECK_C_RUNS_SOURCE
OK - how should I proceed? File a bug report and submit patches for all of the files? Cheers, CY On Thu, Feb 2, 2012 at 11:59 AM, Alexander Neundorf a.neundorf-w...@gmx.net wrote: I think so. In this case, this should also be added to CheckCXXSourceRuns, CheckCSourceCompiles and CheckCXXSourceCompiles. 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
[CMake] Portable revision lookup?
Right now I wrap my Linux-based build process with a script that
features the line
REVISION=`svn info ${SRC_PATH} | awk '/^Revision/ { print $2 }'`
Which is neither OS or VCS portable.
I'm trying to put together a CPack configuration to make the builds, and
I'd like to name the resulting installer for the revision it was built from.
Is there any kind of built-in mechanism I can use for this, or would I
be best just using IFs and executing os-specific commands? (I'm not
quite sure how I'm going to pluck the info out under Windows)
I'm also wondering if there is a way to query other repository
attributes - specifically the URL - I'd like to build installers named
product.branch.revision.suffix
e.g.
my-client.baseline.57721.deb
or
my-server.branches.1.35.57804.tbz2
Any pointers?
- Oliver
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CheckIncludeFiles problem
Hi Micha, Aha, thanks! That was more clever than I would expect, and it was the problem. readline/history.h was dependent on stdio.h being include beforehand. Just in case anyone else reads this mail in the future, here is a documentation on how to check an array of include files: http://www.cmake.org/Wiki/CMake:How_To_Write_Platform_Checks For instance: CHECK_INCLUDE_FILES (stdio.h;readline/history.h HAVE_READLINE_HISTORY_H) Cheers, Yngve On Torsdag 2. februar 2012 13.46.09, Micha Renner wrote: May be, there is an error when the compiler process the header file. During CHECK_INCLUDE_FILES CMake invokes the Compiler to check whether the header file works fines. In most cases reason is a missing additional header files (but not always). So, check the log files of CMake in the binary directory of your project. Greetings Micha Am Donnerstag, den 02.02.2012, 11:58 +0100 schrieb Yngve Inntjore Levinsen: Dear all, I have a problem with CheckIncludeFiles that I cannot figure out. I'm sure I'm just making a stupid mistake though, but I am unable to figure out what. The following code is in CMakeLists.txt: include(CheckIncludeFiles) check_include_files(readline/history.h HAVE_READLINE_HISTORY_H) check_include_files(sys/select.h HAVE_SYS_SELECT_H) And both headers are installed on my system: $ ls -lh /usr/include/sys/select.h /usr/include/readline/history.h -rw-r--r-- 1 root root 9,9K 21.07.2011 04:40 /usr/include/readline/history.h -rw-r--r-- 1 root root 4,1K 26.10.2011 20:03 /usr/include/sys/select.h CMake only finds sys/select.h though, and I don't see the difference. What might I be missing? I use cmake version 2.8.7. Thanks! 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 -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Fwd: Portable revision lookup?
-- Forwarded message --
From: John Drescher dresche...@gmail.com
Date: Thu, Feb 2, 2012 at 4:36 PM
Subject: Re: [CMake] Portable revision lookup?
To: Oliver kfsone Smith osm...@playnet.com
On Thu, Feb 2, 2012 at 4:10 PM, Oliver kfsone Smith osm...@playnet.com wrote:
Right now I wrap my Linux-based build process with a script that features
the line
REVISION=`svn info ${SRC_PATH} | awk '/^Revision/ { print $2 }'`
Which is neither OS or VCS portable.
I'm trying to put together a CPack configuration to make the builds, and I'd
like to name the resulting installer for the revision it was built from.
Is there any kind of built-in mechanism I can use for this, or would I be
best just using IFs and executing os-specific commands? (I'm not quite sure
how I'm going to pluck the info out under Windows)
I'm also wondering if there is a way to query other repository attributes -
specifically the URL - I'd like to build installers named
product.branch.revision.suffix
e.g.
my-client.baseline.57721.deb
or
my-server.branches.1.35.57804.tbz2
Any pointers?
Cmake has support for pulling the svn and I believe git revs using
cmake modules. Here is what I do for svn
#-
# If subversion is found append the svn rev to the patch version.
#
FIND_PACKAGE(Subversion)
IF(Subversion_FOUND)
OPTION(SVN_APPEND_REV Append subversion rev to application version ON)
IF(SVN_APPEND_REV)
Subversion_WC_INFO(${PROJECT_SOURCE_DIR} Project)
MESSAGE(Current revision is ${Project_WC_REVISION})
OPTION(SVN_GET_LOG Get the SVN LOG OFF)
if(SVN_GET_LOG)
Subversion_WC_LOG(${PROJECT_SOURCE_DIR} Project)
MESSAGE(Last changed log is
${Project_LAST_CHANGED_LOG})
endif(SVN_GET_LOG)
set (${PROJECT_NAME}_VERSION_PATCH
${${PROJECT_NAME}_VERSION_PATCH}.${Project_WC_REVISION})
ENDIF(SVN_APPEND_REV)
ENDIF(Subversion_FOUND)
John
--
John M. Drescher
--
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] Portable revision lookup?
John Drescher said the following on 2/2/2012 3:36 PM: Cmake has support for pulling the svn and I believe git revs using cmake modules. Here is what I do for svn Much appreciated -- I just didn't think to look in the Find package, duly noted for future reference. - Oliver -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Portable revision lookup?
Oliver kfsone Smith said the following on 2/2/2012 4:17 PM:
John Drescher said the following on 2/2/2012 3:36 PM:
Cmake has support for pulling the svn and I believe git revs using
cmake modules. Here is what I do for svn
Much appreciated -- I just didn't think to look in the Find package,
duly noted for future reference.
- Oliver
Hrm - ran into a problem with that, the revision is only produced when
cmake rolls the Makefiles. I.e, if you do the following:
$ cd /tmp mkdir cmake-test cd cmake-test svnadmin create repo
svn co file:///tmp/cmake-test/repo src || echo Failed
$ cat CMakeLists.txt END_CMAKE
CMAKE_MINIMUM_REQUIRED(VERSION 2.8)
PROJECT(Test)
FIND_PACKAGE(Subversion REQUIRED)
MESSAGE(Checking SVN Info of ${Test_SOURCE_DIR} - Repo)
Subversion_WC_INFO(${Test_SOURCE_DIR} Repo)
MESSAGE(Repo_WC_REVISION = ${Repo_WC_REVISION})
$ cmake -G Unix Makefiles .
...
$ make
...
/Repo_WC_REVISION=0/
$ svn add CMakeLists.txt svn commit -m Bump to revision 1 svn update
...
/At revision 1./
$ make
/Repo_WC_REVISION=0/
In particular, this prevents me using it to generate CPack package names :(
- Oliver
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] CPack / Debian install location
osmith@luciddev:~/pn/WW2/src$ cmake --version
cmake version 2.8.2
I can't see to get make package to generate Debian packages that
install any place but /usr/bin. (I actually want them in
/playnet/ra/bin, /playnet/ra/lib and so on)
SET(CPACK_GENERATOR DEB)
SET(CPACK_INSTALL_PREFIX /playnet/ra)
SET(CPACK_PACKAGE_INSTALL_PREFIX /playnet/ra)
SET(CPACK_DEBIAN_INSTALL_PREFIX /playnet/ra)
SET(CPACK_PACKAGE_VERSION
${REPO_WC_REVISION}.${CMAKE_BUILD_TYPE}-${WW2_TARGET_ENV})
SET(CPACK_PACKAGE_NAME servers)
SET(CPACK_PACKAGE_VENDOR Cornered Rat Software)
SET(CPACK_PACKAGE_DESCRIPTION_SUMMARY Game servers)
SET(CPACK_PACKAGE_DESCRIPTION 'Game servers and tools.)
SET(CPACK_DEBIAN_PACKAGE_MAINTAINER Oliver Smith)
SET(CPACK_DEBIAN_PACKAGE_INSTALL_PREFIX /playnet/ra)
SET(CPACK_DEBIAN_PACKAGE_DEPENDS libopenthreads-dev (= 2.8.3-4),
lua5.1 (= 5.1.4-5), libmysqlclient16 (= 5.1.49), bash (= 4.1),
gdb (= 7.2), nfs-common, mysql-server (= 5.1), nfs-kernel-server)
SET(CPACK_DEBIAN_PACKAGE_DESCRIPTION Game servers)
SET(CPACK_DEBIAN_PACKAGE_SECTION Network)
SET(CPACK_DEBIAN_PACKAGE_PRIORITY Important)
SET(CPACK_DEBIAN_PACKAGE_RECOMMENDS vim, mysql-client (= 5.1),
python (= 2.6.6))
SET(CPACK_DEBIAN_PACKAGE_SUGGESTS lvm2, perl (= 5.1))
I've played with a half dozen other variable name combinations, but it
still all goes into /usr.
- Oliver
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] link library paths
On 02.02.12 11:51:11, Alex Olivas wrote: I'm trying to link to libraries located in /usr/lib. This is a very simple example using boost::python and Qt. Here's my cmake file : http://codepad.org/tZxBzXVP I added the link_directories command only after the initial link failed. Using link_directories is almost always wrong. Especially for a standard directory like /usr/lib. Also Boost_INCLUDE_DIRS is most certainly not a directory containing shared libs. Can you post the linker line without link_directories? Maybe also try to remove the unsetting of the shared-lib prefix. The linker-line you posted is wrong, but normally CMake will use absolute paths in the linker-line, so something causes it to not do this. Andreas -- 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] Compile flag issues and VS Express
I think 10M is an insanely large default stack size. It just encourages people to create int foo[100][100][100] on the stack instead of learning how to use malloc or new. When creating non-cmake Visual Studio projects the default stack size is way more sensible. I can't see any reason to default to 10M for cmake generated projects and would love to see this default removed. As it is I have to override it for all my projects. -- Glenn On 1 February 2012 10:14, Yuri Timenkov y...@timenkov.ru wrote: I can assume that 10M stack is reasonable for C code, where it's usual to allocate temporary buffers on stack (in C++ it's easier to use heap, e.g. using std::vector). Bad thing is - impact of this flag is detected only at run time. If with /Zm your code just won't compile, with /STACK everything compiles and links perfectly, works fine in simple cases, but you'll receive OOM under load (in C, when stack will be over). That's why I didn't insist on changing behavior when found this bug 3 years ago. On Tue, Jan 31, 2012 at 8:02 PM, Glenn Coombs glenn.coo...@gmail.comwrote: On a related note: http://www.gccxml.org/Bug/view.php?id=12437 can you check if ITK and VTK build fine without the large stack size argument (/STACK:1000) as well ? -- Glenn On 30 January 2012 15:58, Bill Lorensen bill.loren...@gmail.com wrote: ITK and VTK both build fine if I remove the /Zm1000 flag. On Mon, Jan 30, 2012 at 10:44 AM, Bill Hoffman bill.hoff...@kitware.com wrote: On 1/28/2012 10:51 AM, David Cole wrote: Seems reasonable. Is anybody worried that changing the default values of these flags would have a negative impact on any projects out there? (i.e. is it likely that anybody relies on these flags being present and that would somehow break their build without them...? I don't think it's likely, but I'm willing to discuss before making a change in CMake) They were originally put in for VTK/ITK. They would be the projects to try. -Bill -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake -- Unpaid intern in BillsBasement at noware dot com -- 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
[CMake] how to specify a different source directory
I have a project file and within it I have created a test folder and placed some testing code there. From my test CMakelist, I need to access a .cpp file from the parent folder but I am not sure how to do this? Thus the call to add_executable fails because it can't locate the source file. -- Kind Regards, Rajinder Yadav -- 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] link library paths
I don't know what the issue was, but it's fixed in a later version. I upgraded from 2.8.2 to 2.8.7 and the problem went away. So when you say my linker-line is wrong, you mean in the verbose output there's no '-L/usr/lib' passed to ld, right? Or is there something wrong with my cmake file, other than the use of link_directories? Thanks, Alex. On 2/2/12 4:35 PM, Andreas Pakulat wrote: On 02.02.12 11:51:11, Alex Olivas wrote: I'm trying to link to libraries located in /usr/lib. This is a very simple example using boost::python and Qt. Here's my cmake file : http://codepad.org/tZxBzXVP I added the link_directories command only after the initial link failed. Using link_directories is almost always wrong. Especially for a standard directory like /usr/lib. Also Boost_INCLUDE_DIRS is most certainly not a directory containing shared libs. Can you post the linker line without link_directories? Maybe also try to remove the unsetting of the shared-lib prefix. The linker-line you posted is wrong, but normally CMake will use absolute paths in the linker-line, so something causes it to not do this. Andreas -- 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 specify a different source directory
On Thu, Feb 2, 2012 at 7:46 PM, Dev Guy devguy...@gmail.com wrote: I have a project file and within it I have created a test folder and placed some testing code there. From my test CMakelist, I need to access a .cpp file from the parent folder but I am not sure how to do this? Thus the call to add_executable fails because it can't locate the source file. OK I figured out when I pass in the source file to add_executable, I just need to prefix the source file with ../ Is this the proper way to do it, or should I be using another cmake command to declare a source folder? Thanks, Rajinder -- 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 specify a different source directory
That sounds about right to me. (though personally, I like to make my
tests include the files they are testing by linking to a library
containing them...)
If you wanted to abstract the location away from the test code, you
could set a variable containing the source files in a higher (or
earlier) CMake scope and use that variable to within the deeper scope to
add them to your executable.
/foo/CMakeLists.txt
#[...]
set(FilesToIncludeInTestExe
${CMAKE_CURRENT_LIST_DIR}/file1.cpp
${CMAKE_CURRENT_LIST_DIR}/file2.cpp
${CMAKE_CURRENT_LIST_DIR}/file3.cpp
${CMAKE_CURRENT_LIST_DIR}/file4.cpp
)
#[...]
/foo/foo_test/CMakeLists.txt
#[...]
add_executable(foo_test ${fooTestFiles} ${FilesToIncludeInTestExe} )
#[...]
Some other alteratives might be to set a Global or target property in
the parent CMakeLists.txt and read it in the child one.
Aaron Meadows
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Dev Guy
Sent: Thursday, February 02, 2012 8:11 PM
To: CMake mailing list
Subject: Re: [CMake] how to specify a different source directory
On Thu, Feb 2, 2012 at 7:46 PM, Dev Guy devguy...@gmail.com wrote:
I have a project file and within it I have created a test folder and
placed some testing code there. From my test CMakelist, I need to
access a .cpp file from the parent folder but I am not sure how to do
this?
Thus the call to add_executable fails because it can't locate the
source file.
OK I figured out when I pass in the source file to add_executable, I
just need to prefix the source file with ../
Is this the proper way to do it, or should I be using another cmake
command to declare a source folder?
Thanks,
Rajinder
--
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
This email was sent to you by Thomson Reuters, the global news and information
company. Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be the views of
Thomson Reuters.
--
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 2.8.5 - CMAKE_GENERATOR Bug?
Hello John,
I can +vely see this behavior with the latest 2.8.7 version as well.
I am using a windows 64-bit machine with Visual studio 2008 installed on it.
This is how I use Externa Project Add command:
include(ExternalProject)
ExternalProject_Add(
gen
CMAKE_GENERATOR Visual Studio 9 2008
URL file://${CMAKE_SOURCE_DIR}/src/tools/gen
INSTALL_COMMAND
)
The CMakeLists.txt hosting this ExternalProject_Add is generated using NMake
Makefiles - which uses the default 64-bit build configuration.
A verbose Makefile generation nails the issue.
The gen project is generated as cmake -G Visual Studio 9 2008 which
screws things up.
Can somebody please help me with this?
Thanks,
Best Regards,
Sarnath
-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Thursday, February 02, 2012 11:12 PM
To: Sarnath K - ERS, HCLTech
Cc: cmake@cmake.org
Subject: Re: [CMake] CMAKE 2.8.5 - CMAKE_GENERATOR Bug?
On Thu, Feb 2, 2012 at 12:33 PM, Sarnath K - ERS, HCLTech
k_sarn...@hcl.com wrote:
All,
I was trying to use the external project add feature to add a 32-bit VC++
project on a 64-bit parent build system.
However, I ran into problems while compiling the 32-bit project.
devenv used to complain invalid solution configuration
I tried to explicitly set CMAKE_BUILD_TYPE using -D option as well as in
the CMakeLists.txt.
Nothing changed.
However, when I enabled CMAKE_VERBOSE_MAKEFILE, I found that CMAKE was
not passing the -G option correctly.
Instead of passing cmake -G Visual Studio 9 2008, cmake was actually
configuring the project as cmake -G Visual Studio 9 2008
(Note that -G is inside the double-quote)
When I isolate the build-step and build it manually using the correct
syntax, everything works flawlessly.
Specifying the generator via CMAKE_ARGS helps me compile. But CMAKE still
appends the faulty -G syntax and
hence is not producing the intended results for me.
If this is indeed a bug, can some one tell me:
1.What is the temporary workaround for this?
2.If at all fixed, how long will it take the build to come out?
I am not seeing this breakage. However you are 2 versions behind in cmake.
John
::DISCLAIMER::
---
The contents of this e-mail and any attachment(s) are confidential and intended
for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates.
Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the
opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of
this message without the prior written consent of the author of this e-mail is
strictly prohibited. If you have
received this email in error please delete it and notify the sender
immediately. Before opening any mail and
attachments please check them for viruses and defect.
---
--
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] link library paths
On 02.02.12 18:37:03, Alex Olivas wrote: I don't know what the issue was, but it's fixed in a later version. I upgraded from 2.8.2 to 2.8.7 and the problem went away. So when you say my linker-line is wrong, you mean in the verbose output there's no '-L/usr/lib' passed to ld, right? No, the error is to use -llibfoo, the linker then searches for a file called liblibfoo.so which does not not exist. But as I said, if you pass absolute paths to CMake it usually uses them (I'm not sure right now about that when the directory is a system-link-directory) Or is there something wrong with my cmake file, other than the use of link_directories? My guess would've been for the setting of the shared-lib prefix, maybe thats whats causing the older CMake version to generate a -llibfoo argument for the linker. Andreas -- 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.7-267-g46a734c
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 46a734cdbd4c2ffb5af64a3f0d8a5c48c47b8140 (commit) from e8584401852a871b6cda57e570b7bb04b6dacf74 (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=46a734cdbd4c2ffb5af64a3f0d8a5c48c47b8140 commit 46a734cdbd4c2ffb5af64a3f0d8a5c48c47b8140 Author: KWSys Robot kwro...@kitware.com AuthorDate: Fri Feb 3 00:05:06 2012 -0500 Commit: KWSys Robot kwro...@kitware.com CommitDate: Fri Feb 3 00:05:06 2012 -0500 KWSys Nightly Date Stamp diff --git a/Source/kwsys/kwsysDateStamp.cmake b/Source/kwsys/kwsysDateStamp.cmake index 664bf6f..f2998f6 100644 --- a/Source/kwsys/kwsysDateStamp.cmake +++ b/Source/kwsys/kwsysDateStamp.cmake @@ -18,4 +18,4 @@ SET(KWSYS_DATE_STAMP_YEAR 2012) SET(KWSYS_DATE_STAMP_MONTH 02) # KWSys version date day component. Format is DD. -SET(KWSYS_DATE_STAMP_DAY 02) +SET(KWSYS_DATE_STAMP_DAY 03) --- 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
