#50246: CMake PortGroup : generate a file in ${workpath} containing the complete cmake invocation --------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by michaelld@…): I'd love to see this feature in base, somehow: a single command including environment variables for how to do the configure stage. Given the ever growing number of projects using cmake, I think doing it with just cmake would be fine as a test to see about the usefulness of storing this info. Storing the configure phase environment and command are generally more useful that those for build or destroot since the latter 2 are generally just "make" and "make install". Not always, of course. So, if we're talking about storing 1 phase's info then I'd say to just store all phase's info if it's that simple. cmake does actually store it's original command line internal to the build (somewhere; I don't remember) such that if one of the cmake build files is updated (even just touched) then cmake will try to re-run itself (sort of a re-configure). But, it doesn't store the shell environment so the results from re-configuration might vary from the original configuration stage. -- Ticket URL: <https://trac.macports.org/ticket/50246#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X