On Aug 30, 2012, at 16:13 18, WBHM Web Operations wrote:
> ls -l /opt/local/lib | grep QtCore
> -rwxr-xr-x 1 root admin 3433260 Apr 28 10:26 libQtCore.4.8.0.dylib
> lrwxr-xr-x 1 root admin 21 Apr 28 10:26 libQtCore.4.8.dylib ->
> libQtCore.4.8.0.dylib
> lrwxr-xr-x 1 root admin 21 Apr 28 10:26 libQtCore.4.dylib ->
> libQtCore.4.8.0.dylib
> lrwxr-xr-x 1 root admin 21 Apr 28 10:26 libQtCore.dylib ->
> libQtCore.4.8.0.dylib
> -rw-r--r-- 1 root admin 657 Apr 28 10:26 libQtCore.la
> -rw-r--r-- 1 root admin 984 Apr 28 10:28 libQtCore.prl
>
> I'm using the configure as follows:
>
> ./configure CPPFLAGS=-I/opt/local/lib/
The -I flag is for providing a path to header files. You want -L for giving a
path to the libraries themselves. Try something like:
./configure CPPFLAGS=-L/opt/local/lib -I<path-to-include-headers>
You'll need to be doing something similar for each dependency as well. See
'INSTALL' in the sources for a list. I've found that building each dependency
from source and then doing 'sudo make install' puts it in a place where it gets
found by default without having to futz around with the environment. Good
enough for alpha development, but will likely need some major rework when the
time comes to build proper app bundles -- DLL library management on OS X is
*very* different from Linux! One thing at a time though -- let's learn to walk
before we try a hundred meter dash... :)
Cheers!
|-------------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Chief Developer |
| | Paravel Systems |
|-------------------------------------------------------------------------|
| At the beginning of the week, we sealed ten BSD programmers into a |
| computer room with a single distribution of BSD Unix. Upon opening |
| the room after seven days, we found all ten programmers dead, |
| clutching each others' throats, and thirteen new flavors of BSD. |
| -- Anonymous |
|-------------------------------------------------------------------------|
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
