Re: Ardour3 waf build sysẗem and *FLAGS

Thomas Nagy tnagy1024 at gmail.com
Wed Sep 25 19:21:03 UTC 2013


On Wed, Sep 25, 2013 at 9:03 PM, Felipe Sateler wrote:
>
> Hi Thomas,
>
> On Wed, Sep 25, 2013 at 1:42 PM, Thomas Nagy <tnagy1024 at gmail.com> wrote:
> > Waf by default does accept CFLAGS and CXXFLAGS, and in all versions.
> >
> > There might be something in the Ardour3 project preventing that. Do you have
> > any url for the source code and in particular for the wscript file?
>
> Here is the wscript file[1]
>
> Paul Davis[2] noted that --optimize seems to enable waf to pick up the
> C*FLAGS variables. Is this intended behavior, or possibly something in
> the wscript is triggering this?
>

The Ardour wscript file loads an Ardour helper module called
"autowaf.py". This module will force specific CFLAGS/CXXFLAGS in the
default build. If I am not mistaken, the default build is intended as
a debug build and will enforce its own flags.

This is therefore an Ardour-specific trap, and you almost certainly
want to configure Ardour with "--optimize" for packaging purposes.

Regards,
Thomas



More information about the pkg-multimedia-maintainers mailing list