The "-isysroot /Developer/SDKs/MacOSX10.4u.sdk" switch replace GCC's
build-in search-path (e.g. /usr/{lib, include} /usr/local/{lib,include},
and "-arch xyz" sets back-end code generation.
___
http://lists.gnu.org/mailman/listinfo/libtool
Perrog wrote:
> Has anyone been using libtool for universal binary builds on Mach-O/Mac OS
> X?
I know a couple of users have tried that with my library libsndfile.
> Are there any other platform that have similar requirements?
Not that I know of.
> Or should universal builds be handled by oth
Hi!
Has anyone been using libtool for universal binary builds on Mach-O/Mac OS
X? Are there any other platform that have similar requirements? In summary,
an "universal build" is a Mach-O object or binary file format containing
both PowerPC and Intel architectures, in an architecture independend
Hi together!
I have a question regarding relinking on windows (while installing).
Everytime a library/exe is installed it is relinked, which costs tons of
time.
After thinking about the problem of having to relink (i assume because
of changing runpaths?) i realized that a Makefile target (pointin
On May 11, 2007, at 4:45 AM, Perrog wrote:
Hi!
Has anyone been using libtool for universal binary builds on Mach-O/
Mac OS X? Are there any other platform that have similar
requirements? In summary, an "universal build" is a Mach-O object
or binary file format containing both PowerPC and
Hello Arto,
* [EMAIL PROTECTED] wrote on Wed, May 09, 2007 at 11:50:10AM CEST:
>
[...]
> ...
> gmake[4]: Entering directory
> `/build/libtool-1.5.22_static-obj9_g412-b2175020070420-O2-mcpu=supersparc/depdemo'
> gcc -DPACKAGE_NAME=\"depdemo\" -DPACKAGE_TARNAME=\"depdemo\"
> -DPACKAGE_VERSION=\"0
