Re: [CMake] HP-UX ia64 (32bit) port

[Bill Hoffman]

Can you run a nightly dashboard for CMake on this HW?  It would be the 
only way these changes would continue to work into the future.


On 6/28/2019 6:24 PM, Earle Lowe wrote:

I have made an HP-UX port for CMAKE 3.15

It's not entirely optimal, because I took a small shortcut on fsevents
in libuv by using the "no events" source also used by cygwin. HP-UX
does have /dev/poll, so I think the AIX code could be used as a
template for a proper implementation.

It runs --version, but I haven't tried to use it to make itself again,
or any other tests.

HP-UX  B.11.31 ia64 using GCC 9.4.3

The binaries are 32-bit

I didn't do this quite correctly because I didn't fork master and I
don't have a PR prepared.

If the community wants though, I can make a proper merge request

I'll note, getting GCC 9.4.3 working on HP-UX is actually harder than
porting cmake. This version of GCC has a fairly robust implementation
of C++11

-Earle

--

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] After working for a well over a year my cmake has suddenly stopped working, CMake Gui now fails to configure any project with the error..

[Bill Hoffman via CMake]

It could also be this issue:

https://developercommunity.visualstudio.com/content/problem/399774/visual-studio-2019-preview-1-running-cmake-on-comm.html

Do  you have Visual Studio 2019 installed?



On 1/4/2019 1:46 PM, 2GooD Productions wrote:


Selecting Windows SDK version 10.0.17763.0 to target Windows 6.3.9600.

CMake Error at CMakeLists.txt:45 (project):
Failed to run MSBuild command:

C:/Program Files (x86)/Microsoft Visual
Studio/2017/Community/MSBuild/15.0/Bin/MSBuild.exe

to get the value of VCTargetsPath:

The system cannot find the file specified


Configuring incomplete, errors occurred! See also
"G:/dev/CPP/libraries/LibraryBuilds/GLEW_TEST/CMakeFiles/CMakeOutput.log".


When I try to use VS2017 to build, I get this error...

CMake Error at C:/Program Files (x86)/Microsoft Visual

Studio/2017/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.12/Modules/CMakeTestCCompiler.cmake:52
(message):

  The C compiler


    "C:/Program Files (x86)/Microsoft Visual
Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64/cl.exe"


  is not able to compile a simple test program.


  It fails with the following output:


    Change Dir:

C:/Users/2Good/CMakeBuilds/774fd661-ecad-c93e-a053-ab53694fc56d/build/x64-Debug
(default)/CMakeFiles/CMakeTmp

    Run Build Command:"C:/Program Files (x86)/Microsoft Visual

Studio/2017/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe"
"cmTC_5cf10"

    ninja: fatal: couldn't open nul



  CMake will not be able to correctly generate this
project.C:/Program Files (x86)/Microsoft Visual

Studio/2017/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.12/Modules/CMakeTestCCompiler.cmake52

Yes, Im a noob, but I could really use some help, Ive been trying to 
fix this for over a week. Ive reinstalled CMake, VS2017, and MSBuild, 
added to the environment path variable the path to the compiler, but 
nothing Ive done has worked. Ive ran VS2017 as admin, Ive ran Cmake as 
admin. Can somebody please help this noob out?


-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] After working for a well over a year my cmake has suddenly stopped working, CMake Gui now fails to configure any project with the error..

[Bill Hoffman via CMake]

In the build trees, is there any more information in 
CMakeFiles/CMakeOutput.log or CMakeFiles/CMakeError.log?


Is your VS able to build things without CMake?

-Bill


On 1/4/2019 1:46 PM, 2GooD Productions wrote:


Selecting Windows SDK version 10.0.17763.0 to target Windows 6.3.9600.

CMake Error at CMakeLists.txt:45 (project):
Failed to run MSBuild command:

C:/Program Files (x86)/Microsoft Visual
Studio/2017/Community/MSBuild/15.0/Bin/MSBuild.exe

to get the value of VCTargetsPath:

The system cannot find the file specified


Configuring incomplete, errors occurred! See also
"G:/dev/CPP/libraries/LibraryBuilds/GLEW_TEST/CMakeFiles/CMakeOutput.log".


When I try to use VS2017 to build, I get this error...

CMake Error at C:/Program Files (x86)/Microsoft Visual

Studio/2017/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.12/Modules/CMakeTestCCompiler.cmake:52
(message):

  The C compiler


    "C:/Program Files (x86)/Microsoft Visual
Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64/cl.exe"


  is not able to compile a simple test program.


  It fails with the following output:


    Change Dir:

C:/Users/2Good/CMakeBuilds/774fd661-ecad-c93e-a053-ab53694fc56d/build/x64-Debug
(default)/CMakeFiles/CMakeTmp

    Run Build Command:"C:/Program Files (x86)/Microsoft Visual

Studio/2017/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe"
"cmTC_5cf10"

    ninja: fatal: couldn't open nul



  CMake will not be able to correctly generate this
project.C:/Program Files (x86)/Microsoft Visual

Studio/2017/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.12/Modules/CMakeTestCCompiler.cmake52

Yes, Im a noob, but I could really use some help, Ive been trying to 
fix this for over a week. Ive reinstalled CMake, VS2017, and MSBuild, 
added to the environment path variable the path to the compiler, but 
nothing Ive done has worked. Ive ran VS2017 as admin, Ive ran Cmake as 
admin. Can somebody please help this noob out?


-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Can CXX_CLANG_TIDY use .clang-tidy file?

[Bill Hoffman via CMake]

On 12/8/2018 7:47 PM, Mateusz Loskot wrote:

Hi,

Am I correct clang-tidy run via CXX_CLANG_TIDY
ignores .clang-tidy configuration file?

I've tried number of ways to help it find the file,
i.e. copied the file to binary directories from where it seems run via
usr/local/bin/cmake -E __run_co_compile --tidy=/usr/bin/clang-tidy-7


I don't think anything was done to turn that off on purpose.  Can you 
run the command from the command line and get it to work?  If so, you 
should be able to get the same arguments to the clang tidy that CMake is 
running.


-Bill

--

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Problem with using CMake on Windows with Visual Studio 2017

[Bill Hoffman]

Yes, if you could run "set" from the command prompt and post the output 
here.


|C:\Jinja2Cpp\build>set|


That might show if you have something odd in your environment.  I am 
guessing you have LDFLAGS  set which CMake picks up and uses as a linker 
flag.


On 10/26/2018 1:16 PM, Michael Ellery wrote:

look at the error message specifically:LDFLAGS=-static-libstdc++ 
-static-libgcc

Did you add something to your environment recently? Those look like gcc/clang 
flags - msvc is not going to like them.  Also, have you wiped your CMakeCache 
completely (clean configure)?  I’d have a look at your env variables to start 
with. Not generally needed, but you should also try building in a visual studio 
command prompt as it might properly set some of these ENV vars, just in case 
there is any confusion.

-Mike


-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Happy Birthday CMake!

[Bill Hoffman]

On 9/2/2018 6:54 PM, Alan W. Irwin wrote:


And thanks to you for coming up with such a useful tool in the first 
place!


Can you recommend a site that gives a (fairly) short history of CMake
that at least lists the most fundamental changes made to this software
since its inception?  For example, I am pretty sure you have stated 
before that it

did not start out as a C++ project.  If so, when did it switch to C++?
I did look at , but the history
paragraph there includes nothing about the fundamental changes made along
the way in the development of CMake.
CMake has always been in C++.   The idea was that all that would be 
required would be a C++ compiler.  With that, you could build CMake.  
Since CMake was designed to build C++ projects, it was assumed that the 
user would at least have a C++ compiler.


Should be some history these talks:
https://www.youtube.com/watch?v=8Ut9o4OdSC0=youtube_gdata
https://www.youtube.com/watch?v=TqjtN8NGtl4

I don't think there is anything written.

-Bill

-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [cmake-developers] [CMake] Happy Birthday CMake!

[Bill Hoffman]

On 9/2/2018 6:54 PM, Alan W. Irwin wrote:


And thanks to you for coming up with such a useful tool in the first 
place!


Can you recommend a site that gives a (fairly) short history of CMake
that at least lists the most fundamental changes made to this software
since its inception?  For example, I am pretty sure you have stated 
before that it

did not start out as a C++ project.  If so, when did it switch to C++?
I did look at , but the history
paragraph there includes nothing about the fundamental changes made along
the way in the development of CMake.
CMake has always been in C++.   The idea was that all that would be 
required would be a C++ compiler.  With that, you could build CMake.  
Since CMake was designed to build C++ projects, it was assumed that the 
user would at least have a C++ compiler.


Should be some history these talks:
https://www.youtube.com/watch?v=8Ut9o4OdSC0=youtube_gdata
https://www.youtube.com/watch?v=TqjtN8NGtl4

I don't think there is anything written.

-Bill

-- 

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:
https://cmake.org/mailman/listinfo/cmake-developers

[CMake] Happy Birthday CMake!

[Bill Hoffman]

http://public.kitware.com/pipermail/insight-developers/2000-August/024248.html

Thanks to everyone that has contributed or used CMake!

-Bill


-- 

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:
https://cmake.org/mailman/listinfo/cmake

[cmake-developers] Happy Birthday CMake!

[Bill Hoffman]

http://public.kitware.com/pipermail/insight-developers/2000-August/024248.html

Thanks to everyone that has contributed or used CMake!

-Bill


-- 

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:
https://cmake.org/mailman/listinfo/cmake-developers

Re: [CMake] find_library doesn't find .dll on windows

[Bill Hoffman]

On 6/1/2018 6:30 PM, Romain LEGUAY wrote:

Thank you for your answer.

I just want to find the file libmysql.dll because it's needed to be 
used with Qt (unless I did not understand how to use Qt's MySQL driver).
For now, I just do a simple copy of this file in my build folder, but 
it's not a good method.


So, for Windows runtime you have to have the dll in the same directory 
as the exe or in the PATH.  There is no concept of rpath built into an exe.


-Bill


--

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] cpp macro

[Bill Hoffman]

With the makefile generator you can do make foo.cxx.i.  Sadly this 
feature never made it into ninja.  If you run make help it shows the 
targets available.  With VS IDE you can right click on a file and get it 
to preprocess the file.


-Bill

--

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:
https://cmake.org/mailman/listinfo/cmake

Re: [cmake-developers] Using CMake to build big projects with cross-dependencies

[Bill Hoffman]

On 5/17/2018 11:46 AM, Brad King wrote:

On 05/17/2018 05:56 AM, Kinga Kasa wrote:

cmake running for hours and hours (stuck at saying Configuring done,
eventually it will finish, but it runs for hours).

That's not expected.  Even on projects with tens of thousands of
source files and thousands of libraries and executables it typically
takes only a few minutes.  You could try breaking in the debugger
locally during generation to see what it's doing.  Or, you could
try bisecting your project's content to get a smaller example that
reproduces the long generation time.
Another quick way to see what is going on is to run cmake with the 
--trace option:

cmake . --trace

It will produce a lot of output but you should be able to see if it is 
repeating something or getting stuck on some operation.


-Bill

--

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:
https://cmake.org/mailman/listinfo/cmake-developers

Re: [CMake] rebuild_cache does not fully rebuild the cache information

[Bill Hoffman]

On 5/9/2018 4:42 AM, Nils Rathmann wrote:

Hi,
when I change the installation of external dependencies, which are 
located by find_packages, it seems, that it is not enough to run 
rebuild_cache. The information about external software is not thrown 
away and rebuild. I have to delete the CMakeCache.txt and rebuild again.

It this intended? And why is it intended?

I work with cmake 3.9.1.
rebuild_cache basically just re-runs cmake on the project. It does not 
re-check find_package information.


-Bill

--

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] using ExternalProject_Add when cmake is launched

[Bill Hoffman]

On 5/2/2018 4:47 AM, Petr Kmoch wrote:

Hi Stephane.

ExternalProject is designed to run at *build* time, not at *CMake* 
time. It is not really intended for mixing with normal, 
non-ExternalProject targets (such as those created by add_library).


When using ExternalProject, the canonical form of operation is a 
SuperBuild-style project: your master CMakeLists.txt will contain only 
ExternalProject_Add() calls, *including one for your normal project.* 
Your normal project becomes just another project managed by the 
SuperBuild. The SuperBuild's purpose is to download, configure, build, 
etc., all the subprojects. So you generate the SuperBuild and then 
build it once to get all the dependencies in place. The you switch to 
using just the YourProject "child" of the SuperBuild and do normal 
development there.


I think googling "CMake ExternalProject_Add superbuild" will give you 
enough details to get you going.


Another option can be found in the most recent CMake 3.11:

https://cmake.org/cmake/help/git-stage/module/FetchContent.html

That should do what you want. It can not build or configure like 
external project, but it can download at cmake time.


-Bill




--

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Generating MSVS solution files that can be passed around

[Bill Hoffman]

One thing to consider is that MS is now shipping CMake as part of VS.  
So, if you can get your project to work with that version of VS, you 
should be all set. In fact you can have people just open the project and 
MS VS will run CMake for you.


-Bill

--

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] CTest extra tests

[Bill Hoffman]

Must be coming from some macro, cmake does not automatically add any
tests.  You could run cmake --trace and look at the output and find out
where the add_test call is coming from.

On Sun, Mar 18, 2018 at 5:39 PM, Adam Getchell 
wrote:

> Hello all,
>
> I’m running into unexpected behavior when using CTest.
>
> First, I define the list of tests that I want to run in my CMakeLists.txt:
>
> https://github.com/acgetchell/CDT-plusplus/blob/develop/
> CMakeLists.txt#L151
>
> However, it generates two extra tests:
>
> ┌─[*adam*][hapkido][*±*][develop {1} *✓*][~/CDT-plusplus/build]
> └─▪ ctest -N
> Test project /Users/adam/CDT-plusplus/build
>   Test  #1: cdt-gv
>   Test  #2: build_target_cdt-gv
>   Test  #3: CDT-Usage
>   Test  #4: CDT-3Donly
>   Test  #5: CDT-Simplices
>   Test  #6: CDT-Timeslices
>   Test  #7: CDT-3Dtriangle
>   Test  #8: CDT-MinimalS3
>   Test  #9: CDT-S3Runs
>   Test #10: CDT-unit-tests
>
> Total Tests: 10
>
> I’d like to get rid of these first two autogenerated tests, because #1
> fails. Where/how are these being generated/defined?
>
> I’m aware that I can just filter using ctest -E, but I’d like to make it
> easy for the other contributors (and my CI) by making `ctest` just work.
>
> Thanks for any pointers.
>
> Cheers,
> Adam
> --
> Adam Getchell
> https://keybase.io/adamgetchell
>
>
> --
>
> 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:
> https://cmake.org/mailman/listinfo/cmake
>
>
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug on Windows with Intel Fortran

[Bill Hoffman]

On 2/23/2018 10:59 AM, Anthony Zukaitis wrote:
On windows I found an issue with Visual studio where intel fortran was 
attempting to preprocess lowercase .f90 files.  Intel's documentation 
states that it does not preprocess these files.  Looking into the cmake 
source code I found:


in Modules/Platform/Windows-Intel-Fortran line 3:

set(_COMPILE_Fortran " /fpp")


which looks to me like cmake is adding this flag by default to all 
fortran files not .F90 vs .f90.  Also we are using our own preprocessor 
which would also complicate things.  Can you guys remove the setting of 
this flag?


Tony




Please add the issue here:
https://gitlab.kitware.com/cmake/cmake/issues
--

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:
https://cmake.org/mailman/listinfo/cmake

[CMake] Free CMake course at Kitware Headquarters March 13-15, 2018 at Kitware's Clifton Park, NY, USA

[Bill Hoffman]

Kitware is offering a free course on VTK/ParaView/CMake March 13-15, 
2018 at Kitware's Clifton Park, NY, USA.  The signup can be found here:


https://docs.google.com/forms/d/e/1FAIpQLSeee7oTBzapITmark0dIX0E86zEyyPmh-LEbecz2zm_822WFw/viewform

Hope to meet some of you in person.

-Bill
--

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:
https://cmake.org/mailman/listinfo/cmake

[cmake-developers] Free CMake course at Kitware Headquarters March 13-15, 2018 at Kitware's Clifton Park, NY, USA

[Bill Hoffman]

Kitware is offering a free course on VTK/ParaView/CMake March 13-15, 
2018 at Kitware's Clifton Park, NY, USA.  The signup can be found here:


https://docs.google.com/forms/d/e/1FAIpQLSeee7oTBzapITmark0dIX0E86zEyyPmh-LEbecz2zm_822WFw/viewform

Hope to meet some of you in person.

-Bill
--

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:
https://cmake.org/mailman/listinfo/cmake-developers

Re: [CMake] FortranCInterface not working with 3.9.0 with Intel 2015

[Bill Hoffman]

Thanks for sending the files.  I think I might have found something. 
The FortranCInterface.exe is not linking because of mismatched linker 
commands.  Here are the errors:


Did you change any of the default compiler/linker flags?  It looks like 
it is mixing run time libraries somehow.



[100%] Linking Fortran executable FortranCInterface.exe

LINK: command "xilink /nologo 
@CMakeFiles\FortranCInterface.dir\objects1.rsp 
/out:FortranCInterface.exe /implib:FortranCInterface.lib 
/pdb:C:\winsame\cary\usimall\builds\ulixes\ser\CMakeFiles\FortranCInterface\FortranCInterface.pdb 
/version:0.0 /machine:x64 /INCREMENTAL:NO /subsystem:console symbols.lib 
myfort.lib user32.lib /MANIFEST 
/MANIFESTFILE:FortranCInterface.exe.manifest" failed (exit code 1169) 
with the following output:

xilink: executing 'link'

LIBCMT.lib(winapisupp.obj) : error LNK2005: 
__crtSetUnhandledExceptionFilter already defined in MSVCRT.lib(MSVCR120.dll)


LIBCMT.lib(crtheap.obj) : error LNK2005: _calloc_crt already defined in 
MSVCRT.lib(MSVCR120.dll)


LIBCMT.lib(crt0dat.obj) : error LNK2005: _amsg_exit already defined in 
MSVCRT.lib(MSVCR120.dll)


LIBCMT.lib(crt0dat.obj) : error LNK2005: _cexit already defined in 
MSVCRT.lib(MSVCR120.dll)


LIBCMT.lib(crt0dat.obj) : error LNK2005: _exit already defined in 
MSVCRT.lib(MSVCR120.dll)


LIBCMT.lib(crt0dat.obj) : error LNK2005: _initterm_e already defined in 
MSVCRT.lib(MSVCR120.dll)


LIBCMT.lib(crt0dat.obj) : error LNK2005: exit already defined in 
MSVCRT.lib(MSVCR120.dll)


LIBCMT.lib(mlock.obj) : error LNK2005: _lock already defined in 
MSVCRT.lib(MSVCR120.dll)


LIBCMT.lib(mlock.obj) : error LNK2005: _unlock already defined in 
MSVCRT.lib(MSVCR120.dll)





--
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

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

Re: [CMake] FortranCInterface not working with 3.9.0 with Intel 2015

[Bill Hoffman]

Can you just send me a zip or tar file of the build tree from your project?

Thanks.

On 12/2/2017 4:17 AM, JR Cary wrote:



Does it work with 3.10?
  
It works with no version from  3.9.0 - 3.10.0.



Also, look in the CMakeFiles/CMakeError.log file to find out why this
happened: - Detecting Fortran/C Interface - Failed to compile.


Compiling the Fortran compiler identification source file 
"CMakeFortranCompilerId.F" failed.
Compiler: C:/Program Files (x86)/Intel/Composer XE 2015/bin/intel64/ifort.exe
Build flags:
Id flags: -v

The output was:
0
Intel(R) Visual Fortran Intel(R) 64 Compiler XE for applications running on 
Intel(R) 64, Version 15.0.6.285 Build 20151119
Copyright (C) 1985-2015 Intel Corporation.  All rights reserved.
ifort: command line warning #10006: ignoring unknown option '/v'

CMakeFortranCompilerId.F(2): warning #5117: Bad # preprocessor line
#if 0
...

Looks from 
https://stackoverflow.com/questions/36557120/usual-causes-for-bad-preprocessor-warning
that the preprocessor is not being run.  It requires -fpp to be added to the 
Fortran compiler
flags.  I do not see how to do that for CMakeFortranCompilerId.F.  Tried

   set(CMAKE_Fortran_FLAGS "${CMAKE_Fortran_FLAGS} -fpp")

but that did not help.



On 11/26/17 4:29 PM, JR Cary wrote:

Works with 3.8.2.

Compilers specified by

-DCMAKE_C_COMPILER:FILEPATH='C:/Program Files (x86)/Intel/Composer XE
2015/bin/intel64/icl.exe' -DCMAKE_CXX_COMPILER:FILEPATH='C:/Program
Files (x86)/Intel/Composer XE 2015/bin/intel64/icl.exe'
-DCMAKE_Fortran_COMPILER:FILEPATH='C:/Program Files (x86)/Intel/Composer
XE 2015/bin/intel64/ifort.exe'

The cmake code is

include(FortranCInterface)
FortranCInterface_HEADER(
   ${CMAKE_BINARY_DIR}/FCMangle.h
   MACRO_NAMESPACE "FC_"
   SYMBOL_NAMESPACE "FC_"
   SYMBOLS mysub mymod:my_sub
)

The relevant output is

-- Detecting Fortran/C Interface
-- Detecting Fortran/C Interface - Failed to compile
CMake Warning (dev) at
C:/winsame/cary/usim/contrib-icl15/cmake-3.9.0-ser/share/
cmake-3.9/Modules/FortranCInterface.cmake:309 (message):
   No FortranCInterface mangling known for mysub
Call Stack (most recent call first):
   scimake/SciFortranChecks.cmake:269 (FortranCInterface_HEADER)
   scimake/SciInit.cmake:232 (include)
   CMakeLists.txt:28 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at
C:/winsame/cary/usim/contrib-icl15/cmake-3.9.0-ser/share/
cmake-3.9/Modules/FortranCInterface.cmake:295 (message):
   No FortranCInterface mangling known for mymod:my_sub
Call Stack (most recent call first):
   scimake/SciFortranChecks.cmake:269 (FortranCInterface_HEADER)
   scimake/SciInit.cmake:232 (include)
   CMakeLists.txt:28 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

The resulting file is

$ cat FCMangle.h
#ifndef FC_HEADER_INCLUDED
#define FC_HEADER_INCLUDED

/*--*/
/* Mangle some symbols
automatically.   */

#endif

Any help appreciated..John Cary









--
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

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

Re: [CMake] FortranCInterface not working with 3.9.0 with Intel 2015

[Bill Hoffman]

On 11/26/2017 6:29 PM, JR Cary wrote:

Works with 3.8.2.


Does it work with 3.10?

Also, look in the CMakeFiles/CMakeError.log file to find out why this 
happened: - Detecting Fortran/C Interface - Failed to compile.


-Bill
--

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

Re: [cmake-developers] Make it easier for beginners

[Bill Hoffman]

On 10/21/2017 10:56 AM, Lectem wrote:

_Question :_ Would it possible to delete the wiki, or reset/reopen it ?

_Reason:_ The wiki is full of old stuff, but we can't register to edit 
stuff. Still, people willing to learn will end up visiting it, thinking 
it gives good advice. "How could it not ? It's the official wiki". At 
the very least I wish we could add a big red message stating it is 
outdated and not updated anymore.


The wiki is still open.  If people want to edit they have to send an 
email and let us know what they want to do.  It was too hard to keep the 
spam off of it otherwise.  So, send me an email off list and I can get 
you setup with a wiki account.


-Bill
--

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] Adding compile and build type tests to CMake/CTest

[Bill Hoffman]

On 9/12/2017 1:11 PM, Robert Ramey wrote:


Could we get some response on Edward's suggestion here? It's a serious 
obstacle to implementing support of CMake in Boost libraries.
I don't think it would be a problem to implement something like this in 
CMake.  It might make more sense to move this conversation to the 
cmake-developers list where we can discuss the particulars of the 
interface and implementation. Then we can figure out how to get it 
implemented.


Edward, did you want to start the discussion on the cmake-developers list?

Thanks.

-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

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

Re: [cmake-developers] C++ IDE

[Bill Hoffman]

On 8/18/2017 9:37 AM, Jean-Michaël Celerier wrote:


IMHO, Visual Studio's CMake integration is a joke in comparison to 
QtCreator and CLion.

Microsoft has been working to fix that.
https://blogs.msdn.microsoft.com/vcblog/2016/10/05/cmake-support-in-visual-studio/

MS is shipping a version of CMake with VS, and are using the 
cmake-server to talk to CMake.  They continue to improve this, so with 
new versions of VS, it should continue to get better.


-Bill
--

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] Future of ccmake and cmake-gui and internationalization

[Bill Hoffman]

On 8/17/2017 12:11 PM, Eric Wing wrote:

Oddly, I don't have any direct experience with FLTK even though I've
known about it for years. The projects I get involved with usually
need a lot more native UI integration, so FLTK is never on the list.
And I personally prefer native UI experience.  But for something small
like the CMake GUI, it wouldn't bother me as much. That said, it
sounds like this is not a rewrite, so I guess the conversation is
moot.
CMake originally had an FLTK GUI it was dropped for the Qt one.  :) 
This happened around the time Qt changed licenses.  I am not that 
interested in dropping Qt for something else at this point.  Computers 
have big disks/memory so the bloat does not bother me that much.  There 
are folks maintaining the Qt cmake-gui and there seems to be enough Qt 
knowledge around to keep that going.


-Bill
--

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] Kitware is hiring

[Bill Hoffman]

Kitware is currently looking for a software developer in our Clifton 
Park NY office.  We are looking for someone with C++ and CMake 
experience.  Here is the job posting:


https://www.smartrecruiters.com/kitware/743999656184083-software-developer

Thanks.

-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

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

Re: [CMake] Compiling Fortran on IBMs XL

[Bill Hoffman]

On 6/8/2017 5:13 AM, Matthias Redies wrote:


I believe my Error was discussed in:

http://public.kitware.com/pipermail/cmake/2015-January/059522.html

and solved here:

http://public.kitware.com/pipermail/cmake/2015-January/059547.html

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4729547a

However, I am working on a cluster where the only available version is:
cmake version 2.8.12.2
You should be able to build cmake from source or download a linux binary 
from here: https://cmake.org/download/.


It does not need to be installed as root, you can just untar and run 
cmake from any directory.  If I was in your  position I would set the 
minimum required version of cmake to one that handles your fortran 
compiler.  Then use the binary or build from source.


-Bill
--

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

Re: [CMake] Tracing ctest crash on windows

[Bill Hoffman]

On 1/5/2017 9:32 AM, Jakob van Bethlehem wrote:


CTest is not some magical tool that internally runs your test or
something like that - instead CTest just fires up your test executable
and does clever things with the output. In the same way you can just set
your test project as startup-project, and debug it like any other
executable.

Sincerely,
Jakob

On Wed, Jan 4, 2017 at 2:43 PM, Aaron Boxer > wrote:

Hello,
I am on windows, with visual studio 2015.
Some of my ctest tests are crashing with exception.
Is there a way of debugging these tests ?

When I run in debug mode, I get an exception dialog,
but can't drop into debugging environment.
If you run ctest -VV it will show the full command line.  Best way is to 
just run the same command in the debugger.


-Bill

--

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

Re: [CMake] What are the missing features in Ninja that CMake needs?

[Bill Hoffman]

On 12/18/2016 8:57 AM, David Cole via CMake wrote:

This "compare" view on GitHub shows the difference between the
regular/upstream ninja and the Kitware patched ninja:


https://github.com/ninja-build/ninja/compare/master...Kitware:features-for-fortran

The ReadMe explains the high-level view, and says it is gradually
being worked into upstream ninja.

It has to do with Fortran modules. These are sort of "include" files 
that are automatically generated by the Fortran compiler.  So, there is 
a specific order in which Fortran source files must be compiled so that 
files that include exist before they try to include them.


For some examples see this cmake test case:

https://gitlab.kitware.com/cmake/cmake/tree/master/Tests/FortranModules

It will not pass with upstream ninja.

-Bill

--

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

Re: [cmake-developers] Disabling leaks check when using Address Sanitizer

[Bill Hoffman]

On 12/16/2016 7:55 AM, Brad King wrote:

It looks like this was added in commit 44726714322ca0b75628e234229f4583a480d7ec
when support for asan was first added.  Bill, do you recall why?
I don't recall exactly.  I guess I figured if you were running asan you 
might as well check for leaks as well.  Maybe the right fix is to have 
user flags over ride anything CMake adds, but leave the default like it is.


-Bill

--

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] Ninja+Fortran support for PGI compiler

[Bill Hoffman]

On 12/16/2016 8:38 AM, Brad King wrote:

Great!  I'll integrate that for CMake 3.8.

Daniel, do you think you could setup a dashboard so this stays working?
https://cmake.org/testing/

-Bill

--

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

Re: [CMake] CXX_CLANG_TIDY doesn't handle multiple arguments correctly

[Bill Hoffman]

On 11/16/2016 5:01 PM, Nikita wrote:

It works for me with '-fix' as well. However, it doesn't work with
"-warnings-as-errors", '-header-filter', and '-line-filter'.
The problem is definitely not in semicolons.

It is the * that causes trouble.

-Bill

--

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

Re: [CMake] Relinking with Ninja broken in 3.7.0

[Bill Hoffman]

On 11/16/2016 11:36 AM, Mika Fischer wrote:


I get the following error even though I'm on Linux and thus an ELF-based
platform. This breaks all our builds...

`The install of the  target requires changing an RPATH from
the build tree, but this is not supported with the Ninja generator unless
on an ELF-based platform.  The CMAKE_BUILD_WITH_INSTALL_RPATH variable may
be set to avoid this relinking step.`

Looking at cmGeneratorTarget.cxx#L1214, I see that there's no switch for
ELF-based platforms, it just unconditionally throws a fatal error when
relinking is required and ninja is being used...

Is the error message misleading and this should actually work on Linux?
Or is this not supposed to be working, and we should no longer use
ninja? If so, why?

CMAKE_BUILD_WITH_INSTALL_RPATH is not a viable alternative for us...

Did you start with a completely clean build tree?  Or did you maybe just 
remove the CMakeCache.txt file?


-Bill

--

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

Re: [CMake] additional arguments with CMAKE_CXX_CLANG_TIDY variable

[Bill Hoffman]

On 11/8/2016 11:20 AM, Michael Ellery wrote:

/usr/local/Cellar/cmake/3.6.2/bin/cmake -E __run_iwyu
--tidy="/usr/local/opt/llvm38/bin/clang-tidy-3.8;-checks=*"
--source=/Users/ellery/work/.
That should still work.  It is passing that to -E __run_iwyu which 
should expand the arguments.


https://gitlab.kitware.com/cmake/cmake/blob/master/Source/cmcmd.cxx#L353
cmSystemTools::ExpandListArgument will separate out the arguments.  My 
guess is the * might be causing the trouble somehow.


-Bill


--

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

Re: [CMake] Single Letter Omissions From File Path In Linker

[Bill Hoffman]

Can you create a small example that shows the problem?  Even a small 
full example with the code you have below so I can better understand it.


-Bill


On 10/17/2016 10:59 AM, Randy Turner wrote:

Thanks, Andrew, Bill, and Zan! I'm not completely certain that
reinstalling Windows is the only or even the best solution, but once we
all moved our repositories into our root directories I have not found
another solution, even temporary. Of our six dev machines, it is a
recurring problem on two and has occurred once on a third. The other
three have never seen this problem.

I did some digging on Friday and found that the problem seems to be
connected to this call below to add all of our code files to a library
to be used an item in the add_executable() command for each of our targets.

foreach (code ${code_files})
get_filename_component (codeName ${code} NAME_WE)
add_library (${codeName} OBJECT
 ${code}
  )
  list(APPEND codelib $<TARGET_OBJECTS:${codeName}>)
endforeach()

If I remove that loop and add code_files instead of codelib to the
executables then the problem disappears, but this breaks most of the
functionality of my implementation of CMake, so this isn't a long-term
solution. Using the library call above I followed the file paths around
the script and printed them out at every step through the makefile
generation and never saw any incorrect paths, but then I called the
compiler and saw it error out.

The project uses "Unix Makefiles" to run on TI's gmake compiler 7.4.14.
I'm have been using CMake 3.5.2. I upgraded to 3.6.2 and continue to see
the same problem. I will move forward with looking into this library
issue but I'm sure what I expect to find.

On Fri, Oct 14, 2016 at 10:16 AM, Andrew Bell <andrew.bell...@gmail.com
<mailto:andrew.bell...@gmail.com>> wrote:

On Fri, Oct 14, 2016 at 9:04 AM, Randy Turner
<randallsturne...@gmail.com <mailto:randallsturne...@gmail.com>> wrote:

Hello! I've been running into a frustrating issue on and off for
the past year. The project will build the source files correctly
but when it comes to linking the executables, I always get the
same error. The specific file varies, but the failure mode is
always the same. For example:


"C:\\Users\\User\\AppData\\Local\\Temp\\",
line xxx: error #10008-D: cannot find file

"C:/Repos/operatingsystem/CMakeFiles/nvm_validate_ierator.dir/os/nvm/nvm_validate_iterator.c.obj"

As you can see, the file path is missing a "t" in the first
occurrence of the word "iterator" and so that file definitely
does not exist. A file exists in the location with correct
spelling, but somehow that hardcoded path in that temporary file
has dropped a letter. The specific letter that gets dropped
varies along with which file is allegedly missing. We noticed
that requiring people to store the repository in their root
directory greatly cut down on the occurrence of this issue but
it is returning with more frequency as of late. Once it occurs
once, CMake builds are never successful again and the only way
that I have been able to completely clear the problem has been
to reinstall Windows and set up the build environment again.


This seems really, really strange.  Have to reinstall Windows?  What
about just using another build directory?  It sure *seems* like
there's some problem in your CMakeFiles.txt where the way the
filepath is being constructed is incorrect.  But I don't think
you've really provided enough information to determine the problem.
Where does the name of the object file come from?

--
Andrew Bell
andrew.bell...@gmail.com <mailto:andrew.bell...@gmail.com>







--
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

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

Re: [CMake] Single Letter Omissions From File Path In Linker

[Bill Hoffman]

On 10/14/2016 10:04 AM, Randy Turner wrote:

Hello! I've been running into a frustrating issue on and off for the
past year. The project will build the source files correctly but when it
comes to linking the executables, I always get the same error. The
specific file varies, but the failure mode is always the same. For example:


"C:\\Users\\User\\AppData\\Local\\Temp\\", line
xxx: error #10008-D: cannot find file
"C:/Repos/operatingsystem/CMakeFiles/nvm_validate_ierator.dir/os/nvm/nvm_validate_iterator.c.obj"

As you can see, the file path is missing a "t" in the first occurrence
of the word "iterator" and so that file definitely does not exist. A
file exists in the location with correct spelling, but somehow that
hardcoded path in that temporary file has dropped a letter. The specific
letter that gets dropped varies along with which file is allegedly
missing. We noticed that requiring people to store the repository in
their root directory greatly cut down on the occurrence of this issue
but it is returning with more frequency as of late. Once it occurs once,
CMake builds are never successful again and the only way that I have
been able to completely clear the problem has been to reinstall Windows
and set up the build environment again.

Has anyone else seen this issue? Is there a way to change the directory
for those linker files so that they're not in the Temp folder?

What generator are you using?  What version of CMake?

-Bill

--

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

Re: [cmake-developers] Android Support

[Bill Hoffman]

On 9/26/2016 5:50 PM, David Neto via cmake-developers wrote:


I agree.  I work for Google but not in this area, and I don't know who
is doing this support.  I suspect this is just an accidental duplication
of effort.  I've pinged someone to see about finding the right person to
coordinate with.
Brad has been working with the team at Google.  He can elaborate more 
tomorrow.  Just wanted to let folks sleep easy tonight.  :)


-Bill

--

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] Windows Visual Studio 13 with Ninja & CMake

[Bill Hoffman]

On 9/22/2016 1:58 PM, Michael Jackson wrote:

My combination is Windows 10 (Anniversary Update), Visual Studio 12 2013
Update 5, Ninja and CMake 3.5/3.6.

I launch CMake-GUI.exe, select my Source and binary directories and then
"Configure", select "Ninja" as the generator and then I instantly get
the error that CMake can not find the C/C++ compilers. I do not recall
ever having this issue. I just recently updated Windows 10 to the latest
so I am not sure if that caused something to go wrong? I use the
"Zipped" version of CMake if that makes a difference. I did have to
install the "Windows 8.1 SDK" in order for QtCreator to work correctly.

I can successfully do the following:
* Configure and generate from the command line for Ninja
* Use the CMake-Gui to generate a VS 12 2013 solution file without any
issues.
* QtCreator 4.1 can use ninja to properly generate its own projects with
a correctly detected compiler.

Thoughts?
You have to run cmake-gui from an environment that has been setup to run 
the compiler.  VS command prompt.  If you run cmake-gui from a menu or 
clicking on an icon it won't have that and things won't work unless you 
use the VS generator which does not require a special environment.


-Bill

--

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1922-gf8fc47d

[Bill Hoffman]

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, next has been updated
   via  f8fc47db59a6cbd16a4fdd3238e82f8a5561631f (commit)
   via  e42471b9d4e4e99f38200a87121f46a7991510cd (commit)
   via  9e8dc649129b8ec711d6fb854d4f9576c0dd4dc9 (commit)
   via  7d2e9dd88c154707c7434c27edb34de948a51d60 (commit)
  from  e0aa392d59fed43a0de907fc31518adc8ca1d74e (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 -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f8fc47db59a6cbd16a4fdd3238e82f8a5561631f
commit f8fc47db59a6cbd16a4fdd3238e82f8a5561631f
Merge: e0aa392 e42471b
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Fri Sep 9 16:53:44 2016 -0400
Commit: CMake Topic Stage <kwro...@kitware.com>
CommitDate: Fri Sep 9 16:53:44 2016 -0400

Merge topic 'extend_matlab_unit_test' into next

e42471b9 remove stray }
9e8dc649 use single value args
7d2e9dd8 Extend matlab_add_unit_test to run arbitrary code for the test.


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e42471b9d4e4e99f38200a87121f46a7991510cd
commit e42471b9d4e4e99f38200a87121f46a7991510cd
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Fri Sep 9 16:33:36 2016 -0400
Commit: Bill Hoffman <bill.hoff...@kitware.com>
CommitDate: Fri Sep 9 16:33:36 2016 -0400

remove stray }

diff --git a/Modules/FindMatlab.cmake b/Modules/FindMatlab.cmake
index fd222fd..0462bd0 100644
--- a/Modules/FindMatlab.cmake
+++ b/Modules/FindMatlab.cmake
@@ -788,7 +788,7 @@ function(matlab_add_unit_test)
   add_test(NAME ${${prefix}_NAME}
COMMAND ${CMAKE_COMMAND}
 "-Dtest_name=${${prefix}_NAME}"
-"-Dadditional_paths=${${prefix}_ADDITIONAL_PATH}}"
+"-Dadditional_paths=${${prefix}_ADDITIONAL_PATH}"
 "-Dtest_timeout=${${prefix}_TIMEOUT}"
 "-Doutput_directory=${_matlab_temporary_folder}"
 "-Dworking_directory=${${prefix}_WORKING_DIRECTORY}"
@@ -796,7 +796,7 @@ function(matlab_add_unit_test)
 "-Dno_unittest_framework=${${prefix}_NO_UNITTEST_FRAMEWORK}"
 
"-DMatlab_ADDITIONNAL_STARTUP_OPTIONS=${${prefix}_MATLAB_ADDITIONAL_STARTUP_OPTIONS}"
 "-Dunittest_file_to_run=${${prefix}_UNITTEST_FILE}"
-"-Dcustom_Matlab_test_command=${${prefix}_CUSTOM_TEST_COMMAND}}"
+"-Dcustom_Matlab_test_command=${${prefix}_CUSTOM_TEST_COMMAND}"
 "-Dcmd_to_run_before_test=${${prefix}_UNITTEST_PRECOMMAND}"
 -P ${_FindMatlab_SELF_DIR}/MatlabTestsRedirect.cmake
${${prefix}_TEST_ARGS}

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9e8dc649129b8ec711d6fb854d4f9576c0dd4dc9
commit 9e8dc649129b8ec711d6fb854d4f9576c0dd4dc9
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Fri Sep 9 14:44:48 2016 -0400
Commit: Bill Hoffman <bill.hoff...@kitware.com>
CommitDate: Fri Sep 9 14:44:48 2016 -0400

use single value args

diff --git a/Modules/FindMatlab.cmake b/Modules/FindMatlab.cmake
index 7c03635..fd222fd 100644
--- a/Modules/FindMatlab.cmake
+++ b/Modules/FindMatlab.cmake
@@ -773,9 +773,10 @@ function(matlab_add_unit_test)
   endif()
 
   set(options NO_UNITTEST_FRAMEWORK)
-  set(oneValueArgs NAME UNITTEST_FILE TIMEOUT WORKING_DIRECTORY)
-  set(multiValueArgs UNITTEST_PRECOMMAND ADDITIONAL_PATH
-MATLAB_ADDITIONAL_STARTUP_OPTIONS TEST_ARGS CUSTOM_TEST_COMMAND)
+  set(oneValueArgs NAME UNITTEST_FILE TIMEOUT WORKING_DIRECTORY
+UNITTEST_PRECOMMAND CUSTOM_TEST_COMMAND)
+  set(multiValueArgs ADDITIONAL_PATH MATLAB_ADDITIONAL_STARTUP_OPTIONS
+TEST_ARGS)
 
   set(prefix _matlab_unittest_prefix)
   cmake_parse_arguments(PARSE_ARGV 0 ${prefix} "${options}" "${oneValueArgs}" 
"${multiValueArgs}" )

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7d2e9dd88c154707c7434c27edb34de948a51d60
commit 7d2e9dd88c154707c7434c27edb34de948a51d60
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Tue Aug 30 15:02:35 2016 -0400
Commit: Bill Hoffman <bill.hoff...@kitware.com>
CommitDate: Fri Sep 9 14:41:53 2016 -0400

Extend matlab_add_unit_test to run arbitrary code for the test.

This commit allows a custom matlab set of commands to be run
as the test instead of runtests('matlab_file_name'). It also
escapes strings for matlab commands to allow for complicated
matlab commands to be passed into the tests.

diff --git a/Modules/FindMatlab.cmake b/Modules/FindMatlab.cmake
index b501599..7c03635 1006

[Cmake-commits] CMake branch, next, updated. v3.6.1-1700-ge623fc9

[Bill Hoffman]

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, next has been updated
   via  e623fc98ca6bfeb4f4fda75b21542aefbcefd78b (commit)
   via  48b32fae344ca8bab5f0b93b0570e4d8b7ef1eca (commit)
  from  1ec2259fe60a0d147bd85ce171120a5bdafa6fbe (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 -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e623fc98ca6bfeb4f4fda75b21542aefbcefd78b
commit e623fc98ca6bfeb4f4fda75b21542aefbcefd78b
Merge: 1ec2259 48b32fa
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Thu Sep 1 16:34:37 2016 -0400
Commit: CMake Topic Stage <kwro...@kitware.com>
CommitDate: Thu Sep 1 16:34:37 2016 -0400

Merge topic 'extend_matlab_unit_test' into next

48b32fae remove extra }}


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=48b32fae344ca8bab5f0b93b0570e4d8b7ef1eca
commit 48b32fae344ca8bab5f0b93b0570e4d8b7ef1eca
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Thu Sep 1 16:33:22 2016 -0400
Commit: Bill Hoffman <bill.hoff...@kitware.com>
CommitDate: Thu Sep 1 16:33:22 2016 -0400

remove extra }}

diff --git a/Modules/FindMatlab.cmake b/Modules/FindMatlab.cmake
index 4c787d7..a2289d5 100644
--- a/Modules/FindMatlab.cmake
+++ b/Modules/FindMatlab.cmake
@@ -795,7 +795,7 @@ function(matlab_add_unit_test)
 "-Dno_unittest_framework=${${prefix}_NO_UNITTEST_FRAMEWORK}"
 
"-DMatlab_ADDITIONNAL_STARTUP_OPTIONS=${${prefix}_MATLAB_ADDITIONAL_STARTUP_OPTIONS}"
 "-Dunittest_file_to_run=${${prefix}_UNITTEST_FILE}"
-"-Dcustom_Matlab_test_command=${${prefix}_CUSTOM_TEST_COMMAND}}"
+"-Dcustom_Matlab_test_command=${${prefix}_CUSTOM_TEST_COMMAND}"
 "-Dcmd_to_run_before_test=${${prefix}_UNITTEST_PRECOMMAND}"
 -P ${_FindMatlab_SELF_DIR}/MatlabTestsRedirect.cmake
${${prefix}_TEST_ARGS}

---

Summary of changes:
 Modules/FindMatlab.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, next, updated. v3.6.1-1663-g908cfab

[Bill Hoffman]

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, next has been updated
   via  908cfab96a7cb0edbde586e6b31d28f36623577f (commit)
   via  ca0497c945460a10d2bb273be1f39e35c9c88742 (commit)
  from  c01d364e2bd3ce04cc251e44aa21022204d69176 (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 -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=908cfab96a7cb0edbde586e6b31d28f36623577f
commit 908cfab96a7cb0edbde586e6b31d28f36623577f
Merge: c01d364 ca0497c
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Wed Aug 31 11:24:16 2016 -0400
Commit: CMake Topic Stage <kwro...@kitware.com>
CommitDate: Wed Aug 31 11:24:16 2016 -0400

Merge topic 'extend_matlab_unit_test' into next

ca0497c9 Extend matlab_add_unit_test to run arbitrary code for the test.


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ca0497c945460a10d2bb273be1f39e35c9c88742
commit ca0497c945460a10d2bb273be1f39e35c9c88742
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Tue Aug 30 15:02:35 2016 -0400
Commit: Bill Hoffman <bill.hoff...@kitware.com>
CommitDate: Wed Aug 31 10:42:13 2016 -0400

Extend matlab_add_unit_test to run arbitrary code for the test.

This commit allows a custom matlab set of commands to be run
as the test instead of runtests('matlab_file_name'). It also
escapes strings for matlab commands to allow for complicated
matlab commands to be passed into the tests.

diff --git a/Modules/FindMatlab.cmake b/Modules/FindMatlab.cmake
index 9f96fe6..aaca953 100644
--- a/Modules/FindMatlab.cmake
+++ b/Modules/FindMatlab.cmake
@@ -635,7 +635,7 @@ function(matlab_get_version_from_matlab_run 
matlab_binary_program matlab_list_ve
 set(devnull INPUT_FILE NUL)
   endif()
 
-  # timeout set to 30 seconds, in case it does not start
+  # timeout set to 120 seconds, in case it does not start
   # note as said before OUTPUT_VARIABLE cannot be used in a platform
   # independent manner however, not setting it would flush the output of Matlab
   # in the current console (unix variant)
@@ -644,12 +644,17 @@ function(matlab_get_version_from_matlab_run 
matlab_binary_program matlab_list_ve
 OUTPUT_VARIABLE _matlab_version_from_cmd_dummy
 RESULT_VARIABLE _matlab_result_version_call
 ERROR_VARIABLE _matlab_result_version_call_error
-TIMEOUT 30
+TIMEOUT 120
 WORKING_DIRECTORY "${_matlab_temporary_folder}"
 ${devnull}
 )
-
-
+  if("${_matlab_result_version_call}" MATCHES "timeout")
+if(MATLAB_FIND_DEBUG)
+  message(WARNING "[MATLAB] Unable to determine the version of Matlab."
+" Matlab call timed out after 120 seconds.")
+endif()
+return()
+  endif()
   if(${_matlab_result_version_call})
 if(MATLAB_FIND_DEBUG)
   message(WARNING "[MATLAB] Unable to determine the version of Matlab. 
Matlab call returned with error ${_matlab_result_version_call}.")
@@ -698,7 +703,6 @@ function(matlab_get_version_from_matlab_run 
matlab_binary_program matlab_list_ve
 
 endfunction()
 
-
 #.rst:
 # .. command:: matlab_add_unit_test
 #
@@ -720,6 +724,7 @@ endfunction()
 # matlab_add_unit_test(
 # NAME 
 # UNITTEST_FILE matlab_file_containing_unittest.m
+# [CUSTOM_MATLAB_COMMAND matlab_command_to_run_as_test]
 # [UNITTEST_PRECOMMAND matlab_command_to_run]
 # [TIMEOUT timeout]
 # [ADDITIONAL_PATH path1 [path2 ...]]
@@ -735,6 +740,11 @@ endfunction()
 #   ``UNITTEST_FILE``
 # the matlab unittest file. Its path will be automatically
 # added to the Matlab path.
+#   ``CUSTOM_MATLAB_COMMAND``
+# Matlab script command to run as the test.
+# IIf this is not set, then the following is run:
+# "runtests('matlab_file_name'), exit(max([ans(1,:).Failed]))
+# matlab_file_name comes from UNITTEST_FILE without the .m.
 #   ``UNITTEST_PRECOMMAND``
 # Matlab script command to be ran before the file
 # containing the test (eg. GPU device initialisation based on CMake
@@ -748,6 +758,7 @@ endfunction()
 #   ``MATLAB_ADDITIONAL_STARTUP_OPTIONS``
 # a list of additional option in order
 # to run Matlab from the command line.
+# -nosplash -nodesktop -nodisplay are always added.
 #   ``TEST_ARGS``
 # Additional options provided to the add_test command. These
 # options are added to the default options (eg. "CONFIGURATIONS Release")
@@ -762,8 +773,9 @@ function(matlab_add_unit_test)
   endif()
 
   set(options NO_UNITTEST_FRAMEWORK)
-  set(oneValueArgs NAME UNITTEST_PRECOMMAND UNITTEST_FILE TIMEOUT)
-  set(multiValueArgs ADDITIONAL_PATH M

Re: [CMake] Using clang-tidy with cmake 3.6.0

[Bill Hoffman]

On 7/20/2016 4:02 PM, Robert Maynard wrote:

I believe the correct form is:

set_target_properties(example PROPERTIES CXX_CLANG_TIDY
"${path_to_tidy} -some -args")

No, that won't work.

You want it to be a semi-colon separated list of arguments.  Not space 
separated.


https://cmake.org/cmake/help/v3.6/prop_tgt/LANG_CLANG_TIDY.html#prop_tgt:_CLANG_TIDY


In a ctest script it would be done something like this:

set(DASHBOARD_CLANG_TIDAY
"/path/to/clang-tidy" "-arg1" "-arg2")


Then put this in the cache:
"CMAKE_CXX_CLANG_TIDY:STRING=${DASHBOARD_CLANG_TIDY}"

-Bill
--

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

Re: [CMake] best way to handle subdirectory libraries ?

[Bill Hoffman]

On 7/12/2016 2:11 PM, Dan Ibanez wrote:


Other projects have a whole system atop CMake that manages this.
I'm trying to get a sense of what the "best" setup looks like using pure
CMake.


See  Usage Requirements:

https://cmake.org/cmake/help/v3.0/manual/cmake-buildsystem.7.html#id10
https://cmake.org/cmake/help/v3.0/prop_tgt/INTERFACE_INCLUDE_DIRECTORIES.html

-Bill

--

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

Re: [CMake] CTest periodic freeze under MacOS

[Bill Hoffman]

On 6/27/2016 5:57 AM, ycollette.nos...@free.fr wrote:

I forgot to say that the cmake version installed on macos is 3.4.3.

Can you try a more recent version of cmake?

-Bill
--

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-350-gc3e9f73

[Bill Hoffman]

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, next has been updated
   via  c3e9f7396581ff316be231fdd85bb0dfd2503596 (commit)
   via  d0adee7c496d08e8702a378ab841989568cd0f27 (commit)
  from  6ba4954cb9787ea034f3f8d56003aad8130e4465 (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 -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c3e9f7396581ff316be231fdd85bb0dfd2503596
commit c3e9f7396581ff316be231fdd85bb0dfd2503596
Merge: 6ba4954 d0adee7
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Thu Jun 16 14:13:24 2016 -0400
Commit: CMake Topic Stage <kwro...@kitware.com>
CommitDate: Thu Jun 16 14:13:24 2016 -0400

Merge topic 'link_what_you_use' into next

d0adee7c Add support for ldd -u -r as link what you use tool.

diff --cc Source/cmMakefileExecutableTargetGenerator.cxx
index f2c7bc8,9c34125..ca0fdcb
--- a/Source/cmMakefileExecutableTargetGenerator.cxx
+++ b/Source/cmMakefileExecutableTargetGenerator.cxx
@@@ -187,10 -187,13 +187,14 @@@ void cmMakefileExecutableTargetGenerato
  this->LocalGenerator->AppendFlags(
linkFlags, this->Makefile->GetDefinition(export_flag_var));
}
+   if(this->GeneratorTarget->GetProperty("LINK_WHAT_YOU_USE")) {
+ this->LocalGenerator->AppendFlags(linkFlags,
+   " -Wl,--no-as-needed");
+   }
  
// Add language feature flags.
 -  this->AddFeatureFlags(flags, linkLanguage);
 +  this->LocalGenerator->AddFeatureFlags(flags, linkLanguage,
 +this->GeneratorTarget);
  
this->LocalGenerator->AddArchitectureFlags(flags, this->GeneratorTarget,
   linkLanguage, this->ConfigName);

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d0adee7c496d08e8702a378ab841989568cd0f27
commit d0adee7c496d08e8702a378ab841989568cd0f27
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Thu Jun 2 18:08:30 2016 -0400
Commit: Bill Hoffman <bill.hoff...@kitware.com>
CommitDate: Thu Jun 16 14:12:20 2016 -0400

Add support for ldd -u -r as link what you use tool.

diff --git a/Help/manual/cmake-properties.7.rst 
b/Help/manual/cmake-properties.7.rst
index 3403dcd..6a7560a 100644
--- a/Help/manual/cmake-properties.7.rst
+++ b/Help/manual/cmake-properties.7.rst
@@ -217,6 +217,7 @@ Properties on Targets
/prop_tgt/LINK_LIBRARIES
/prop_tgt/LINK_SEARCH_END_STATIC
/prop_tgt/LINK_SEARCH_START_STATIC
+   /prop_tgt/LINK_WHAT_YOU_USE
/prop_tgt/LOCATION_CONFIG
/prop_tgt/LOCATION
/prop_tgt/MACOSX_BUNDLE_INFO_PLIST
diff --git a/Help/manual/cmake-variables.7.rst 
b/Help/manual/cmake-variables.7.rst
index 85b8eae..36d00dc 100644
--- a/Help/manual/cmake-variables.7.rst
+++ b/Help/manual/cmake-variables.7.rst
@@ -275,6 +275,7 @@ Variables that Control the Build
/variable/CMAKE_LINK_INTERFACE_LIBRARIES
/variable/CMAKE_LINK_LIBRARY_FILE_FLAG
/variable/CMAKE_LINK_LIBRARY_FLAG
+   /variable/CMAKE_LINK_WHAT_YOU_USE
/variable/CMAKE_MACOSX_BUNDLE
/variable/CMAKE_MACOSX_RPATH
/variable/CMAKE_MAP_IMPORTED_CONFIG_CONFIG
diff --git a/Help/prop_tgt/LINK_WHAT_YOU_USE.rst 
b/Help/prop_tgt/LINK_WHAT_YOU_USE.rst
new file mode 100644
index 000..32d6edb
--- /dev/null
+++ b/Help/prop_tgt/LINK_WHAT_YOU_USE.rst
@@ -0,0 +1,15 @@
+LINK_WHAT_YOU_USE
+---
+
+This is a boolean option that when set to ``TRUE`` will automatically run
+``ldd -r -u`` on the target after it is linked. In addition, the linker flag
+``-Wl,--no-as-needed`` will be passed to the target with the link command so
+that all libraries specified on the command line will be linked into the
+target. This will result in the link producing a list of libraries that
+provide no symbols used by this target but are being linked to it.
+This is only applicable to executable and shared library targets and
+will only work when ld and ldd accept the flags used.
+
+This property is initialized by the value of
+the :variable:`CMAKE_LINK_WHAT_YOU_USE` variable if it is set
+when a target is created.
diff --git a/Help/variable/CMAKE_LINK_WHAT_YOU_USE.rst 
b/Help/variable/CMAKE_LINK_WHAT_YOU_USE.rst
new file mode 100644
index 000..90c4d3f
--- /dev/null
+++ b/Help/variable/CMAKE_LINK_WHAT_YOU_USE.rst
@@ -0,0 +1,6 @@
+CMAKE_LINK_WHAT_YOU_USE
+-
+
+Default value for :prop_tgt:`LINK_WHAT_YOU_USE` target property.
+This variable is used to initialize the property on each target as it is
+created.
diff --git a/Source/cmMakefileExecutableTargetGene

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-222-g74ee264

[Bill Hoffman]

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, next has been updated
   via  74ee264c0bcd5f5a003cc8e3ebf8f1b38e2ac3e5 (commit)
   via  89ae032fb010197715d8308697987421083d604a (commit)
   via  a8942cd2b555f72c39fdac6df54ecff52d58e975 (commit)
   via  24d7e3ea16e7cb687010c03a35621053f8ed74fb (commit)
  from  c0253804aed4f21ba5b9dede973a59bc65f65e47 (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 -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=74ee264c0bcd5f5a003cc8e3ebf8f1b38e2ac3e5
commit 74ee264c0bcd5f5a003cc8e3ebf8f1b38e2ac3e5
Merge: c025380 89ae032
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Fri Jun 10 10:31:43 2016 -0400
Commit: CMake Topic Stage <kwro...@kitware.com>
CommitDate: Fri Jun 10 10:31:43 2016 -0400

Merge topic 'link_what_you_use' into next

89ae032f use inline markup for rst files and call ldd directly
a8942cd2 add documentation for LINK_WHAT_YOU_USE
24d7e3ea Add support for ldd -u -r as link what you use


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=89ae032fb010197715d8308697987421083d604a
commit 89ae032fb010197715d8308697987421083d604a
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Thu Jun 9 17:12:13 2016 -0400
Commit: Bill Hoffman <bill.hoff...@kitware.com>
CommitDate: Thu Jun 9 17:12:13 2016 -0400

use inline markup for rst files and call ldd directly

diff --git a/Help/prop_tgt/LINK_WHAT_YOU_USE.rst 
b/Help/prop_tgt/LINK_WHAT_YOU_USE.rst
index 76bfafa..32d6edb 100644
--- a/Help/prop_tgt/LINK_WHAT_YOU_USE.rst
+++ b/Help/prop_tgt/LINK_WHAT_YOU_USE.rst
@@ -1,10 +1,10 @@
 LINK_WHAT_YOU_USE
 ---
 
-This is a boolean option that when set to TRUE will automatically run
-ldd -r -u on the target after it is linked. In addition, the linker flag
--Wl,--no-as-needed will be passed to the target with the link command so that
-all libraries specified on the command line will be linked into the
+This is a boolean option that when set to ``TRUE`` will automatically run
+``ldd -r -u`` on the target after it is linked. In addition, the linker flag
+``-Wl,--no-as-needed`` will be passed to the target with the link command so
+that all libraries specified on the command line will be linked into the
 target. This will result in the link producing a list of libraries that
 provide no symbols used by this target but are being linked to it.
 This is only applicable to executable and shared library targets and
diff --git a/Tests/RunCMake/CMakeLists.txt b/Tests/RunCMake/CMakeLists.txt
index 4be81e9..8fb91a9 100644
--- a/Tests/RunCMake/CMakeLists.txt
+++ b/Tests/RunCMake/CMakeLists.txt
@@ -307,9 +307,8 @@ if(CMAKE_OSX_ARCHITECTURES AND XCODE AND NOT 
"${XCODE_VERSION}" MATCHES "^[^12]"
 endif()
 
 if("${CMAKE_GENERATOR}" MATCHES "Make|Ninja")
-  find_program(LDD_PATH ldd)
-  if(UNIX AND LDD_PATH)
-execute_process(COMMAND ${LDD_PATH} --help
+  if(UNIX)
+execute_process(COMMAND ldd --help
   OUTPUT_VARIABLE LDD_HELP)
 if("${LDD_HELP}" MATCHES
 "(-r, --function-relocs.*process data and function relocations|-u, 
--unused.*print unused direct dependencies)")

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a8942cd2b555f72c39fdac6df54ecff52d58e975
commit a8942cd2b555f72c39fdac6df54ecff52d58e975
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Thu Jun 9 16:32:24 2016 -0400
Commit: Bill Hoffman <bill.hoff...@kitware.com>
CommitDate: Thu Jun 9 16:32:24 2016 -0400

add documentation for LINK_WHAT_YOU_USE

diff --git a/Help/manual/cmake-properties.7.rst 
b/Help/manual/cmake-properties.7.rst
index 3403dcd..6a7560a 100644
--- a/Help/manual/cmake-properties.7.rst
+++ b/Help/manual/cmake-properties.7.rst
@@ -217,6 +217,7 @@ Properties on Targets
/prop_tgt/LINK_LIBRARIES
/prop_tgt/LINK_SEARCH_END_STATIC
/prop_tgt/LINK_SEARCH_START_STATIC
+   /prop_tgt/LINK_WHAT_YOU_USE
/prop_tgt/LOCATION_CONFIG
/prop_tgt/LOCATION
/prop_tgt/MACOSX_BUNDLE_INFO_PLIST
diff --git a/Help/manual/cmake-variables.7.rst 
b/Help/manual/cmake-variables.7.rst
index 85b8eae..36d00dc 100644
--- a/Help/manual/cmake-variables.7.rst
+++ b/Help/manual/cmake-variables.7.rst
@@ -275,6 +275,7 @@ Variables that Control the Build
/variable/CMAKE_LINK_INTERFACE_LIBRARIES
/variable/CMAKE_LINK_LIBRARY_FILE_FLAG
/variable/CMAKE_LINK_LIBRARY_FLAG
+   /variable/CMAKE_LINK_WHAT_YOU_USE
/variable/CMAKE_MACOSX_BUNDLE
/variable/CMAKE_MACOSX_RPATH
/variable/CMAKE_MAP_IMPORTED_CONFIG_CONFIG
diff --git a/Help/prop_tgt/LINK_WHAT_YOU_USE.

Re: [CMake] CMake v3.6.0 rc1

[Bill Hoffman]

On 6/8/2016 6:02 PM, Gonzalo Garramuño wrote:

I tried v3.6.0 rc1 but it fails on linking with a message about unknown
symbols when doing cmake -E vs_link_dll on a windows library.  It seems
not to recognize the symbols in, for example, tinyxml2.

The same code works just fine under cmake v3.5.2.
Can you post an example project that shows this problem and describe 
which version of VS you are using and the steps needed to reproduce the 
problem?


Thanks.

-Bill

--

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

Re: [CMake] [EXTERNAL] Re: Get ctest -S script to pull from git branch other than 'master'?

[Bill Hoffman]

On 6/8/2016 12:59 PM, Bartlett, Roscoe A wrote:

Xavier,



Thanks for the info.  I got another email from Brad King and he also
pointed out the same thing:




https://cmake.org/cmake/help/v3.6/command/ctest_start.html#command:ctest_start



and then Brad updated the documentation for ctest_update() to state that
it will just keep you on whatever tracking branch you are on and do a
git pull (after doing a reset --hard to wipe out any local changes).



With is info, I can do what I need.



If you have something external like jenkins doing the build, you can 
also use:

https://cmake.org/cmake/help/latest/variable/CTEST_UPDATE_VERSION_ONLY.html?highlight=ctest_update_version_only

If set in the ctest script the ctest_update command will just get the 
hash and do nothing else.


-Bill

--

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

Re: [CMake] CPack with BZIP2 is a lot slower than GNU tar

[Bill Hoffman]

On 6/2/2016 5:29 AM, Alessio wrote:

I'm comparing the following two things:
  1. cpack TBZ2 generator
  2. "tar cjf" the same files as with cpack. (j option = BZIP2 compression)

I cannot avoid CPack. It takes care of way too many little details of
the packaging. Obviously we use it via lots of install() statements in
our CMakeLists.txt files.

Sounds like it needs some performance testing.   One thing to try would 
be to compare cmake -E tar with tar and see if it is libtar that is 
slow, or something CPack is doing.  After that, maybe calgrind or other 
tools to profile cpack.


-Bill

--

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

Re: [CMake] ExternalProject_Add + imported targets: no rule to make yourlibrary.so

[Bill Hoffman]

On 4/28/2016 4:31 PM, SnakE wrote:

set_target_properties(foo PROPERTIES IMPORTED_LOCATION foo.so)

https://cmake.org/cmake/help/v3.0/prop_tgt/IMPORTED_LOCATION.html?highlight=imported_location

"Full path to the main file on disk for an IMPORTED target."

You need to use a full path to foo.so, works by luck with make.

-Bill


--

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

Re: [CMake] Unable to download cmake-3.5.1 (a 403 error)

[Bill Hoffman]

On 4/13/2016 12:40 PM, Asiga Nael via CMake wrote:

Hi,

I'm trying to download the file cmake-3.5.1-Darwin-x86_64.dmg but it brings me to a page 
at public.kitware.com with a 403 error: "Permission Denied You do not have 
permission to retrieve the URL or link you requested."

Is there any mirror hosting cmake releases, so that I can download it from 
other place?

Should be fixed now.

-Bill
--

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

Re: [CMake] CMake download blocked by Google Chrome

[Bill Hoffman]

On 4/10/2016 10:40 AM, Raymond Wan wrote:

Google seems to have marked it as "partially dangerous".  Of course,
Google could be wrong -- I think this filter list is maintained
automatically and maybe they got the criteria wrong this time.
We are looking into this.  We have had false positives in the past for 
virus checkers and the downloads in the past.


-Bill

--

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

Re: [cmake-developers] Parallel ctest issues on the MinGW-w64/MSYS2 platform

[Bill Hoffman]

On 3/29/2016 5:34 PM, Alan W. Irwin wrote:

In any case, whatever the issue is, Arjen appears (so far) to have
found a reliable reproducer with the -j option for ctest.  So I hope
others here try the -j option for ctest on MinGW-w64/MSYS2 platforms
for their favorite projects to get a better idea of how widespread
this issue is.
I would recommend building ctest with debug.  Then running it with -j 
and then use gdb to figure out where it is stuck.   Until we know 
exactly where it is stuck, the rest is pure speculation


-Bill


--

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] Best way to show/include CMake files in IDE

[Bill Hoffman]

On 3/8/2016 2:25 PM, David Doria wrote:

add_custom_target(MyProject_HDRS SOURCES MyHeader.h MyImplementation.hpp)

It sounds like David says you can do the same for your .cmake files.
This is pretty awkward though - it seems like there should be more of an
explicit function for this, something like:

add_files_to_IDE(MyHeader.h MyImplementation.hpp)

This would make it much more clear what this line is for and would
prevent forcing this "abuse" of the concept of a target for a very
common use case.
You just add them to the target and it should work.  Platforms that 
don't need those files will ignore them and IDEs that want them will use 
them.




--
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

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

Re: [CMake] Is there any way to use clang-cl with MSBuild on Windows?

[Bill Hoffman]

On 1/29/2016 1:04 PM, Yi-Hong Lyu wrote:

Hello everyone,

I am a newbie of CMake. I would like to use clang-cl with MSBuild on
Windows. However it always use MSVC 19.0.23506.0 as the identified
compiler even I defined CMAKE_C_COMPILER / CMAKE_CXX_COMPILER /
CMAKE_C_COMPILER_FORCED / CMAKE_CXX_COMPILER_FORCED:

$ cmake -DCMAKE_C_COMPILER=clang-cl -DCMAKE_CXX_COMPILER=clang-cl
-DCMAKE_C_COMPILER_FORCED=ON -DCMAKE_CXX_COMPILER_FORCED=ON ..\src\
-- Building for: Visual Studio 14 2015
-- The CXX compiler identification is MSVC 19.0.23506.0
-- The C compiler identification is MSVC 19.0.23506.0
-- Configuring for standalone build.
-- Found PythonInterp: C:/Python34/python.exe (found version "3.4.4")
-- Sphinx disabled.
.
.
.

PS. The environment PATH is already set to clang-cl.

I am wondering whether there is any option that I can force MSBuild use
clang-cl instead.

You could get it to work with ninja, make or nmake.  How does one 
normally force the VS IDE to use the clang compiler?


-Bill

--

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

Re: [CMake] WINDOWS_EXPORT_ALL_SYMBOLS

[Bill Hoffman]

On 1/26/2016 12:51 PM, Bill Hoffman wrote:


I am running the community edition...  Maybe there is some difference
with express?

One other question, did you build 64 or 32 bit?

-Bill

--

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

Re: [CMake] WINDOWS_EXPORT_ALL_SYMBOLS

[Bill Hoffman]

On 1/26/2016 5:12 AM, Micha Renner wrote:

It prevents that I can link the library to a program since there is no
__local_stdio_printf_options etc.

May be there exists an explanation.

Greetings

Michael


cmake 3.4.2 Windows 10 VS Express 15

So, I am able to get this to work with Visual Studio 14 2015.  CMake 3.4.3

$ cat TLib.dir/Debug/exportall.def
EXPORTS
testCall1_1
__local_stdio_printf_options
_vfprintf_l
vprintf
printf
_vsnprintf_l
vsprintf

Those symbols show up in the .def file but get resolved by system libraries.

Here is my link line:
(output from cmake --build .)

Link:
  C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\link.exe 
/ERRORREPORT:QUEUE 
/OUT:"C:\Users\hoffman\Documents\BuildDll\BuildDLL-44\src\b\Debug\TLib.dll" 
/INCREMENTAL /NOLOGO kernel32.lib user32.lib gdi32.lib winspool.lib 
shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib 
/DEF:"TLib.dir\Debug\exportall.def" /MANIFEST 
/MANIFESTUAC:"level='asInvoker' uiAccess='false'" /manifest:embed /DEBUG 
/PDB:"C:/Users/hoffman/Documents/BuildDll/BuildDLL-44/src/b/Debug/TLib.pdb" 
/SUBSYSTEM:CONSOLE /TLBID:1 /DYNAMICBASE /NXCOMPAT 
/IMPLIB:"C:/Users/hoffman/Documents/BuildDll/BuildDLL-44/src/b/Debug/TLib.lib" 
/MACHINE:X86 /SAFESEH  /machine:X86 /debug /DLL TLib.dir\Debug\tlib.obj


You can see I get the dll and .lib file here:
$ ls Debug/
TLib.dll  TLib.exp  TLib.ilk  TLib.lib  TLib.pdb

I am running the community edition...  Maybe there is some difference 
with express?


-Bill


--

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

Re: [CMake] ExternalProject not being configured / custom_command not executed

[Bill Hoffman]

On 1/21/2016 2:33 PM, Kügler, David wrote:

Hello everybody,

I am trying to build a Project (via ExternalProject from a parent project).

More precisely, I want to build the plus Toolkit (plustoolkit.org) and
the subprojects using the build “superproject” (i.e. PlusBuild).

It partly seems to work fine, but the ExternalProject PlusApp never
actually gets built. Build-rule-files in the CMakeFiles folder are
created, but it seems, the “configure”-command is never actually called.
Thusly there is never ANY file created in the BINARY_DIR of the
PlusApp-project subfolder.

Why do I ask you guys, and not the people from Plus? Because a second
subproject (i.e. PlusLib) just works fine, AND if I go ahead and extract
the configure-command (i.e. the command-line-command) either from
–trace-expand or from the PlusApp-CfgCmd.txt file (replacing ‘;’ with ‘“
“’ (space and double quotation) ) it works fine.

So: The command to configure, and the rule-files are created from CMake,
but the command is actually not executed and I cannot say why.

This definitely seems to be a hiccup in CMake, but I am at a deadend.

Any Idea, why this is so?

Using CMake 3.4.10 ; Visual Studio 2013 x64 ; Windows 8.1 ; plustoolkit

(I hope this would be the relevant information)

Still sounds like a question for the PlusApp guys.  It is possible that 
they have some error in their CMakeLists.txt files that prevents this 
from working.  CMake is pretty well tested and external project tests 
are all passing for that platform and version  of CMake.


-Bill

--

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

Re: [CMake] Changing the the current generator in CMake GUI

[Bill Hoffman]

On 1/15/2016 7:19 PM, mozzis wrote:

Well, CMAKE is the thing that is conflating this idea of a “generator”
(which is clearly a concept in CMAKE’s own domain of “build
configuration generator”) with the idea of “platform” or “architecture”
(which is a concept in the domain of certain kinds of build tools, such
as a C compiler.) It would be healthier if platform/arch were broken out
as a separate item in CMAKE, i.e. CMAKE recognizes that some build tools
have this concept, but is (possibly) agnostic about how it is
represented. I assume that it is not really possible to do so in the
config files that drive CMAKE at present, only because I have never seen
it done and did not find it when I went looking. Instead, that
information is scattered across several files in the CMakeFiles folder.


So, in CMake it currently supports one platform/arch at a time.  This is 
because of support for system introspection (trycompile/tryrun).



configurations. The resulting build time was cut by a factor of 5, plus
it became much easier (for me anyways) to be able to do things like
change the output file names based on platform, something I have so far
found impossible to do with CMake. [Once again, it really has no concept
of this.]


I really can't believe the build was faster, that just does not sound 
possible.  At the end of the day CMake gives VS  a list of files and VS 
compiles them.  If you want something really fast with VS, use the CMake 
ninja generator instead of VS and get builds that are significantly 
faster than VS IDE builds.  I would like to see a real example of that 
which I can reproduce, because we could modify CMake to create a similar 
project file.  The only thing that could improve build times that much 
is adding the /MP flag, but that can be done with CMake right now. (see 
my blog http://www.kitware.com/blog/home/post/434)


CMake does have the ability to change output names based on 
configuration with target properties.  However, the VS project files are 
not intended to be changed but only generated.  The changes should all 
happen in the CMake input files or the next time you run CMake all the 
changes will be lost.  CMake is not intended to create an IDE file that 
then can be changed/maintained on its own.  It will be erased and 
overwritten as soon as there is any change in a CMake input file used to 
generate it.


I would do the same thing for OpenCV, but it is ten times worse than
HDF5 in this regard. For instance, apparently project files are modified
/as part of the MSVS build process/, so that Visual Studio always
complains about project files needing to be reloaded after a build. This
is a recipe for mysterious bugs that you will never be able to fix.
That sounds like something wrong in the OpenCV CMake files, it should 
not rerun cmake with each build.


I have created/maintained multi-platform projects, and I find that the
effort needed to produce efficient, readable makefiles for each platform
is worth it. Once done, I can change the platform or the library type or
similar parameters by changing one switch in each platform’s makefile.
Plus there are fewer gotchas at runtime, as not querying the build
environment for every build ensures more consistent behavior in the
binaries I am going to distribute.

If you have the time to maintain hand crafted makefiles/IDE project 
files then more power to you.  Also, I assume that every developer on 
your project knows how to make changes to each platforms build files 
when they want to add a new source file or library.

Thanks again to all for the comments on this thread. It is good to know
that development continues on this tool. At some point, it may become
more interesting for me.

I really don't care if you use CMake or not.  However, I want to make 
sure that I clear up any misconceptions that this thread may raise for 
others.  To sum things up:


- CMake is a cross platform build generator, the makefiles/IDE/build 
files that it generates are not meant to be human readable and 
especially human editable. The way to change what happens in the build 
has to be done by changing either the source CMakeLists.txt files or the 
CMakaCache.txt and not the build files.  This is because the build files 
are written over each time CMake is run.


- CMake is setup to make it easier for cross platform development with a 
team of developers that only needs to know how to add sources and modify 
the build by changing the input to CMake.  They are not required to know 
how to edit and maintain files for make/ninja/VS 9,10,11,12,13,14, Xcode 
various versions.


- You should use out of source builds and once a build generator is 
picked (VS some version, make, ninja, ect), You can not change that 
build generator without erasing the directory or creating a new one.


- It might be possible in future versions of CMake that VS IDEs support 
64/32 bit builds like they support release/debug right now, but 
currently this is not supported in a 

Re: [CMake] Changing the the current generator in CMake GUI

[Bill Hoffman]

On 1/15/2016 11:26 AM, mozzis wrote:

You can not change the generator.  It is better to remove the entire
build tree.  Out of source builds are a best practice with CMake.  Once
a build tree has been configured with one compiler, it must be
completely removed to change to a new compiler


Clearly, "can not" is incorrect, since I did. "must be" seems also
incorrect.


You can do it by changing the CMakeCache.txt file, but it won't work in 
the general case.  You should put them in separate directories: build-32 
and build-64.

It seems like the developers don't understand about 32-bit vs. 64-bit
builds, or don't intend for this tool to be used with software that is a
product. Determining that after painstakingly configuring all of the build
options, the user must throw it all away in order to build for the other
"bitness", seems wrong. Almost anyone that is intending to build software
that can be installed (without the end user having to build it from source
every time, that way lies madness) needs to produce a 32-bit and a 64-bit
package these days.


You can build both 32 and 64 from the same SOURCE tree, just not the 
same build tree.


src
build32   (cmake ../src -G"Visual Studio 10 2010")
build64   (cmake ../src -G"Visual Studio 10 2010 Win64")

You seem to be trying to reuse the same build tree for different builds 
which is not a supported use case.  I think if you stopped doing that 
your life might get easier when working with CMake projects.



-Bill

--

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

Re: [CMake] Changing the the current generator in CMake GUI

[Bill Hoffman]

On 1/15/2016 2:41 PM, Greg Marr wrote:

You can do both in the same solution/projects with the Microsoft fork
of CMake, but it's not a general solution, and it doesn't handle
different settings for 32 bit and 64 bit.  Because of that, they're
"not pushing too hard" for it to be in mainline CMake.

https://cmake.org/pipermail/cmake/2015-August/061346.html


Yes, and things like CMAKE_SIZEOF_VOID_P would not have valid values. 
However, if you want cmake builds to work, you should never change the 
generator in a CMakeCache.txt file, it is going to more often than not 
cause problems.  A build tree should be configured with one generator 
and if you need another generator you should use a different directory 
and a different build tree sharing the same source tree.


-Bill
--

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

Re: [CMake] Changing the the current generator in CMake GUI

[Bill Hoffman]

On 1/14/2016 3:02 PM, mozzis wrote:

I was able to edit CMakeCache.txt and CPackConfig.cmake (with CMake GUI
closed)
  I changed
   CMAKE_GENERATOR:INTERNAL=Visual Studio 10 2010 Win64
to
   CMAKE_GENERATOR:INTERNAL=Visual Studio 10 2010

and then in general looked for the string "64" and made appropriate changes.
I then started CMake GUI, noted that the "Current Generator" was to my
liking, and did Configure and Generate steps again.
You can not change the generator.  It is better to remove the entire 
build tree.  Out of source builds are a best practice with CMake.  Once 
a build tree has been configured with one compiler, it must be 
completely removed to change to a new compiler.  You are changing from 
32 bit to 64 bit, this means that all the try-compile stuff needs to be 
re-run as the answers are likely to be different.


All in all, doesn't seem that it would be too hard for CMake devs to
implement a function to do this, but IMO Cmake is a mistake anyway, I only
use it when forced (e.g., OpenCV.) CMake butchers MS Visual Studio project
files, and makes it much harder to maintain projects that use it. Which I
guess is kind of the opposite of the intended effect. More intelligent use
of existing macros for both make and MSVS would go a long way to making it
useful.
Thanks for the praise...  :)   CMake creates VS projects that should 
work to build the project that is the goal. I don't understand about 
make and MSVS, CMake can create makefiles or ninja files if that is what 
you are talking about.


-Bill
--

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

Re: [CMake] FORTRAN name mangling

[Bill Hoffman]

On 1/11/2016 2:31 PM, Zaak Beekman wrote:

Happy hacking!

FYI:
There is a longer version of that blog found here:
http://www.netlib.org/lapack/lawnspdf/lawn270.pdf
bind(c) sounds like a good idea if your compilers support it.

-Bill

--

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

Re: [CMake] get_prerequisites() - fails with No such file or directory

[Bill Hoffman]

On 1/6/2016 6:14 AM, roze...@volny.cz wrote:

When get_prerequisites() is not called, the build works correctly. So, did I do 
anything wrong?

 get_prerequisites needs to be called at install time and not CMake time.

Look at install(CODE "")

-Bill

--

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

Re: [CMake] Parallel jobs failed for cmake

[Bill Hoffman]

On 12/14/2015 1:34 AM, Igor Sobinov wrote:


Thanks, that's clear.

So, If I write in makefile
No not really clear.  The problem is NOT in your makefile.  The problem 
is in your custom command that calls make again.  That is where the 
problem is.  In your custom command (which you have not provided the 
code for), it is clear that you call make without $(MAKE)


If you go back to your second post on this topic:
igor 5460 0.0 0.0 101152 972 pts/3 S+ 08:10 0:00 | \_ make build_release -j5
igor 5466 0.0 0.0 106096 1164 pts/3 S+ 08:10 0:00 | \_ /bin/sh -c cd 
/home/igor/build_root/release_target; make release


Right there is the problem.  The custom command does this:
/bin/sh -c cd /home/igor/build_root/release_target; make release

It needs to do this:

/bin/sh -c cd /home/igor/build_root/release_target; $(MAKE) release

You will need to escape the $ to get this right.

You can check the generated makefile if you are having trouble.

-Bill
--

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

Re: [CMake] Parallel jobs failed for cmake

[Bill Hoffman]

On 12/11/2015 7:24 AM, Igor Sobinov wrote:

Hello Bill,

yes, make release is a custom command but that's not important.
I do the following:
# cd /home/igor/build_root/release_target
# make release -j5
Yes, it is important, it is the reason it is not working.  The custom 
command needs to use $(MAKE) and not make to call make or you will get 
this error.  Child make calls need environment variables to get parallel 
builds to work.  The MAKE env var is used to pass them around.


-Bill

--

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

Re: [CMake] Parallel jobs failed for cmake

[Bill Hoffman]

On 12/10/2015 12:19 AM, Igor Sobinov wrote:

igor 5460 0.0 0.0 101152 972 pts/3 S+ 08:10 0:00 | \_ make build_release -j5
igor 5466 0.0 0.0 106096 1164 pts/3 S+ 08:10 0:00 | \_ /bin/sh -c cd
/home/igor/build_root/release_target; make release
igor 5467 0.0 0.0 101184 1060 pts/3 S+ 08:10 0:00 | \_ make release
Looks like you created the build_release target as a custom command that 
does:

make release

This will strip the -j off of the make process and you get the warning. 
 If you are going to call make recursively like that you have to use 
$(MAKE) so that all the right env stuff gets passed down.  CMake does 
this with its calls to make.


You should be able to do what we do in ExternalProject and use $(MAKE). 
 I would have to see your CMakeLists.txt code and the custom command to 
help more.


-Bill

--

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

Re: [CMake] How to generate for Ninja + MSVC?

[Bill Hoffman]

On 12/2/2015 10:39 PM, iosif neitzke wrote:

Ah, okay, thanks.  From cmake-gui the solution equivalent would be
selecting the Ninja generator but specifying native compilers (cl.exe
for this example) instead of using the default native compilers?
.
Yes, that would work as well.  As long as cmake-gui was run in an 
environment that had the compiler setup to work from the command line.


-Bill

--

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

Re: [CMake] How to generate for Ninja + MSVC?

[Bill Hoffman]

On 12/2/2015 2:39 PM, Robert Dailey wrote:

For some reason Strawberry Perl installed gcc/g++ to my PATH. I
removed this and it's finding MSVC 19 now. Thanks.


Could also set CC and CXX to cl before running CMake.


--
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

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

Re: [CMake] How to generate for Ninja + MSVC?

[Bill Hoffman]

On 12/2/2015 8:22 PM, iosif neitzke wrote:

Isn't this what Generator Toolset selection is for?

ex. cmake -G Ninja -T v140

http://cmake.blogspot.com/2013/05/cmake-2811-available-for-download.html
No, that is for telling the VS IDE which tool set to use.  It has no 
effect on the Ninja generator.  Like makefiles the ninja generator 
assumes it is running in an environment that is setup to run a compiler 
from the command line.  If there is more than one compiler it picks one. 
 If you have more than one compiler you can force it to pick one over 
the other with CC and CXX variables.   The IDE has its own environment 
for the compiler and some IDEs support more than one tool chain and the 
-T is how you tell it to use something other than its default.


-Bill

--

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

Re: [CMake] actually using cmake alternative to convenience libraries

[Bill Hoffman]

On 11/17/2015 2:46 PM, Jack Stalnaker wrote:

I read about those, but they don't seem to provide a way to add linked
in libraries, so it didn't seem to add a lot over a list of sources. In
autotools, you could bind your convenience lib with any dependencies via
a LIBADD primary, and the added libs would automatically propagate to
the final target. This of course works in cmake if I build a real
library, but if I try to link a library (e.g. say the system math
library) to the object library, cmake tells me it cannot do that for
object libraries. In that case, it seems like I still need to create the
foobarLIBRARIES variable to provide to target_link_libraries later.

Am I missing something, or is there a way to somehow attach the
necessary external libraries to the object library as well?
It is a feature that has not been implemented.  However, I would say 
that it does add something over lists of sources.  It avoids all the 
cache and parent scope in this thread.  Seems like it would still be 
more simple to use object libraries than to try and do it via lists of 
sources.


To add that feature would be some work, but is possible:
 https://cmake.org/Bug/view.php?id=14778
 https://cmake.org/Bug/view.php?id=14970

I still think the object libraries might work for you.

-Bill
--

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-1441-gacb550c

[Bill Hoffman]

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, next has been updated
   via  acb550c33e9b1c6a19fb7fb9d691bd45bd8ec795 (commit)
   via  75004280af22edd22a3efb7b47d5d87f2da65354 (commit)
  from  e8f8a0805ff5cf70cd962c8365dcff47797cb45d (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 -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=acb550c33e9b1c6a19fb7fb9d691bd45bd8ec795
commit acb550c33e9b1c6a19fb7fb9d691bd45bd8ec795
Merge: e8f8a08 7500428
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Thu Nov 19 17:24:20 2015 -0500
Commit: CMake Topic Stage <kwro...@kitware.com>
CommitDate: Thu Nov 19 17:24:20 2015 -0500

Merge topic 'fix_bigobj_64_autodef' into next

75004280 Fix auto export symbols for Dlls containing /bigobj for 64bit 
builds.


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=75004280af22edd22a3efb7b47d5d87f2da65354
commit 75004280af22edd22a3efb7b47d5d87f2da65354
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Thu Nov 19 17:21:03 2015 -0500
Commit: Bill Hoffman <bill.hoff...@kitware.com>
CommitDate: Thu Nov 19 17:21:03 2015 -0500

Fix auto export symbols for Dlls containing /bigobj for 64bit builds.

This fixes a bug where 64 bit builds with /bigobj incorrectly determined
that the object files were not 64 bit. This manifested itself with
printf type functions showing up as undefined because the leading
underscore was being removed and should not be removed.

diff --git a/Source/bindexplib.cxx b/Source/bindexplib.cxx
index 64621e0..e7263ae 100644
--- a/Source/bindexplib.cxx
+++ b/Source/bindexplib.cxx
@@ -422,7 +422,7 @@ DumpFile(const char* filename,
  DumpSymbols<cmANON_OBJECT_HEADER_BIGOBJ, cmIMAGE_SYMBOL_EX>
symbolDumper((cmANON_OBJECT_HEADER_BIGOBJ*) lpFileBase, symbols,
 dataSymbols,
-(dosHeader->e_magic == IMAGE_FILE_MACHINE_AMD64));
+(h->Machine == IMAGE_FILE_MACHINE_AMD64));
  symbolDumper.DumpObjFile();
   } else {
  printf("unrecognized file format in '%s'\n", filename);
diff --git a/Tests/RunCMake/AutoExportDll/sub/sub.cxx 
b/Tests/RunCMake/AutoExportDll/sub/sub.cxx
index 9766b41..9a3145e 100644
--- a/Tests/RunCMake/AutoExportDll/sub/sub.cxx
+++ b/Tests/RunCMake/AutoExportDll/sub/sub.cxx
@@ -1,4 +1,6 @@
+#include 
 int sub()
 {
+  printf("");
   return 10;
 }

---

Summary of changes:
 Source/bindexplib.cxx|2 +-
 Tests/RunCMake/AutoExportDll/sub/sub.cxx |2 ++
 2 files changed, 3 insertions(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

Re: [CMake] actually using cmake alternative to convenience libraries

[Bill Hoffman]

On 11/17/2015 10:37 AM, Jack Stalnaker wrote:

I'm trying to figure out the best way to handle something that was a
convenience lib under autotools. I realize that there's a FAQ entry here:

https://cmake.org/Wiki/CMake_FAQ#Does_CMake_support_.22convenience.22_libraries.3F

But its terse 2 paragraphs don't say how to actually do what it
suggests. My problem is this. I have this source tree:

lib
|--foo.c
|--foo.h
|--bar.c
|--bar.h
|--baz.c
src
|--goo.c

In lib, I need to somehow collectively refer to foo and bar. Okay, so I
can create a variable:

set(foobarSRCS foo.c bar.c)
set(foobarLIBS ${externalLibFound})

which is what the FAQ entry seems to suggest. However, this variable is
not visible to goo.c. Okay, so as an alternative, I can do this:

set(foobarSRCS foo.c bar.c PARENT_SCOPE), etc.

but now the variable is not visible to baz.c, which also must include
the srcs to create a module library called _baz! I can of course do
something like this:

set(foobarSRCSLOC foo.c bar.c)
set(foobarSRCS ${foobarSRCSLOC} PARENT_SCOPE)

but this feels dirty and repetitive.

I also realize that I can just create the variables in src, but that
kind of defeats the entire purpose of walling of the common libs and
their dependencies in the first place.

Is this the right way to work, or am I missing something simple?

There is a new feature to do that:

https://cmake.org/Wiki/CMake/Tutorials/Object_Library

--
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

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

Re: [CMake] CMake on OpenVMS - Bootstrap CMake complaining that “pid_t doesn’t exist on this platform?”

[Bill Hoffman]

On 11/1/2015 4:19 PM, Custin, Jay (CSC Sw Middleware) wrote:

Anyone have any ideas?


Look in the CMakeError.log file and find out why it is not finding pid_t.

-Bill


--

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

Re: [CMake] CMake on OpenVMS - Apparent roadblock buried within cmake-3.3.2\Tests\CMakeLists.txt

[Bill Hoffman]

On 10/30/2015 11:18 AM, Custin, Jay (CSC Sw Middleware) wrote:

Interrupting/preventing the automatic execution of the bootstrapped
CMake in the end of the bootstrap script and then try to execute it
from the shell prompt using the same basic switches I used for the
"simple" project above.


This sounds like a good plan.  You have a basic makefile working!  That 
is pretty cool.


I would run everything from bash all the time.

Next step would be to run the bootstrapped cmake from the bash shell on 
CMake itself. Must be a configure file or execute_process in there that 
is messing things up.  But hey, you have the basic CMake working!


-Bill

--

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

Re: [CMake] The project files that CMake generates can't be moved

[Bill Hoffman]

On 10/30/2015 1:48 PM, Attila Krasznahorkay wrote:

I'm a bit surprised about this answer.

Sure, build areas are not to be moved around. I completely agree. But
this is why we have the concept of installing releases. As long as
you configure your build correctly, you should be able to move around
your install directory. As the binaries by default will not have
absolute paths in them after installation. At least not to
"themselves".

(I am myself working these days on how to install larger projects
such that after installation, after moving the installed directories
around, including the directories that the build was done against,
the code would still work. It's not trivial to do, but it's not
impossible either. One just has to use $ in a
clever way...)

Cheers,


Install trees should be relocatable (that is how cpack works).  However, 
build trees are not.


-Bill
--

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

Re: [CMake] CMake on OpenVMS - Apparent roadblock buried within cmake-3.3.2\Tests\CMakeLists.txt

[Bill Hoffman]

Questions inline:

On 10/28/2015 3:35 PM, Custin, Jay (CSC Sw Middleware) wrote:



So the configuration/bootstrap script seems to blissfully get all the
way to the end and even displays the following:

-

CMake has bootstrapped.  Now run make.

Except when I looked… it had not created the Makefile.  I ran the same
basic process on one of my Linux systems and noticed that in addition to
NOT creating the Makefile… it also did not create the bin subdirectory.
I tried simply adding the –trace option on the bootstrap’s cmake command
(the last thing it does before posting the text above), but that didn’t
seem to reveal any clues.

I would love to simply comment out large swaths of the 3000+ lines of
cmake-3.3.2\Tests\CMakeLists.txt but at this point I don’t have
sufficient understanding of what impact doing this would have and fear
that without the understanding doing so would probably do little to help
me isolate where things appear to have gone awry.


What makes you think there is a problem in Tests/CMakeLists.txt?

Does anyone know where (specifically) I should investigate to determine
where the Makefile itself should get generated?


What files are generated in the build tree?

The toplevel makefile is created here:
void cmGlobalUnixMakefileGenerator3::WriteMainCMakefile()

But there are lots of other files that get created.

One thing you could try is to use the bootstrapped cmake to configure a 
more simple project.  Something like:


project(foo)
add_library(foo foo.c)
foo.c can be an empty file.

Does the bootstrapped cmake work on that project?



What about what triggers the creation of the bin folder?

I would not worry about that yet.

-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

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

Re: [CMake] CMake on OpenVMS - watching CMake build process run through its enormous number of self-tests!!!!

[Bill Hoffman]

On 10/2/2015 12:40 PM, Custin, Jay (CSC Sw Middleware) wrote:

Cautiously optimistic…

Staring at my terminal session watching self-tests execute…

Hey, that is cool.   Hopefully when you are done you can setup a 
dashboard so we can make sure the changes you put into CMake work into 
the future.



https://cmake.org/Wiki/CMake/Git/Dashboard

https://cmake.org/gitweb?p=cmake.git;a=blob_plain;f=cmake_common.cmake;hb=refs/heads/dashboard

Good luck!

I spent some time about 6 or 7 years ago and got most of it working, but 
with no testing it did not last


-Bill

--

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

Re: [CMake] Build log generation in a "custom" way

[Bill Hoffman]

On 9/24/2015 7:47 AM, Attila Krasznahorkay wrote:

Dear All,

I'd like to ask for some advice about the following issue. We're
migrating a very big project (millions of lines of code...) from a
custom build manager to CMake.

The software is put together from separate "packages" that are all
developed by a different set of people. Our nightly build system
collects all these packages, and compiles all of them. In our old
build system we could easily save package-specific build log files
for the nightly system. Making it easy for the developers to quickly
find build problems in their specific package.

Now we'd like to do something similar with CMake. To teach it how to
generate separate build log files for the separate packages.
(Packages in this context are really just subdirectories in the end.)
The clumsy thing that we're doing now is to use a script that we set
for RULE_LAUNCH_COMPILE, RULE_LAUNCH_LINK, and RULE_LAUNCH_CUSTOM.
This script writes log files in a non-too-perfect way, which need to
be stitched together at the end of the build to get "package
specific" build log files.

So the question is whether we could do something better. Does anyone
have an idea/suggestion? I'm happy to give more information about our
setup if needed.



You might want to look into CDash (www.cdash.org).

http://www.kitware.com/media/html/CDashSubprojects.html

Here is an example in the Trilinos project:
http://testing.sandia.gov/cdash/index.php?project=Trilinos=2015-09-23

-Bill

--

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

Re: [CMake] "Pre-configure" step in CMake

[Bill Hoffman]

On 9/24/2015 4:26 PM, Matthäus G. Chajdas wrote:

Hi,

that sounds like it would do the trick. I wasn't aware that
execute_process will block the script until it's done executing. Need to
check this out but that definitely looks like the way to go, thanks!
ExternalProject might be a better option.  It pushes the downloads to 
build time and handles dependencies without having to re-run CMake.  If 
you run a download script at CMake time, it could take an unknown amount 
of time to configure.


-Bill


--

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

Re: [CMake] "Pre-configure" step in CMake

[Bill Hoffman]

On 9/24/2015 5:02 PM, Matthäus G. Chajdas wrote:

Hi,

how does the ExternalProject interact with subsequent find_library calls?

I've seen projects building dependencies through ExternalProject, but
those would the project manually by querying ExternalProject and adding
a new imported target. How would I connect an ExternalProject to one or
more find_library calls?

So, the trick is it all has to be ExternalProject including your 
project.  Then the find_library stuff will work.


EP_add(3rdpartylib)
EP_add(myproj)

# at build time of myproj all of 3rdparytlib will be done and 
discoverable by myproj find_* calls.We often have project-bootstrap 
projects that use external project to configure an environment.


1. build project-bootstrap (all external project stuff)
2. cd myproject, and treat this like a standalone CMake project that has 
just discovered all of its depends on the system.



Is there a downside from configure taking an unknown amount of time? My
expectation was that there is no timeout for the configure step.
It is meant to be an interactive step with cmake-gui.  Also, if there 
are configuration errors you would want to see them up front and not 
after a wait.


-Bill

--

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

Re: [CMake] Continued issues in trying to get CMake working on OpenVMS

[Bill Hoffman]

On 9/21/2015 11:29 AM, Custin, Jay (CSC Sw Middleware) wrote:

I will try adding that option and see what it may reveal... the
output contained in the CMakeOutput.log and CMakeError.log offered
nothing other than politely telling me the test failed.


That is odd...  It should have the stderr/stdout.  There maybe some 
issue with that.  Can you send me those files off the list?


You may want to create a small project to test the flag.  Then use the 
bootstraped cmake to configure it with the --debug-trycompile.


-Bill
--

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

Re: [CMake] Continued issues in trying to get CMake working on OpenVMS

[Bill Hoffman]

On 9/21/2015 10:17 AM, Custin, Jay (CSC Sw Middleware) wrote:

This gets made even more frustrating in that it appears that the
testing phase does a VERY good job cleaning up after itself...



So, the output should all be in CMakeOutput.log and CMakeError.log found 
in the build tree in the CMakeFiles directory.


If you want CMake not to delete the temp files you can use 
--debug-trycompile


http://www.cmake.org/cmake/help/v3.3/manual/cmake.1.html

-Bill

--

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

Re: [CMake] Parallel builds

[Bill Hoffman]

http://www.kitware.com/blog/home/post/434

-Bill

--

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

Re: [CMake] Parallel builds

[Bill Hoffman]

On 9/16/2015 1:47 PM, J Decker wrote:

I see yer right.
Details get foggy after years.
well that's something to add:)


All covered my blog.  :)

-Bill
--

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

Re: [CMake] Parallel builds

[Bill Hoffman]

On 9/16/2015 2:06 PM, Greg Marr wrote:

This part here is inaccurate, at least with the current CMake and
Visual Studio: "To set the flag you will have to edit the CMake cache
with the cmake-gui and add it to the CMAKE_CXX_FLAGS and the
CMAKE_C_FLAGS."

This is all we do in the CMake file that we include in all our
projects: add_compile_options(/MP$ENV{NUMBER_OF_PROCESSORS})

If you don't have a NUMBER_OF_PROCESSORS environment variable, you
just get /MP.

The oversubscription part is still true, but I've never seen randomly
bad object files.


I was writing it from the point of view of NOT having to edit the 
project.  Seems like more of a per build decision to me.  As there could 
be issues, the most reliable way to build is to not use /MP which is why 
CMake does not just do this by default.  So, I would not want to 
recommend that projects make it a default.  But, you can change the 
flags either by editing the CMakeLists.txt files or by editing the 
CMakeCache.txt file to change the flags in the build.


-Bill

--

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

[Cmake-commits] CMake branch, next, updated. v3.3.1-2853-ge6cc5a9

[Bill Hoffman]

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, next has been updated
   via  e6cc5a9fff4689e8b0818e0a21f59f65f1ce7fd3 (commit)
   via  5487b1be38c2003132ec4ddbb1dca615474777e4 (commit)
  from  54329e174573e7d6f5aa497074e4a37bd8167750 (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=e6cc5a9fff4689e8b0818e0a21f59f65f1ce7fd3
commit e6cc5a9fff4689e8b0818e0a21f59f65f1ce7fd3
Merge: 54329e1 5487b1b
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Thu Sep 10 17:16:13 2015 -0400
Commit: CMake Topic Stage <kwro...@kitware.com>
CommitDate: Thu Sep 10 17:16:13 2015 -0400

Merge topic 'fix_64bit_autodef' into next

5487b1be Fix autoexport feature for 64 bit Windows builds by not removing 
leading _


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5487b1be38c2003132ec4ddbb1dca615474777e4
commit 5487b1be38c2003132ec4ddbb1dca615474777e4
Author: Bill Hoffman <bill.hoff...@kitware.com>
AuthorDate: Thu Sep 10 17:12:41 2015 -0400
Commit: Bill Hoffman <bill.hoff...@kitware.com>
CommitDate: Thu Sep 10 17:12:41 2015 -0400

Fix autoexport feature for 64 bit Windows builds by not removing leading _

With 64 bit windows builds, there is no need to remove the leading
underscore from all the symbols.  This is because it does not have
one in the .obj file unless it is really in the name.  This did
not cause any trouble until VS 2015 which has some system functions
that have a leading underscore that end up in the .def file.

diff --git a/Source/bindexplib.cxx b/Source/bindexplib.cxx
index 11e3f34..dc4db63 100644
--- a/Source/bindexplib.cxx
+++ b/Source/bindexplib.cxx
@@ -173,7 +173,7 @@ public:
*/
 
DumpSymbols(ObjectHeaderType* ih,
-   FILE* fout) {
+   FILE* fout, bool is64) {
   this->ObjectImageHeader = ih;
   this->SymbolTable = (SymbolTableType*)
   ((DWORD_PTR)this->ObjectImageHeader
@@ -183,6 +183,7 @@ public:
 GetSectionHeaderOffset(this->ObjectImageHeader);
   this->ImportFlag = true;
   this->SymbolCount = this->ObjectImageHeader->NumberOfSymbols;
+  this->Is64Bit = is64;
}
 
   /*
@@ -287,7 +288,14 @@ public:
   symbol.erase(posAt);
}
 }
-if (symbol[0] == '_') symbol.erase(0,1);
+// For 64 bit builds we don't need to remove _
+if(!this->Is64Bit)
+  {
+  if (symbol[0] == '_')
+{
+symbol.erase(0,1);
+}
+  }
 if (this->ImportFlag) {
this->ImportFlag = false;
fprintf(this->FileOut,"EXPORTS \n");
@@ -355,6 +363,7 @@ private:
   PIMAGE_SECTION_HEADER SectionHeaders;
   ObjectHeaderType* ObjectImageHeader;
   SymbolTableType*  SymbolTable;
+  bool Is64Bit;
 };
 
 bool
@@ -406,7 +415,8 @@ DumpFile(const char* filename, FILE *fout)
   * and IMAGE_FILE_HEADER.SizeOfOptionalHeader == 0;
   */
   DumpSymbols<IMAGE_FILE_HEADER, IMAGE_SYMBOL>
-symbolDumper((PIMAGE_FILE_HEADER) lpFileBase, fout);
+symbolDumper((PIMAGE_FILE_HEADER) lpFileBase, fout,
+ (dosHeader->e_magic == IMAGE_FILE_MACHINE_AMD64));
   symbolDumper.DumpObjFile();
} else {
   // check for /bigobj format
@@ -414,7 +424,8 @@ DumpFile(const char* filename, FILE *fout)
 (cmANON_OBJECT_HEADER_BIGOBJ*) lpFileBase;
   if(h->Sig1 == 0x0 && h->Sig2 == 0x) {
  DumpSymbols<cmANON_OBJECT_HEADER_BIGOBJ, cmIMAGE_SYMBOL_EX>
-   symbolDumper((cmANON_OBJECT_HEADER_BIGOBJ*) lpFileBase, fout);
+   symbolDumper((cmANON_OBJECT_HEADER_BIGOBJ*) lpFileBase, fout,
+(dosHeader->e_magic == IMAGE_FILE_MACHINE_AMD64));
  symbolDumper.DumpObjFile();
   } else {
  printf("unrecognized file format in '%s'\n", filename);

---

Summary of changes:
 Source/bindexplib.cxx |   19 +++
 1 file changed, 15 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

Re: [CMake] CMake on OpenVMS (some clarification)

[Bill Hoffman]

On 9/4/2015 9:42 AM, Custin, Jay (CSC Sw Middleware) wrote:

While I specifically want this on OpenVMS/Integrity (V8.3 or higher), I
have not tried this on an Alpha yet (vast majority of the coding/builds
I do involve the Integrity platform).  It took some manual editing of
files, etc. to get this far:

<>

CXX has ios::binary openmode

-

CXX -I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk -I/PRJ_ROOT/CMAKE-3_3_1/Source
-I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk -c /PRJ_ROOT/CMAKE

-3_3_1/Source/cmake.cxx -o cmake.o

#ifndef cmIML_ABI_H

.^

%CXX-E-MISSINGENDIF, the #endif for this directive is missing

at line number 33 in file LCL_ROOT:[cmake-3_3_1.Bootstrap_cmk.cmIML]ABI.h;4

cmIML_INT__VERIFY_TYPE(cmIML_INT_intptr_t,  sizeof(void*));

^

%CXX-E-NOTCOMPREDEC, declaration is incompatible with

   "int (*cmIML_INT_intptr_t__VERIFY__)[4U]" (declared at line 839)

at line number 839 in file
LCL_ROOT:[cmake-3_3_1.Bootstrap_cmk.cmIML]INT.h;23

<

I have the GNU Not VMS (GNV) Bash environment with the latest code base
for GNV (including Perl 5.22) and CMake (3.3.1).

I worked on this years ago.  I did manage to get most of it working, but 
no one ever setup a dashboard for it, so I am sure it fails now.   If 
you do manage to get it working it would be great if you could run a 
nightly dashboard... :)


-Bill


--

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

Re: [CMake] Patch on Windows?

[Bill Hoffman]

On 9/1/2015 11:51 AM, Macumber, Daniel wrote:

There was a thread back in January of 2014 about “It would be great if
CMake implemented a "cmake -E patch".”.  This feature would really help
us out, especially since the patch tool was removed from the Git for
Windows distribution (I have no idea why).  Did anything ever happen
with this request?


Would be a great contribution but I don't think there is a compatible 
license patch library that is around.  I have looked in the past.  This 
one requires Qt:


https://github.com/arrbee/google-diff-match-patch/blob/master/cpp/diff_match_patch.h

-Bill

--

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

[CMake] Happy Birthday CMake!

[Bill Hoffman]

Today is the 15th birthday of CMake:

http://www.kitware.com/blog/home/post/959

Thanks to everyone that has used and contributed to CMake over the years!

-Bill
--

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

[cmake-developers] Happy Birthday CMake!

[Bill Hoffman]

Today is the 15th birthday of CMake:

http://www.kitware.com/blog/home/post/959

Thanks to everyone that has used and contributed to CMake over the years!

-Bill
--

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] Prefix header for Makefiles

[Bill Hoffman]

CMake does not really support this.  At build time CMake scans the 
source files and builds the depend list.  Since your file is not 
actually included it does not end up in the depend list.  To add this as 
a feature you would have to put the information into DependInfo.cmake 
and have cmDependsC.cxx read the information.  If you are interested, I 
would suggest you come up with a patch and post it to the 
cmake-developer mailing list.  You could also try the ninja generator as 
it uses the compiler to compute depends and should have the correct 
information.


-Bill

--

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

Re: [CMake] [cmake-developers] CMake IR

[Bill Hoffman]

On 7/31/2015 12:33 PM, Ruslan Baratov wrote:

  rm -rf _builds
  cmake -H. -B_builds
  cmake -H. -B_builds -DA=ON
  grep '\B\' _builds/CMakeCache.txt
 B:STRING=There is no A

I'm not saying cache is a bad idea, I'm just saying that when users hit
such kind of situations that's one of the reason why they said CMake is
not a good script language. Just like CMake before CMP0054: user see
`if(a STREQUAL b)` and think okay, 'a' is not equal to 'b' so this
condition is always false... nope!
OK, it is a bit confusing.  One solution would be to treat the cache 
variables with some sort of separate look up.  Basically put all cache 
stuff into its own namespace.


Something like:
$CACHE{A}

Then, it would never be confused with the the variable A.  However, 
getting rid of the cache would not be something that could be done.


-Bill
--

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

Re: [CMake] CMake finds wrong ar/ranlib/nm

[Bill Hoffman]

On 7/30/2015 3:17 AM, Auer, Jens wrote:

Thanks a lot. Obviously, setting the environment when calling cmake
is not enough. The command scl enable devtoolset-3 cmake ../src
sets the path etc and runs the cmake command, but it seems that cmake
opens a new subshell with default settings. I've added the settings
to .bashrc and it now finds the correct ar/ranlib etc.
I don't believe it.  CMake does not open a new shell, something else is 
going on.  Sounds like you have other system problems to deal with.


-Bill



--

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

Re: [CMake] CMake IR

[Bill Hoffman]

On 7/30/2015 7:51 AM, Nagy-Egri Máté Ferenc via CMake wrote:

Bill:

I am a member, I just tried sending using the same mail using
the “secret CC” option. It seems it did not work.


OK, I just checked and it was rejected because of this:

Reason: Message has implicit destination

I have approved it, but if you could send directly to the list that 
would be better as I don't look at the rejected posts that often.


-Bill
--

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

Re: [CMake] [cmake-developers] CMake IR

[Bill Hoffman]

On 7/30/2015 10:48 AM, Dan Kegel wrote:

I wouldn't mind getting rid of the cache, it's a bizarre concept that appears
to be a workaround for users who can't stand starting cmake from a script,
and it complicates my cmake scripts, but that's not a battle I'd like to wage.
No, it is how CMake stores things it finds during the configure step. 
If you did not have it you would have to rediscover everything for every 
run on a build tree, and have no place to store user selections in the 
GUI.


-Bill

--

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

Re: [CMake] [cmake-developers] CMake IR

[Bill Hoffman]

On 7/30/2015 11:56 AM, Dan Kegel wrote:

I believe the latter, but not the former.
I never use the GUI, and consider the cache an anti-feature there solely
to support GUI users.  It complicates my life, and I'd love to see it go.
It is certainly not there just for the GUI.  Every try-compile, 
find_library, find_program result is stored there as well.  If you did 
this each time, it would be not only slow to re-run a build, but it 
might come up with different answers each time.   If it went it would 
complicate your life even more.   In what way do you think it is causing 
you trouble?


Also, CMake needs to be able to auto-rerun when its input changes and 
this is how the command line -D options are saved along with all the 
other system introspection results.


-Bill

--

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

Re: [CMake] CMake IR

[Bill Hoffman]

On 7/29/2015 9:11 AM, Nagy-Egri Máté Ferenc via CMake wrote:

I also posted this idea to the dev list at the same time, but it’s
awaiting moderation due to the inserted links.

We really do not moderate the lists like that.  If it is pending it is 
because you are not a member of the list.  So, you should become a member:

http://www.cmake.org/mailman/listinfo/cmake-developers

Then repost.

-Bill

--

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

Re: [cmake-developers] Modules/GetPrequisites.cmake issues

[Bill Hoffman]

On 7/29/2015 10:17 AM, Bill Somerville wrote:

Is there a reason not to look for objdump before dumpbin?

I was under the impression that dumpbin was selected first for non-MinGW
Windows builds, I have no idea if objdump works with binaries produced
by compilers other than GNU/CLang. This is why I commented about
detecting MinGW, there are mentions of a MINGW CMake system variable but
it doesn't seem to exist.
Yes, that is the problem.  This is  a standalone script that is run at 
install time, so it does not have any information about the build 
toolchain. In retrospect it should have been passed more information 
about the build tool chain that was used.


This is what we want:

#dumpbin (Windows)
#objdump (MinGW on Windows)
#ldd (Linux/Unix)
#otool (Mac OSX)

Trouble is dumpbin and objdump might both be in the PATH on Windows. 
You don't really know which one to use. I wonder if you found both 
if you could call something on each of them with one of the binaries, if 
you could figure out what tool would work better with it.


-Bill
--

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