Le Sun, 31 Mar 2013 22:04:20 +0200, Karl Lindén <[email protected]> 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 <[email protected]>: > > 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 <[email protected]>: > >> 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."
