[cmake-developers] [CMake 0012232]: CMake possibly fails to launch devenv.com when disable8dot3 is set on NTFS
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=12232 == Reported By:Felix Nawothnig Assigned To: == Project:CMake Issue ID: 12232 Category: CMake Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2011-05-28 15:26 EDT Last Modified: 2011-05-28 15:26 EDT == Summary:CMake possibly fails to launch devenv.com when disable8dot3 is set on NTFS Description: CMake applies GetShortPathName() on the compiler path with the purpose to generate a space-free string - this doesn't work if the path to devenv.com a) contains a directory with spaces (which it usually does, due to the Microsoft Visual Studio X directory) and b) said directory was created (e.g. MSVC was installed) when disable8dot3 was set to 1. The resulting error is rather cryptic - Check for working C compiler fails with the error message %1 is not a valid Win32 application (including the verbatim %1), as a result of CreateProcess() trying to launch the file C:\Progra~2\Microsoft. Additional Information: As a workaround the user can give the MSVC directory a short-name, after which cmake works fine: fsutil.exe behavior set disable8dot3 0 fsutil.exe file setshortname Microsoft Visual Studio 9.0 msvc~90 fsutil.exe behavior set disable8dot3 1 == Issue History Date ModifiedUsername FieldChange == 2011-05-28 15:26 Felix NawothnigNew Issue == ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[CMake] CMake v.2.8.4 OpenSSL 1.0.0.d
Hi, I just tried to build CMake 2.8.4 on Win7 (MSVC 2010, x64) against OpenSSL 1.0.0.d. I built OpenSSL by hand and started the cmake-gui with the -DOPENSSL_ROOT_DIR set to the build directory and with an appropriately configured CMAKE_INCLUDE_PATH. First, CMake failed because in Utilities\cmcurl\CMakeLists.txt (ll. 183ff) FIND_LIBRARY(LIBEAY NAMES libeay32) and FIND_LIBRARY(SSLEAY NAMES ssleay32) failed. I fixed this by patching the CMakeLists.txt and adding the appropriate PATHS statements for my system. I know, its a little bit invasive but for the moment I did not care. I am wondering why you do not use the results from find_package(OpenSSL). There you already search for those libs and they were found on my system. Anyways, I finally managed to create the project files to the MSVC2010, x64 generator. Now, when I try to build, I am facing a bunch of compilation errors. Some symbols cmcurl needs seem to have changed. E.g. SSL_CTX seems to be undefined. Could it be, that I am using a wrong OpenSSL version? Did you ever test to build CMake against OpenSSL in x64 bit mode? Any hints would be welcome since I would love to stick to my CDash behind https. Regards, Hauke ___ 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] Preserving path information when installing headers
I have a project setup like this:
set(OT_HEADERS
Headers/ObjectTools/_RawFormat/COFF.h
Headers/ObjectTools/Format/COFF.h
Headers/ObjectTools/Object.h
)
add_library(ObjectTools SHARED ${OT_SOURCES} ${OT_HEADERS} ${OT_RESOURCES})
set_target_properties(ObjectTools PROPERTIES
VERSION 0.1.0
SOVERSION 0
RESOURCE ${OT_RESOURCES}
PUBLIC_HEADER ${OT_HEADERS}
FRAMEWORK ${FRAMEWORK})
install(TARGETS ObjectTools
ARCHIVE DESTINATION lib
LIBRARY DESTINATION lib
RUNTIME DESTINATION bin
FRAMEWORK DESTINATION Library/Frameworks
BUNDLE DESTINATION Applications
PUBLIC_HEADER DESTINATION include/ObjectTools
RESOURCE DESTINATION share/ObjectTools)
As you can see, my headers are not laid out in a flat format, and worse,
some have the same file names (This is because the Format/ headers wrap the
(internal) headers in _RawFormat. The trouble I'm having is that CMake
strips all path information when installing the headers resulting in the
headers being in the wrong place (and therefore the cross references being
broken).
I don't see any information in the documentation on how to avoid this from
being an issue is it even possible? If its not, perhaps the next release
of CMake could include a target property to set the header prefix. Perhaps
something like
PUBLIC_HEADER_PREFIX:
Specifies the prefix to be removed from headers when installing them, or
copying them to the Headers directory within a Mac OS X bundle. For example,
if you set this value to include/MyFramework/, and specify a public header
named include/MyFramework/MyHeader.h will be installed as MyHeader.h
relative to the include path.
An alternative option would be similar to the above, except CMake will
additionally strip the framework's (output) name when building on Mac OS X,
since the framework lookup rules will cause the framework name to be
automatically re-inserted.
Many thanks,
-- Owen Shepherd
http://www.owenshepherd.net
owen.sheph...@e43.eu (general) / oshephe...@shef.ac.uk (academic)
___
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 pod cast
Bill, Nice pod cast. The hosts asked very good questions and your responses were right on. They were very objective and your answers were objective. Bill On Thu, May 26, 2011 at 10:14 PM, Bill Hoffman bill.hoff...@kitware.com wrote: Last week I did an interview for the High Performance Computing (HPC) and Research Computing Podcast. It can be found here: http://www.rce-cast.com/ -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 ___ 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
