Changes between Initial Version and Version 1 of Ticket #40648
- Timestamp:
- Oct 1, 2013, 9:50:59 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #40648
- Property Keywords optimization release removed
- Property Owner changed from macports-tickets@… to css@…
-
Ticket #40648 – Description
initial v1 1 1 Recently, projects generated with CMake as installed from MacPorts stopped getting optimization flags set in Release mode. 2 2 3 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.3 This appears to be caused by r110069 wherein the Portfile was configured to explicitly strip -O3 from the compiler modules shipped with CMake. 4 4 5 5 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.