On Nov 23, 2011, at 9:45 PM, Igor Stasenko wrote:
On 23 November 2011 21:16, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Igor
since we will want to have that on the build server ;) can you tell a bit what you did that I try on my machine.
since i installed ports before, and since my system is 64 bit, most of packages are built using 64bit arch. now, since i insisted to also have 32bit libs (obviously to be able to use cairo with VM), i had to reinstall all dependents of cairo (a lot) with +universal flag.
so, the basic rule, is whenever you install anything using ports, add +universal option, to make sure that it will produce 'fat' binaries containing both 32bit and 64bit versions. (of course it doubles the compilation time ;)
about portâ¦.. people make me laugh when they say that GTK is available one day it took 8 h to get it installed on my machine and it did not work at all :(
hehe.. to build cairo, for some strange reason it had to rebuild xml, python, perl, x11 lib and dozen of other stuff.
rephrasing famous Alan's Kay note: by saying "modularity" i didn't had C dynamic libraries in mind :)
now given that cairo library having so much/deep strange dependencies, i am not sure whether we should a) build it on build server b) bundle it with VM
a), because port seems to be working, and it is external to our project and maintained by people we do not know. b, because otherwise it may require to bundle VM with 32-bit versions of a lot of libs, which normally can be found in any unix system, and should be installed by user(s) , not us.
Indeed we should not :) Now when we will ship pharo it would be good to have a lib included.
Stef
-- Best regards, Igor Stasenko.