Re: API freeze release ... status so far.

Bastien Nocera <hadess hadess net> writes: 
> I think one should read "Architecture independant" as "if it's not an executable
> and it isn't compiled for a specific architecture"
> If what you're telling me is that there might be a .pc for a library available one
> arch, and not for the other, I could argue that the same problem would happen if 2
> versions of one application have different layouts under their
> /usr/share/application dir (and different versions are available on the platforms),
> or if a bonobo component is available on one platform and not the other
> (/usr/share/oaf)

The point is that you can have arch-specific compiler flags or the
like in the .pc files. So you may need a different .pc file for each

/usr/lib/glib/include/glibconfig.h is a similar example.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]