Re: [cmake-developers] Peculiar issue for "NMake Makefiles JOM" (GOT IT TO WORK)
Thanks to off-list help from Bill, I now have the following (subject to mail wrapping issues) working with my build_projects project on Wine: bash.exe-3.1$ cmake -G"NMake Makefiles JOM" -DCMAKE_C_COMPILER:FILEPATH=/z/home/wine/newstart/MinGW-4.7.2/bin/gcc.exe -DCMAKE_RC_COMPILER:FILEPATH=/z/home/wine/newstart/MinGW-4.7.2/bin/windres.exe -DCMAKE_INSTALL_PREFIX:PATH=/z/home/wine/newstart/build_script/install-git_mingw /z/home/software/plplot_svn/HEAD/plplot_allura/cmake/build_projects >& cmake.out bash.exe-3.1$ time jom build_ndiff >& build_ndiff.out real0m27.527s user0m0.000s sys 0m0.040s Note, I had to specify both CMAKE_C_COMPILER and CMAKE_RC_COMPILER to get this C build, install, and test of ndiff to work (without disabling the RC language). I also got good build, install, and test results for the shapelib C library. The build time numbers for the "MinGW Makefiles" and "MSYS Makefiles" generators are slightly longer than what I obtained above. So these are promising initial efficiency results for the combination of the "NMake Makefiles JOM" generator and the MinGW suite of compilers for at least the C case. I will continue such experiments with projects that enable C++, Fortran, Ada, and D (e.g., PLplot) as well to see how far I can push this. If I find any real showstoppers I will create appropriate bug reports for the "NMake Makefiles JOM" generator. I also plan to create a bug report about making it easier to use the "NMake Makefiles JOM" generator without having to specify all these CMake_??_COMPILER variables and also suppress the following inappropriate cl-oriented message that appears in results for the MinGW suite of compilers: CMake Warning at CMakeLists.txt:4 (project): To use the JOM generator, cmake must be run from a shell that can use the compiler cl from the command line. This environment does not contain INCLUDE, LIB, or LIBPATH, and these must be set for the cl compiler to work. Alan __ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __ Linux-powered Science __ -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0014232]: cmake can't find X11 (XQuartz)
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14232 == Reported By:Schamschula Assigned To: == Project:CMake Issue ID: 14232 Category: CMake Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2013-06-19 14:43 EDT Last Modified: 2013-06-19 14:43 EDT == Summary:cmake can't find X11 (XQuartz) Description: As of Mac OS X 10.8, X11 is no longer installed under /usr/X11, but under /opt/X11 Steps to Reproduce: run cmake in any project that requires X11 Additional Information: *** /usr/local/share/cmake-2.8/Modules/FindX11.cmake.orig 2013-06-19 13:39:31.0 -0500 --- /usr/local/share/cmake-2.8/Modules/FindX11.cmake2013-06-19 13:39:40.0 -0500 *** *** 69,72 --- 69,73 /usr/openwin/share/include /opt/graphics/OpenGL/include + /opt/X11/include ) *** *** 76,79 --- 77,81 /usr/X11R7/lib /usr/openwin/lib + /opt/X11/lib ) == Issue History Date ModifiedUsername FieldChange == 2013-06-19 14:43 SchamschulaNew 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 0014231]: external project doesn't pass CMAKE_Fortran_COMPILER to subprojects
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=14231 == Reported By:Andy Bauer Assigned To: == Project:CMake Issue ID: 14231 Category: CMake Reproducibility:always Severity: minor Priority: low Status: new == Date Submitted: 2013-06-19 10:30 EDT Last Modified: 2013-06-19 10:30 EDT == Summary:external project doesn't pass CMAKE_Fortran_COMPILER to subprojects Description: When building an external project (ExternalProject_Add) that depends on Fortran, the CMAKE_Fortran_COMPILER doesn't get passed to the external project. I would guess that the other Fortran build options aren't passed either. Steps to Reproduce: 1) Download the ParaView superbuild repo at http://review.source.kitware.com/#/t/2904/ 2) Set the Fortran compiler to a non-default value. 3) Enable the nektar reader plugin (ENABLE_nektarreader) and ParaView (ENABLE_paraview) 4) Configure and build and note that in the paraview/src/paraview-build that there will be the default Fortran compiler that CMake finds. == Issue History Date ModifiedUsername FieldChange == 2013-06-19 10:30 Andy Bauer 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] Add a manifest file to the created jar
On 6/17/2013 12:51 PM, Matthew Woehlke wrote: > I pushed document-add_jar-compat-shims to stage to make this more > explicit. Brad/Andreas/Nicolas, can you please verify that it looks > reasonable? Yes, merged to next, 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
Re: [cmake-developers] Cross-compiling with clang
On 6/13/2013 11:39 AM, Stephen Kelly wrote: > However, even when LDFLAGS is set, the ABI compiler test fails, and the > triple is not automatically determined, or the implicit link dirs etc. Only > the patch to the CMakeDetermineCompilerABI.cmake file I posted helps with > that. Is that expected, or is there a bug somewhere there? I think something like your patch is needed, but perhaps more. If linking flags are needed then of course they should be used in all test builds. This extends to all try_compile calls including those made by CheckSymbolExists and similar modules. See below. >> Shouldn't you create a platform file that sets >> CMAKE_*_LINKER_FLAGS_INIT appropriately? > > I don't follow your thinking. Would such a file live in the cmake tree? What > would it be called and what else would it contain? Well, either in CMake or in CMAKE_MODULE_PATH. However, I think my suggestion may be incorrect because in this case we're working around trouble with the host system's arrangement of the compiler, not anything specific to the target system for which the platform file would be defined. Until now we've depended on platform files always setting things like CMAKE_EXE_LINKER_FLAGS_INIT because they are loaded in the test projects inside try_compile. The LDFLAGS environment variable makes it into them too. Now we have a case where we would like flags specified for linking by the toolchain file to go through also. Therefore we need logic to pass such flags through. The try_compile command already handles CMAKE__FLAGS by itself when generating the project for the srcfile mode. Perhaps it can be taught to do more. -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
