[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
handling of -framework in .la's?
From: |
Benjamin Reed |
Subject: |
handling of -framework in .la's? |
Date: |
Mon, 11 Aug 2003 14:43:14 -0400 |
I'm not sure how to go about fixing this, but I'm running into an issue
in trying to build KDE from CVS against Qt/Mac 3.2.0. The problem is,
Qt 3.2 now creates a .la file, which contains -framework lines like so:
---(snip!)---
# libqt-mt.la - a libtool library file
# Generated by qmake/libtool (1.06c) (Qt 3.2.0) on: Sun Aug 10 21:14:53
2003
# The name that we can dlopen(3).
dlname='libqt-mt.3.dylib'
# Names of this library.
library_names='libqt-mt.3.2.0.dylib libqt-mt.3.dylib libqt-mt.dylib'
# The name of the static archive.
old_library='libqt-mt.a'
# Libraries that this one depends upon.
dependency_libs='-framework Carbon -framework QuickTime -lresolv -lz
-framework OpenGL -framework AGL'
# Version information for libqt-mt
current=32
age=0
revision=0
# Is this an already installed library.
installed=yes
# Files to dlopen/dlpreopen.
dlopen=''
dlpreopen=''
# Directory that this library needs to be installed in:
libdir='/opt/local/lib'
---(snip!)---
...then, while building with --debug, it dies like so:
---(snip!)---
+ deplibs=AGL -framework OpenGL -framework -lz -lresolv QuickTime
-framework Carbon -framework /opt/local/lib/libqt-mt.la -ldl
/usr/lib//libiconv.la /usr/lib/libiconv.la /usr/lib/libiconv.la
-L/opt/local/lib /opt/local/lib/libintl.la /usr/lib/libiconv.la
/opt/local/lib/libintl.la -L/opt/local/lib
/opt/local/lib/libglib-2.0.la /usr/lib/libiconv.la
/opt/local/lib/libintl.la /opt/local/lib/libglib-2.0.la
-L/opt/local/lib /opt/local/lib/libgthread-2.0.la /usr/lib/libiconv.la
/opt/local/lib/libintl.la /opt/local/lib/libglib-2.0.la
-L/opt/local/lib /opt/local/lib/libgmodule-2.0.la -ldl
/usr/lib//libiconv.la /usr/lib/libiconv.la /opt/local/lib/libintl.la
/opt/local/lib/libglib-2.0.la /opt/local/lib/libgthread-2.0.la
/opt/local/lib/libgmodule-2.0.la -L/opt/local/lib -L/usr/X11R6/lib
../mcop/libmcop.la -L/opt/local/lib -L/usr/X11R6/lib
+ test X = Xyes
+ tmp_libs= -framework Carbon -framework QuickTime -lresolv -lz
-framework OpenGL -framework AGL
+ continue
+ lib=
+ found=no
+ test no = yes
+ test -f ''
+ echo 'libtool: link: cannot find the library `'\'''
libtool: link: cannot find the library `'
+ exit 1
make[2]: *** [libqtmcop.la.closure] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
---(snip!)---
At this time, "$deplib" is set to "Carbon", so clearly it's considering
"-framework" and "Carbon" as 2 different "libraries". Changing them to
use -Xlinker or -Wl, has no effect, it still bombs with the same
complaint.
Any ideas how to handle this?
--
We put a lot of thought into our defaults. We like them. If we
didn't, we would have made something else be the default. So keep
your cotton-pickin' hands off our defaults. Don't touch. Consider
them mandatory. "Mandatory defaults" has a nice ring to it.
- handling of -framework in .la's?,
Benjamin Reed <=