On 23.02.2011 18:53, Manolo Gouy wrote:
> Not propagating archflags to "fltk-config --cflags" is convenient
> when one wants to build a native appl using universal libraries,
> but is a nuisance in another scenario:
> I am on Mac OS X 10.6 and want to build 32-bit applications
> (because I know 64-bit is useless unless the appl uses more
> than 4GB of memory).
> Here, I would be happy to have archflags propagated from
> the library to the application builds.
In your scenario, wouldn't it be possible that the library uses
different archflags when building it ("universal" or whatever[1]),
and your app needs other flags (as you described)? In this case
I *believe* [1] that the library shouldn't set any archflags, as
the OP requested, and it should be the responsibility of the app's
Makefile to set the appropriate archflags for the app.
-----
[1] Disclaimer: I don't know enough about OS X build flags to be sure
here, I'm just /thinking/ loud.
Albrecht
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
