[fluxus] MacOS X

[Artem Baguinski]

Hi Dan

On 25 Feb 2006, at 02:46, Dan Bethell wrote:
> Hi artem,
>
> it was me who put together that binary - i detailed how here:
> http://www.pawfal.org/index.php?page=CompilingFluxusForMacOSX

AH! I heard that it was detailed on wiki, but I could find it back ;-)

Thanks

> I did get cvs access from dave but haven't got round to comitting the
> changes detailed on the page... lazy surf bum i am. Maybe between  
> us we
> can get them in?!

sure. to not break anything i split another branch - macos-scons  
where i adjust SConsctruct to build the bundle and then the diskimage.

I have committed the preliminary version form last night, it builds  
the bundle without guile files, (i still use 1.6.7., 1.8 gave too  
much errors when i tried and considering Dave thinks about switching  
schemes i couldn't be bothered yet), then creates the diskimage with  
the bundle, docs, examples and "scm" directory whatever that is. it  
does copying it vi os.system("cp -r ...") because I just wanted a  
quick and dirty proof of concept, i'll convert it to real python and  
make it skip CVS dirs now.

But may be you know better how to do that?

> Ok, the scheme scripts that end up in the resources folder come direct
> from the guile-1.6.7 release - it's a copy of the ice-9 directory  
> which
> contains a few scripts required to startup the interpretor (AFAICT).
> Obviously if you've linked against a newer guile lib then this  
> should be
> copied from the newer version also.
>
> How does guile know where this is? Hmm a little hack to the  
> beginning of
> main() - detailed in the wiki page - which appends the resources  
> path to
> the GUILE_LOAD_PATH env variable.

All right, I'll have a look at the wiki page and incorporate that  
copying. I think the right thing to do is to bundle all scripts that  
come with guile, so that you can do interesting stuff in fluxus live ;-)

I was gonna extend load path anyway - i want fluxus to have several  
builtin paths itself, so i'll add the new guile paths there too.  
Actually the "correct" thing to do is probably overwrite guile's load  
path, because by default it points to $prefix/.../site or something  
(guile prefix that is), which is most probably empty with other  
peoples installing binary bundle. Also making sure we get rid of  
default paths we'll be able to test it better on our machines where  
default location DOES contain guile scripts.

> As for the icon - hmm i'm not sure. If i remember i just copied the  
> icon
> into the appropriate place and knocked together a new Info.plist  
> because
> I couldn't get the one in cvs to work (figured it was me, but it might
> be worth comparing the two to see where they differ). As for the icon
> itself - i just wanted to play with the os x icon builder and that was
> the first image that came to hand :)

I'll read some more documentation about bundles.

> The only *major* problem i found with the binary was that it linked
> against some symbols (_ftime if i recall correctly) which weren't
> defined in the standard libs on panther (10.3.*) release of os x. I  
> can
> definitely test a binary on 10.4 but it would be good to find someone
> who can test on 10.3 as well.

I remember installing something like crosscompilation sdk, which  
allegedly allows to build on 10.4 binaries that run on 10.3 and 10.2.  
I'll check that out later.

> BTW have you seen darwinports (www.darwinports.org)? It makes
> installing/uninstalling deps very easy - great for testing this  
> kind of
> thing. The only weirdity is it installs everything in /opt/local but
> they seem to have their reasons for that... As another os x newbie it
> made my life much easier!

Yes, I know about darwin ports, (and also about gentoo for darwin and  
fink, the latter is installed on all macs at our lab). I don't use  
them, the point of having this laptop is that I can build stuff for  
artists with no clue about compiling stuff and installing open source  
frameworks.

BTW, fink installs everything into /sw ;-)