| Re: [proaudio] [2628] Guitarix2: Added custom-cflags and debug USE flags |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] [2628] Guitarix2: Added custom-cflags and debug USE flags
- From: Dominique Michel <dominique.michel@xxxxxxxxx>
- Date: Mon, 1 Apr 2013 00:05:51 +0200
- Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEXy8ubtkoXo7+b1+fbN cGKCeWDtamweFA8eMkmKPkPtvcWRoqyV0Pn7AAACbElEQVQ4jXXTMWvbQBQA4MOlizsdXEXp KAi09mKcLZ0EJxONDRJVkikg9AtqTm63gtHDmVJs1GsnC0JiaTMJGN2f67uzznJb+gZj9PFO 7717IqdtvCAmem4bxMLp/2BEyEBF1+U/0H8uhI6rv+BVLNrY/gH9T0L8yAxk2yMY3YuZxDCn TY/gpBByyTGktIcZOIvFjPNJmqYJDwrx3cIoBrE0zzG4FF8tfBAwM+DonKCYWjgROZ6Upjcm 5Qje58JAmlKKGfIAjzaDUuogZBY2Bjg14eDbywMIqZvwqgqFBcVFB0seYONLb00ZZlh4p0F6 FHNoUMyKAzxowJSQTyj+XloYs3MN3GeMpzyYSTMshLM00ODpWlPp4SDbqs4cViDcGAgmlK/a PsaOg7DvIQ3wzANMqB/iQW/XTkoTLO6XhSeHUoQKe+NLjyY/Ldx7CW2D4WTYhZ3V0GP64RpP Q/E66IUWMLj3+nDn4w2ejMACyXFeHZy6ETcZehc49bv1GQ/0bazNuzm97mDkhnoie9i30WYM w/YCnYT7Fx308s98n0IT//Jod1+aOzdzYXLVbftol+PC+REG3u+0AxdEtuSMB6G+DLGwMH4E vXGmJn8VCLM9LhmrOAMQYt5Wi/DFgIC52iFkUzMpDVmjAaDZRGC+JGwDqzJ/G5fUUcWZAaE7 YfvPLYtIU1Wb4A2IeS7uDMgcIFutiCr766qGfKHyuxvTIERKXVNSN27lDgCuBuojlpxIyJV6 ritS1uWWuHF2Ww7qcIKbqEFVNbmtmm3vGSCHbVXjikrY3SpVxwQWw2aIjwG+ueXTJDmHeK6a HfwGyU5ZSlGeSRQAAAAASUVORK5CYII=
Le Sun, 31 Mar 2013 23:44:44 +0200,
Karl Lindén <spray.sucks@xxxxxxxxx> a écrit :
Other packages are working that way with that flag. It was a long time
ago, I get very confused by that.
Dominique
> Alright, please do so if you feel like it.
>
> 2013/3/31 Dominique Michel <dominique.michel@xxxxxxxxx>:
> > Le Sun, 31 Mar 2013 22:04:20 +0200,
> > Karl Lindén <spray.sucks@xxxxxxxxx> a écrit :
> >
> >> Oh, if you decide to change it, it should probably renamed as
> >> custom-cflags is not turned on by default and I think the default
> >> behaviour should be respecting CFLAGS. What do you think?
> >>
> >> Karl
> >>
> >> 2013/3/31 Karl Lindén <spray.sucks@xxxxxxxxx>:
> >> > Enabling custom-cflags will enables the wscript enforced flags?
> >> > According to use.desc "custom-cflags - Build with user-specified
> >> > CFLAGS (unsupported)" so I think it should just be the other way
> >> > araound.
> >
> > It is like it work. -custom-cflags (the default in portage) will use
> > the system cflags. custom-cflags will add the flags upsrteam flags.
> >
> > I can add some description into metadata.xml
> >
> >> >
> >> > Karl
> >> >
> >> > 2013/3/31 <subversion@xxxxxxxxxxxxx>:
> >> >> Revision: 2628
> >> >> Author: dominique
> >> >> Date: 2013-03-31 21:33:47 +0200 (Sun, 31 Mar 2013)
> >> >> Log Message:
> >> >> -----------
> >> >> Guitarix2: Added custom-cflags and debug USE flags
> >> >>
> >> >> Modified Paths:
> >> >> --------------
> >> >> trunk/overlays/proaudio/media-sound/guitarix2/ChangeLog
> >> >> trunk/overlays/proaudio/media-sound/guitarix2/Manifest
> >> >> trunk/overlays/proaudio/media-sound/guitarix2/guitarix2-0.25.2.ebuild
> >> >> trunk/overlays/proaudio/media-sound/guitarix2/guitarix2-9999.ebuild
> >> >>
> >>
> >>
> >
> >
> > --
> > "We have the heroes we deserve."
> >
> >
>
>
--
"We have the heroes we deserve."