Finding out how "cmake" was run

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Finding out how "cmake" was run

Rob Boehne

All,

 

Is there some place where the command that cmake was run with gets stored?

GNU Autoconf projects write a config.log file, who’s first line is the command that was used to configure the project.

So when I go back later and try to pick up where I left off, it’s fairly easy –

I run “head config.log”  and I see what I had configured to build in that directory.

 

 

cid:image002.png@01D3D0E3.DCFE6710

Rob Boehne

Senior Software Architect | Datalogics, Inc.

<a href="tel:(312)%20853-8351">+1.312.853.8351 | [hidden email]

datalogics.com | blogs.datalogics.com

Connect with us: Facebook | Twitter | LinkedIn | YouTube

 

 


--

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
Reply | Threaded
Open this post in threaded view
|

Re: Finding out how "cmake" was run

Jean-Michaël Celerier

CMakeCache.txt has all these infos

On 31/10/2018 14:55, Rob Boehne wrote:

All,

 

Is there some place where the command that cmake was run with gets stored?

GNU Autoconf projects write a config.log file, who’s first line is the command that was used to configure the project.

So when I go back later and try to pick up where I left off, it’s fairly easy –

I run “head config.log”  and I see what I had configured to build in that directory.

 

 

cid:image002.png@01D3D0E3.DCFE6710

Rob Boehne

Senior Software Architect | Datalogics, Inc.

<a href="tel:(312)%20853-8351" moz-do-not-send="true">+1.312.853.8351 | [hidden email]

datalogics.com | blogs.datalogics.com

Connect with us: Facebook | Twitter | LinkedIn | YouTube

 

 



--

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
Reply | Threaded
Open this post in threaded view
|

Re: Finding out how "cmake" was run

Ian Cullen
Looks like someone had a similar idea to you a few days ago - https://gitlab.kitware.com/cmake/cmake/issues/18505

Also discussed previously:
https://gitlab.kitware.com/cmake/cmake/issues/14756
https://gitlab.kitware.com/cmake/cmake/issues/16833



On 31/10/2018 14:03, Jean-Michaël Celerier wrote:

CMakeCache.txt has all these infos

On 31/10/2018 14:55, Rob Boehne wrote:

All,

 

Is there some place where the command that cmake was run with gets stored?

GNU Autoconf projects write a config.log file, who’s first line is the command that was used to configure the project.

So when I go back later and try to pick up where I left off, it’s fairly easy –

I run “head config.log”  and I see what I had configured to build in that directory.

 

 

cid:image002.png@01D3D0E3.DCFE6710

Rob Boehne

Senior Software Architect | Datalogics, Inc.

<a href="tel:(312)%20853-8351" moz-do-not-send="true">+1.312.853.8351 | [hidden email]

datalogics.com | blogs.datalogics.com

Connect with us: Facebook | Twitter | LinkedIn | YouTube

 

 





--

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
Reply | Threaded
Open this post in threaded view
|

Re: Finding out how "cmake" was run

Alan W. Irwin-2
On 2018-10-31 14:17-0000 Ian Cullen wrote:

> Looks like someone had a similar idea to you a few days ago -
> https://gitlab.kitware.com/cmake/cmake/issues/18505
>
> Also discussed previously:
> https://gitlab.kitware.com/cmake/cmake/issues/14756
> https://gitlab.kitware.com/cmake/cmake/issues/16833

In addition I requested something like this roughly a decade ago although
it has likely not propagated all the way from the bug tracker back then
to this latest generation of the bug tracker.

I think simply reporting back most cmake arguments specified on the
command line is completely straightforward, i.e., what is
reported back would simply be a list of all cmake arguments that were
specified by the user.  But the -D subset of the arguments are a special case
because there are cache complications.

For that subset what is useful to me is what was requested in 14756, i.e.,
give the user a minimal set of cmake arguments that allow them to
reproduce the build starting from an empty build tree.  (For example,
if the user specified a -D value which happened to be the default presented
by the option command, this unnecessary -D value
would be dropped from this minimal list.)  I guess 16833 (which asked
just for whatever the last set of cmake options were regardless of
cache state) might have a use case as well, but in the discussion
there the requester finally decided that 14756 would satisfy his
needs.

In sum, it would be great from my perspective if the "reproduce the
build from empty build-tree case" use case presented in 14756 (and also very long ago by me) was
finally addressed.

Alan
__________________________
Alan W. Irwin

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________
--

Powered by www.kitware.com

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