[cmake-developers] [CMake 0015636]: alias libraries and and --graphviz
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=15636 == Reported By:tim blechmann Assigned To: == Project:CMake Issue ID: 15636 Category: CMake Reproducibility:have not tried Severity: minor Priority: normal Status: new == Date Submitted: 2015-06-30 00:54 EDT Last Modified: 2015-06-30 00:54 EDT == Summary:alias libraries and and --graphviz Description: when alias libraries are used, the dot files treat original and aliased library as different targets. therefore the dependencies are not visualised. this issue is somehow related to http://www.cmake.org/Bug/view.php?id=13809, which is about add_dependency. Steps to Reproduce: add_library(foo) add_library(bar ALIAS foo) add_executable(baz) target_link_libraries(baz bar) expected behaviour: baz should visualise a dependency to foo. instead foo it shows a dependency to bar. == Issue History Date ModifiedUsername FieldChange == 2015-06-30 00:54 tim blechmann New Issue == -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] FindPython.cmake alternative for FindPythonInterp.cmake and FindPythonLibs.cmake
I have attached an alternative module that replaces the two current modules for finding python-related info. With the current modules it is easy to end up in a situation where the interpreter’s version and the library version do not match, which inevitably leads to problems. My version fixes that and defines a number of other useful things: - PYTHON_SITE_MODULES: the directory where python modules should be installed. - Various PYTHON_VERSION_* variables. - A find_python_module macro, so that you can do something like "find_python_module(numpy REQUIRED)” If you call "cmake -DPYTHON_EXEC=/my/own/python”, you can be sure that everything else is defined appropriately. It is harder to do that with the current Python modules. I have been using this module for a while for my own project, but perhaps it is useful for inclusion with cmake. Let me know if there’s any interest in this. Best, Mark FindPython.cmake Description: Binary data signature.asc Description: Message signed with OpenPGP using GPGMail -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Adding Swift support to CMake
On 06/25/2015 09:24 AM, Eric Wing wrote: > I pushed up a couple of repos for everybody to try. Thanks. From that I was able to make some progress with getting CMakeDetermineSwiftCompiler to work. I've made two tweaks to CMakeDetermineCompilerId to make it easier to use from a new CMakeDetermineSwiftCompiler module: CMakeDetermineCompilerId: Simplify src reference in IDE projects http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8306108f CMakeDetermineCompilerId: Use per-language regex to match Xcode compiler tool http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6452291c Once these changes test cleanly on nightly builds I will look at the rest of the changes for basic Swift + Xcode. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] C# support?
> -Original Message- > From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] > On Behalf Of David Cole via cmake-developers > Sent: Monday, June 29, 2015 17:31 > To: Brad King > Cc: cmake-developers@cmake.org > Subject: Re: [cmake-developers] C# support? > > The C# compiler, csc.exe, takes all its arguments at once in one call to build a > library or executable. Listing all the sources, and its references (other libraries > it depends on) all at once. You can do it as command line arguments, or as > contents of a response file, or a combination or arguments plus response file. > > Conceptually, it's "just like Java." Exactly right; it's like a combined compiler+linker. It's also worth noting that the C# and VB .NET languages doesn't have the concept of "#include" preprocessor directives. Header files are a non-issue. (Once you got that working, I'd imagine Java language support would be easy, too...) > They do have separate project files for it with VS, though. The generators will > need code to generate *.csproj files, rather than custom commands in a > vcxproj file, to make it seem like it's really well-integrated with VS. Not sure if > *.csproj files have evolved much over the last few releases of VS -- I'd expect > the major challenge with this to be making sure CMake generates proper > *.csproj files for however many versions of VS it would take to make it > acceptable. Csproj files are MSBuild compatible, like how Visual C++ 2010 vcxproj files are. While Visual C++ went to MSBuild recently (VS2010), Visual C# has been MSBuild compatible since MSBuild's inception - Visual Studio 2005 if I remember right. Visual Studio 2002/2003 might be different since they pre-date MSBuild but since the VC++ 2002 generator was recently deprecated I'd argue these versions can be ignored. (if someone uses that version still, they could at least use csc.exe directly via a Makefile generator) So, since VS2005, I think you'd find small changes (new flags introduced, etc.) but no major file format overhaul like from VC++ 2008 to VC++ 2010. I'd also like to take this opportunity to point out that whoever does this might want to consider supporting VB .NET also. Everything in this discussion is EXACTLY the same, except that the compiler name is different, and project/source code file extensions are different. It would be relatively trivial to support VB .NET once you have C# working, if you wrote the generator right. (vbc.exe instead of csc.exe, vbproj instead of csproj, .vb file instead of .cs file. Compiler switches are probably almost identical... It's also MSBuild-based and also does a combined "compile+link".) Best regards, James Johnston -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] C# support?
On Mon, Jun 29, 2015 at 10:05 AM, Brad King wrote: > On 06/26/2015 10:47 AM, Stuermer, Michael SP/HZA-ZSEP wrote: > > Does it have a realistic chance to be accepted for upstream > > Yes, so long as it comes with proper tests and is not too intrusive > on the overall design/implementation of CMake. > > In order to enable use of C# sources we should get > > enable_language(CSharp) > > to work. This is likely straightforward with the VS generators. > > One question is how things should be done for the Makefile and > Ninja generators. For these we need to construct command line > invocations of the compiler. I'm not very familiar with C#. > Does it need separate compilation with dependencies or should one > simply invoke the compiler with the entire list of sources in > a response file or something? > > the command line tool is 'mcs' (mono) http://linux.die.net/man/1/mcs and csc for .NET (windows) https://msdn.microsoft.com/en-us/library/78f4aasd.aspx (does support response file with @; from running csc /?) it goes from source to .dll or .exe without .obj inbetween. can compile with C# itself... but I guess there's no command line tool from .NET itself (looks like it comes from visual studio)... something like Power Shell can instance a compiler and build output. (wonder if that was part of the sources includes in the .net source release) Thanks, > -Brad > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/cmake-developers > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] C# support?
The C# compiler, csc.exe, takes all its arguments at once in one call to build a library or executable. Listing all the sources, and its references (other libraries it depends on) all at once. You can do it as command line arguments, or as contents of a response file, or a combination or arguments plus response file. Conceptually, it's "just like Java." They do have separate project files for it with VS, though. The generators will need code to generate *.csproj files, rather than custom commands in a vcxproj file, to make it seem like it's really well-integrated with VS. Not sure if *.csproj files have evolved much over the last few releases of VS -- I'd expect the major challenge with this to be making sure CMake generates proper *.csproj files for however many versions of VS it would take to make it acceptable. D On Mon, Jun 29, 2015 at 1:05 PM, Brad King wrote: > On 06/26/2015 10:47 AM, Stuermer, Michael SP/HZA-ZSEP wrote: >> Does it have a realistic chance to be accepted for upstream > > Yes, so long as it comes with proper tests and is not too intrusive > on the overall design/implementation of CMake. > > In order to enable use of C# sources we should get > > enable_language(CSharp) > > to work. This is likely straightforward with the VS generators. > > One question is how things should be done for the Makefile and > Ninja generators. For these we need to construct command line > invocations of the compiler. I'm not very familiar with C#. > Does it need separate compilation with dependencies or should one > simply invoke the compiler with the entire list of sources in > a response file or something? > > Thanks, > -Brad > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/cmake-developers -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] C# support?
On 06/26/2015 10:47 AM, Stuermer, Michael SP/HZA-ZSEP wrote: > Does it have a realistic chance to be accepted for upstream Yes, so long as it comes with proper tests and is not too intrusive on the overall design/implementation of CMake. In order to enable use of C# sources we should get enable_language(CSharp) to work. This is likely straightforward with the VS generators. One question is how things should be done for the Makefile and Ninja generators. For these we need to construct command line invocations of the compiler. I'm not very familiar with C#. Does it need separate compilation with dependencies or should one simply invoke the compiler with the entire list of sources in a response file or something? Thanks, -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0015635]: CPACK_NSIS_MODIFY_PATH has no affect on PATH variable
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=15635 == Reported By:kdawgud Assigned To: == Project:CMake Issue ID: 15635 Category: (No Category) Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2015-06-29 09:18 EDT Last Modified: 2015-06-29 09:18 EDT == Summary:CPACK_NSIS_MODIFY_PATH has no affect on PATH variable Description: I have a 64-bit windows C++ project where I'm using the NSIS generator for CPack. The installer appears to work fine, except that the PATH variable is not changed at all even when specified by the user during install. The CPACK_NSIS_MODIFY_PATH variable is specified in the cpack config to support changing the path during install. It doesn't seem to matter if "all users" or "current user" is selected. Steps to Reproduce: 1) Use CMake 3.1 to generate MS Visual Studio solution file for 64-bit (VS 2010). 2) Build project, then build "package" withing visual studio 3) Run the NSIS .exe installer generated by cpack 4) Select "Add to the system PATH for all users" when prompted 5) When NSIS install is complete, observe that "echo %PATH%" does not reflect the installed path 6) Reboot and still observe http://www.cmake.org/Bug/view.php?id=5 holds true. == Issue History Date ModifiedUsername FieldChange == 2015-06-29 09:18 kdawgudNew Issue == -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0015634]: Support for pkgconfig --define-variable
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=15634 == Reported By:Heinrich Fink Assigned To: == Project:CMake Issue ID: 15634 Category: CMake Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2015-06-29 09:13 EDT Last Modified: 2015-06-29 09:13 EDT == Summary:Support for pkgconfig --define-variable Description: It is often necessary to re-define the prefix variable of pkgconfig scripts to adapt to different compilation environments. This is usually done via "pkg-config --define-variable=prefix=/my/dev/root/libs". Unfortunately this workflow is not support by CMake scripts that use pkgconfig. A simple option to define additional agurments for pkg-config when invoked would be helpful already. Manually redefining the pkg-config executable path, to already contain the additional argument, wouldn't work. == Issue History Date ModifiedUsername FieldChange == 2015-06-29 09:13 Heinrich Fink New Issue == -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [PATCH] Help: fix FindMatlab section headers
On 06/29/2015 07:43 AM, Tamás Kenéz wrote: > FindMatlab used dash for its internal headers. > This commit replaces caret-headers with double-quote-headers and replaces > dash-headers with caret-headers. Applied, thanks: FindMatlab: Fix documentation section header underline style http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6524ed5e > On top of release. Since this is a trivial documentation update I've scheduled it for merge to 'release' for 3.3. Thanks, -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] [PATCH] Help: fix FindMatlab section headers
Hi, FindMatlab used dash for its internal headers. This commit replaces caret-headers with double-quote-headers and replaces dash-headers with caret-headers. On top of release. Tamas 0001-Help-fix-FindMatlab-section-headers.patch Description: Binary data -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [ANNOUNCE] CMake 3.3.0-rc3 is now ready!
Hi, Robert! Dear CMake developers Hello! 26.06.2015, 21:36, "Robert Maynard" : > I am proud to announce the third CMake 3.3 release candidate. ... > CPack > - > > * The "cpack(1)" "IFW" generator and the "CPackIFW" module learned > to support Qt Framework Installer 2.0 tools. I will add that now CMake can not only create an installer for your project based on QtIFW 2.0, but your own. But you wouldn't believe it :-) suggest believe it! Debian 8: http://ifw.podsvirov.pro/cmake/v3.3/cmake-3.3.0-rc3-Linux-i686.run http://ifw.podsvirov.pro/cmake/v3.3/cmake-3.3.0-rc3-Linux-x86_64.run Windows7: http://ifw.podsvirov.pro/cmake/v3.3/cmake-3.3.0-rc3-win32-x86.exe http://ifw.podsvirov.pro/cmake/v3.3/cmake-3.3.0-rc3-win64-x64.exe This offline installer, but very easy to do online installer with the possibility of further update: Debian 8: http://ifw.podsvirov.pro/cmake/cmake-master-i386-online.run http://ifw.podsvirov.pro/cmake/cmake-master-amd64-online.run Windows 7: http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe I urge everyone to try. Want to hear the opinion of Robert about these installers. Maybe someday CMake will also be distributed through QtIFW. -- Regards, Konstantin Podsvirov -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
