[MacPorts] #40648: cmake @2.8.11.2 does not set optimization flags in release
MacPorts
noreply at macports.org
Tue Oct 1 14:38:48 PDT 2013
#40648: cmake @2.8.11.2 does not set optimization flags in release
----------------------------------+--------------------------------
Reporter: macports@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: optimization release | Port: cmake
----------------------------------+--------------------------------
Recently, projects generated with CMake as installed from MacPorts stopped
getting optimization flags set in Release mode.
This appears to be caused by
https://trac.macports.org/browser/trunk/dports/devel/cmake/Portfile?rev=110069
wherein the Portfile was configured to explicitly strip -O3 from the
compiler modules shipped with CMake.
While it may well be true that when CMake is used to generate makefiles
for a port, one should not set an optimization flag (I don't know), it
does not seem to be the correct behavior for any non-MacPorts project that
is using CMake installed by MacPorts. This seems to me to be a pretty
standard use case- it's certainly what my team has been doing. This change
makes it impossible to make a release build of software without additional
hackery to force the optimization flag back in.
I'm not sure what the correct solution is. I'm hoping someone with a
deeper knowledge has some ideas?
--
Ticket URL: <https://trac.macports.org/ticket/40648>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list