Re: [Sooc-devel] Addendum

[Mike R. <mik...@gm...>]

On Fri, Aug 1, 2008 at 1:04 AM, Daniel Reinish <sta...@gm...> wrote:
> It's been a while since I've verified that Sooc compiles on OS X.
> In particular, I can't remember if it's even ever been tested on
> Leopard.  Considering that a number of things changed since 10.4,
> including full Unix certification, it will be interesting to see
> what sort of process is involved in getting things working out of
> the box.  In particular, I'm wondering what sort of tools and
> libraries still need to be obtained through sources like Fink
> (probably the same ones as always, including but not limited to the
> autotools).  I don't have access to the dev tools at the moment,
> since it's not worth installing them on my laptop.  But I will take
> a look at this some time soon when I set my desktop up again.

At some point, Sooc should be mature enough to start growing in scope.
That is, there should be Sooc interfaces for existing libraries.  Most
likely these will be built slowly and by demand.  In any case, I think
it'd be neat to set it up to configure those automatically.  That is,
the configure script should detect the presence of other libraries and
decide whether to build the wrapper interface intelligently.  Of
course, you should be able to explicitly disable these as well.
I've noticed that Pidgin does a good job of such automatic
configuration, so we can look at that when the time comes.

> When I do get a chance to do this, I think I will try to document,
> for the sake of having it out there, what exactly needs to be done
> to compile on OS X.  That is to say, exactly what needs to be
> downloaded, what settings need to be changed (if any), and so on?

To build Sooc, I think you just need a POSIX-compliant C library
including pthreads.  You may also need pkg-config, or you may only
need pkg-config if you want to use it later to compile and link more
easily against Sooc.

However, I think many systems need /usr/local/lib to be added to
/etc/ld.so.conf in order to start Sooc programs at runtime.  After
installing a new version (like a new release) of Sooc, you need to run

	sudo ldconfig

to make sure your linker knows what's happening.

Also, in order to use Sooc's pkg-config, I needed to make sure the
following was set:

	PKG_CONFIG_PATH="/usr/local/lib/pkgconfig"

In Gentoo, I just dropped that in /etc/env.d/999local-pkgconfig.  On
other systems, that goes in /etc/profile or somewhere...

These system-wide tweaks apply whenever you build your first
non-package-managed software installed to /usr/local.