On 6/11/06, Goetz Isenmann <[EMAIL PROTECTED]> wrote:
I had hoped, that I - could compile chicken with any arbitrary installation path (say /var/tmp/chicken or %TEMP%\chicken), - build a binary package from that, - install this package into another directory on many machines or on a network share (if neccessary different versions side by side), - and use these installations after setting CHICKEN_HOME and LD_LIBRARY_PATH (or equiv). Currently, that does not seem to work. Is that something, that could be fixed, or are there other reasons, why I should not try to do this with the interpreter, the compiler, the runtime, or (static/dynamic linked) applications?
Hm... This *might* work by setting CHICKEN_HOME, LD_LIBRARY_PATH and CHICKEN_REPOSITORY, but will always be a bit of a hack. What specific problems do you currently have? What you intend to do makes certainly sense, so perhaps we should try to address this. (felix) _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
