Re: building on osx

I would do the following:

#1. Bundle SWIG with the src distribution and make it part of the build
process. It's under a BSD license so that is easily possible and the
tar.gz is only 2megs (.24 is 3megs).

Because SVN has specific version requirements for SWIG, it would be
easier for end users to just have SVN build SWIG for you (just like
with apr). 1.3.21 was released over a year ago and 1.3.24 is now a
couple of months old.

#2. I would consider putting a special case into the build system for
OSX to look for libs in "/sw" which is the default fink installation
path. libiconv is distributed with OSX by default, but for whatever
reason, the configure system finds the /sw version first but forgets to
add -L/sw/lib to the build.

#3. I would make SWIG_LDFLAGS settable from environment variables (and
not just after make) and I would make it default to inheriting the
LDFLAGS settings...or maybe just this is enough...

[4][ /usr/local/src/subversion/subversion-1.1.3 ]# diff build.conf.bak
build.conf
343c343
< link-cmd = $(LINK) $(SWIG_LDFLAGS) $(SWIG_PY_LIBS)

---
 > link-cmd = $(LINK) $(LDFLAGS) $(SWIG_LDFLAGS) $(SWIG_PY_LIBS)
If you don't want to do any of those changes, then my script will 
continue to work for people with similar configurations. =)
thanks!
jon
On Feb 5, 2005, at 3:04 PM, kfogel@collab.net wrote:
> Thanks!
>
> I don't run Mac OS X myself, so pardon me if these are dumb questions:
> is this patching over problems in our build system?  Or is it an
> improvement that could be incorporated into our build system?  Or
> should we just make this script available for people in certain
> specific situations?
>
> The subtext here is: I'm trying to figure out what's the right final
> destination for this work you've done, so the most people will
> benefit.  What's your recommendation?
>
> -Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org