[cmake-developers] [CMake 0015683]: Extend --trace to --coverage mode for detection of "dead" cmake code

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15683 == Reported By:j.kreuzberger Assigned To:

[cmake-developers] [PATCH] Add --no-install-deps to bootstrapping procedure

MSYS2 uses Pacman to manage package dependencies so without this patch, our mingw-w64-cmake-git package ends up bundling all the DLLs it depends on which causes conflicts with the packages those DLLs really belong to. Please review. -- Best regards, Ray Donnelly. 0001-configure-Add-no-install-

Re: [cmake-developers] Java support

Hi, For point 1. I completely forgot to test with VS generators… I will work on that ASAP. For point 2., The best approach is to install 32 and 64bit versions of Java SDK (Windows versions, not some cygwin or MSYS versions) and ensure JAVA_HOME is NOT set in the environment nor referenced in t

Re: [cmake-developers] Java support

Hi, Again, a new version for patch 4. I hope I didn’t miss anything this time. :) To handle VS generators, I am relying on generator-expressions supported by add_test function. Marc On 04/08/15 17:42, "Brad King" wrote: >On 08/04/2015 04:45 AM, CHEVRIER, Marc wrote: >> Attached is a new v

[cmake-developers] [CMake 0015684]: CMAKE_Fortran_COMPILER_VERSION becomes unset after second configuring

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15684 == Reported By:Raul Laasner Assigned To:

[cmake-developers] The naming convention SHARED and STATIC

Encourage best practices. For example, I want to export one and the same library in one package in debug and release configurations. What do you name CMake targets and how to name files? -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org

Re: [cmake-developers] The naming convention SHARED and STATIC

Addition: SHARED and STATIC too (mylibstatic and mylibshared?)16:39, 5 августа 2015 г., Konstantin Podsvirov :Encourage best practices. For example, I want to export one and the same library in one package in debug and release configurations. What do you name CMake targets and how to name files? -

[cmake-developers] [PATCH] Add --no-install-deps to bootstrapping procedure

I left some debug stuff in the last version. Here it is without that; apologies. MSYS2 uses Pacman to manage package dependencies so without this patch, our mingw-w64-cmake-git package ends up bundling all the DLLs it depends on which causes conflicts with the packages those DLLs really belong to.

[cmake-developers] Silencing warning about environment when using NMake / JOM

Hi, While using the NMake and JOM generators in CMake, I have come across this warning: To use the [NMake | 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 f

Re: [cmake-developers] Java support

On 08/05/2015 03:15 AM, CHEVRIER, Marc wrote: > For point 2., The best approach is to install 32 and 64bit > versions of Java SDK (Windows versions, not some cygwin or > MSYS versions) and ensure JAVA_HOME is NOT set in the > environment nor referenced in the PATH. In this case, CMake > FindJava.cm

Re: [cmake-developers] Silencing warning about environment when using NMake / JOM

On 08/05/2015 11:17 AM, James Johnston wrote: > To use the [NMake | 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. > >

[cmake-developers] [CMake 0015685]: When packaging cmake-gui Qt dlls are resolved from the PATH and not from the Qt installation directory used to build CMake

The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=15685 == Reported By:Mourad Assigned To: =

Re: [cmake-developers] [PATCH] Add --no-install-deps to bootstrapping procedure

On 08/05/2015 11:16 AM, Ray Donnelly wrote: > MSYS2 uses Pacman to manage package dependencies so without this > patch, our mingw-w64-cmake-git package ends up bundling all the DLLs > it depends on which causes conflicts with the packages those DLLs > really belong to. I don't think we should requ

Re: [cmake-developers] [PATCH] Add --no-install-deps to bootstrapping procedure

On Wed, Aug 5, 2015 at 6:34 PM, Brad King wrote: > On 08/05/2015 11:16 AM, Ray Donnelly wrote: >> MSYS2 uses Pacman to manage package dependencies so without this >> patch, our mingw-w64-cmake-git package ends up bundling all the DLLs >> it depends on which causes conflicts with the packages those

[cmake-developers] Supporting monolithic and efficient CMake + Ninja builds for LLVM developers

(resending now that I’ve subscribed to cmake-developers) Hello CMake-Developers, I’m a contributor to the LLVM project working on improving our CMake-based build process, and I had a request I wanted to discuss with your community. This is related to a feature request I filed (http://public.ki

[cmake-developers] [PATCH] nmake/jom: Only warn about bad VS environment if compiler not found

Hi, Attached is a patch that changes the warning of nmake/jom generators when VCVarsAll.bat hasn't been run: nmake and jom generators no longer warn about missing INCLUDE/LIB environment variables unless the C/CXX compiler cannot be found. This is useful if the user does not want to use

Re: [cmake-developers] Supporting monolithic and efficient CMake + Ninja builds for LLVM developers

Chris Bieneman wrote: > (resending now that I’ve subscribed to cmake-developers) > > Hello CMake-Developers, > > I’m a contributor to the LLVM project working on improving our CMake-based > build process, and I had a request I wanted to discuss with your > community. > > This is related to a fe