On Mar 27, 2018, at 09:43, Benjamin Redelings wrote:
> Following on to this question, how does a port require a c++ compiler that
> supports c++14?
>
> Currently, in science/bali-phy I use the following, which is similar to
> editors/textmate2 and games/gdash.
>
> # Needs support for
On 2018-03-27, at 7:43 AM, Benjamin Redelings wrote:
> I suppose there could be a c++14 portgroup?
There could be.
But I would instead propose that MacPorts never puts forward a compiler that
can't handle c++14 at this point in time instead.
If the system-installed clang is new enough to
Following on to this question, how does a port require a c++ compiler
that supports c++14?
Currently, in science/bali-phy I use the following, which is similar to
editors/textmate2 and games/gdash.
# Needs support for -std=c++14.
compiler.blacklist {clang < 602}
I see that gdash uses
On Mar 27, 2018, at 06:41, Mojca Miklavec wrote:
> On 27 March 2018 at 08:31, Ryan Schmidt wrote:
>>
>>> On Mar 26, 2018, at 01:25, Mojca Miklavec wrote:
On 26 March 2018 at 02:49, Ryan Schmidt wrote:
> On Mar 25, 2018, at 14:37, David B. Evans wrote:
>
>> +# blacklist
u proposing that the names "gcc" and "macports-clang" be
special-cased in the portgroup, and taken to mean "the set of ports whose names
start with 'gcc'" (or maybe even "...whose names contain 'gcc'"?) and "the set
of ports whose names start with 'macports-clan
I think blacklisting *gcc-4* would achieve the desired goal.
gcc-3.x is no longer a compiler macports puts forward for use, so can be
ignored now.
K
> On Mar 26, 2018, at 01:25, Mojca Miklavec <mo...@macports.org> wrote:
>
>> On 26 March 2018 at 02:49, Ryan Schmidt wrote:
&
