-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Philip J. Schneider wrote:
Hi -
Gotta general question or three here...
Recently upgraded to Mac OS X 10.5.6, and in the process decided to nuke
my fink installation and start afresh (had fink 0.8x, now have 0.9), and
grabbed the openmotif and xemacs from there. I've also installed the
latest XQuartz. So far so good...
Ok, I don't use fink (MacPorts here), but I'll try to help.
Just tried to build an X application that I'd successfully built under
Tiger, the earlier fink, etc.
I'm missing libXt.a, libICE.a, and libSM.a.
Eeek. Why are you using or expecting static libs? You should be using
dynamic libs, so you don't need to rebuild your application to inherit
bugfixes from th elibs.
At this point, I can't tell
where, in my previous setup, these came from (at least not without
digging through a Retrospect archive).
The Tiger X11SDK provided static libs. That is no longer the case. You
need to be using the dylibs.
It doesn't appear that fink provides these, if it ever did, and the
XCode X11 dev package doesn't appear to install them either.
But, I see on
http://www.opensource.apple.com/darwinsource/10.5.6/X11libs-17.3/ that
all sorts of X11 libs are available as source, including of course the
ones I want. Not having ever downloaded/used any of the darwinsource
stuff, I don't know what the basic "protocol" is.
Looking at the Makefile in the above-named sources, it appears that one
could simply setenv DSTROOT and make them get installed in an arbitrary
location...hmm...
So (finally), here are the questions:
1. Is there a "standard default" location for installing stuff from
darwinsource? Or just a place that folks consider to be a
convention...Looks like a lot of useful stuff here, and I'd rather start
off putting them in some sort of "reasonable" place :-)
If you want to install your own bits, you should probably use /usr/local
or something similar.
2. Will fink X11 stuff (installs under /sw) conflict with darwinsource?
It shouldn't "conflict" but you may have some trouble convincing fink to
use your build instead of /usr/X11 ...
The thing is... you really shouldn't NEED to be doing this. There is
something wrong with fink or your installation. fink should not need
the static libs. It should use the dylibs.
My advice to you is MacPorts. Recently, I updated MacPorts to use its
own X11 SDK rather than the system X11, so it's consistent across
versions of OSX.
3. Is there a README/INSTALL file for installing darwinsource stuff that
I'm just missing or not aware of? Or a ./configure script?
I don't mean to come off as rude, but the darwinsource bits are the
wrong tree to bark up. Those are mainly provided, so you can see
exactly what source files went into darwin, but it doesn't really lend
itself to easy building for someone without access to our build system.
It's fairly straight forward if you want to do it... You can look at
the Makefile and figure out what environment variables and command line
options need to be set, but there is no documentation for that.
I went through the trouble of updating MacPorts to give people an easy
way to build X11. The versions in MacPorts correspond to the latest
releases of individual components, and the Portfile contains all the
information on how the port is built.
Still... if you are insistent on traveling down this cold, dark path,
then I will offer you some bits of advice.
The source you see are just unpacked tarballs from upstream with some
X11 patches applied (really a minimal number of patches... I think it's
now just 1 patch for Xt to not use poll()).
Each subdirectory contains the unpacked tarball and possibly a conf_args
file that says what extra ./configure arguments are used to build the
package.
Sorry to sound like a n00b - been programming X since the 1980's...just
not a lot of X11 on the Mac lately... :-) Answers can assume I have a
high level of X/Unix/programming/shell expertise..
Thanks!
You may also want to join the xquartz-dev list for more
developer-oriented assistance.
The main thing to figure out is why fink is needing the static libs
instead of the dynamic ones.
- --Jeremy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJ/2CZjC1Anjf1NmMRAiOrAJ9SMH38h8juQOFPBinqvWibeU+64ACdHQRn
a7+ebEPXECW3mmBAowkhmaw=
=Q1Xu
-----END PGP SIGNATURE-----