On Apr 28, 2015, at 11:39 PM, Mihai Moldovan wrote: > On 14.04.2015 07:44 AM, Mojca Miklavec wrote: >> Could something like that be added to the compiler_blacklist >> PortGroup? I believe that pure C++11 projects need consistent handling >> and it would be very handy to allow a keyword like "compiler.c++11" or >> "compiler.<something> c++11" to replace all of the logic above inside >> a port. > > I've now added a new PortGroup called cxx11, which does the blacklisting and > stdlib checking.
Thanks. That was my first thought as well... but what happens next when ports want to require C++14, or some other future standard? Should it be able to accommodate that as well? > Extending compiler_blacklist_versions looked too complicated, as its logic is > contained in multiple procs and one option_proc. Right, I would not add this to that portgroup; it is a different concept. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
