[Ardour-Users] building ardour 3 on macOSX ?

Robin Gareus robin at gareus.org
Thu Jan 13 09:36:19 PST 2011


IIRC the -L$HOME/gtk/inst/lib/ was only needed to make waf happy (when
it tries to compile some tests).

I dunno why I need the '-I/usr/include/libxml2'. There's actually a
/usr/lib/pkgconfig/libxml-2.0.pc which points to that folder.

It could be an ordering issue: the arch-flags come before the CFLAGS;
and /Developer/SDKs/MacOSX10.5.sdk/usr/include/libxml2 is not compatible
or something.

robin

On 01/13/2011 06:23 PM, Thomas Vecchione wrote:
> Hmm I wonder if that is the catch then.  I need to check and see what
> the defaults are when no flags are passed, that may be the difference
> between your build and others(There are a few flags that were standard
> on OS X, that may not being compiled now that might explain it).
> 
>     Seablade
> 
> On Thu, Jan 13, 2011 at 12:19 PM, Robin Gareus <robin at gareus.org> wrote:
>> On 01/13/2011 05:53 PM, Thomas Vecchione wrote:
>>
>>> Out of curiosity, what WAF flags did you use to compile the version of
>>> Ardour you have, and not that it should make a difference, but did you
>>> patch it with Paul's patches or no?
>>>
>>>     Seablade
>>
>> pretty much none. I abused the "--arch" option to pass along some extra
>> flags because somehow pkg-config did not do it.
>>
>> PKG_CONFIG_PATH=$HOME/gtk/inst/lib/pkgconfig/:$PKG_CONFIG_PATH \
>> ./waf configure --arch="-L/Users/rgareus/gtk/inst/lib/
>> -I/usr/include/libxml2/ -arch i386 -arch ppc" --phone-home --videotimeline
>>
>> I may have set CFLAGS and CXXFLAGS to "-isysroot
>> /Developer/SDKs/MacOSX10.5.sdk -mmacosx-version-min=10.5" but I can't
>> see that in the build/config.log now.
>>
>> robin
>>



More information about the Ardour-Users mailing list