Hi Glauber, > Sorry Dave i dont have an answer to your last question but i have > more questions :). If we packaged the binary with all the libs either > statically compiled or bundled on a lib dir and perhaps wrapping a > fluxus.sh with a LD_LIBRARY_PATH to it. > > Which could also be smart enough to search the environment for possible > missing libraries that will not be on this dir lib like when you ldd > fluxus and there are missing ones, search for those make the proper > linking eg, ln -s /usr/lib/libFLAC.so.9 > /path/to/fluxus/lib/libFLAC.so.8, for the hypothetical case it was > compiled against version 8 but the system has version 9. > > My main question is how would we handle the graphics driver libraries? > Would we have to have a binary for each board? or in this particular > case(academical use) could we link it statically to opengl? I remember > doing this on the past but dont remember exactly how i did. Also what do > you think? Im interested on solving this problem cause i want to use > fluxus on a lab too :).
I don't think you can/should statically link to everything. For the case of simplifying installation on linux, it's possible that restricting our use of plt to just mzscheme will help a lot - possibly we could statically link that and make a package which depends on the rest of the libraries (which are all in ubuntu now). I'm assuming a working 'apt-get install fluxus' (or distro equivalent) would be a good enough solution for academic use in labs etc? FWIW - I just remembered that the pure:dyne people did all this work already for fluxus 0.15 (packaging plt + fluxus), so you could probably use that today if you are on debian/ubuntu. For my longterm investigation/need (an all included binary for distribution as a game) I think I can use a combination of the above + removing or statically linking dependancies. cheers, dave
