gambit-c and black-home module system - how to produce stand alone executable?
Hello,
I am using gambit-c v4.6.0 and the latest black-hole (including std libraries) from git (as described on the gambit-c web site).
In the gsc interpreter, all seems fine and I can load black-hole and import installed std libraries, while using the repl.
The "my-program.scm", does _not_ load the black hole (AFAIK, I am supposed to do from command line, using -e), and it does only following import (before any functions from std are used):
(import (std srfi/13 srfi/95))
The all of std are compiled to .o1 files (as described in the black-hole guide)
One thing I cannot figure out - how do I produce stand alone, compiled, executable when using black-hole modules?
So far, I tried (gsc-gambit is gambit-c compiler executable name):
gsc-gambit -exe -e '(load "~~/lib/modules/build")' my-program.scm
the above compiles, but when run, the my-program does not have functions from
gsc-gambit -ld-options "-rpath-link /home/vladimir/opt/gambc/lib/modules:/home/vladimir/opt/gambc/lib/modules/std/srfi build.o1 13.o1 95.o1" -exe -e '(load "~~/lib/modules/build")' my-program.scm
the above fails with "gcc unrecognised option".
I have searched the mailing list, read what I could, tried what I could think of, but now I am quite stuck...
Kind regards,
Vladimir
------
because it reverses the logical flow of conversation + it is hard to follow.
why not?
do not put a reply at the top of the message, please...
Please access the attached hyperlink for an important electronic communications disclaimer: http://www.lse.ac.uk/collections/planningAndCorporatePolicy/legalandComplian...
Afficher les réponses par date
Hi Vladimir,
Until relatively recently, it was not possible to compile BH modules to standalone executables, so the documentation of that feature is pretty non-existent. There is a procedure called module-compile-to-standalone, which takes two arguments: a string which is the name of the output executable, and a module identifier. For instance
(module-compile-to-standalone "hello" 'hello)
Note that this is not supposed to be used as a part of the development cycle, as it recompiles all dependencies. Let me know if it doesn't work for you, as this isn't very well-tested.
best, Per
9 mar 2010 kl. 14.44 skrev Vladimir Konrad:
Hello,
I am using gambit-c v4.6.0 and the latest black-hole (including std libraries) from git (as described on the gambit-c web site).
In the gsc interpreter, all seems fine and I can load black-hole and import installed std libraries, while using the repl.
The "my-program.scm", does _not_ load the black hole (AFAIK, I am supposed to do from command line, using -e), and it does only following import (before any functions from std are used):
(import (std srfi/13 srfi/95))
The all of std are compiled to .o1 files (as described in the black-hole guide)
One thing I cannot figure out - how do I produce stand alone, compiled, executable when using black-hole modules?
So far, I tried (gsc-gambit is gambit-c compiler executable name):
gsc-gambit -exe -e '(load "~~/lib/modules/build")' my-program.scm
the above compiles, but when run, the my-program does not have functions from
gsc-gambit -ld-options "-rpath-link /home/vladimir/opt/gambc/lib/modules:/home/vladimir/opt/gambc/lib/modules/std/srfi build.o1 13.o1 95.o1" -exe -e '(load "~~/lib/modules/build")' my-program.scm
the above fails with "gcc unrecognised option".
I have searched the mailing list, read what I could, tried what I could think of, but now I am quite stuck...
Kind regards,
Vladimir
because it reverses the logical flow of conversation + it is hard to follow.
why not?
do not put a reply at the top of the message, please...
Please access the attached hyperlink for an important electronic communications disclaimer: http://www.lse.ac.uk/collections/planningAndCorporatePolicy/legalandComplian... _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
Hello Per
(module-compile-to-standalone "hello" 'hello)
Thanks for the pointer, so, it looks that the "main" program (I wrote) also has to be converted to black-hole module? No big deal if yes, about to try it.
Kind regards,
Vladimir
------
because it reverses the logical flow of conversation + it is hard to follow.
why not?
do not put a reply at the top of the message, please...
Please access the attached hyperlink for an important electronic communications disclaimer: http://www.lse.ac.uk/collections/planningAndCorporatePolicy/legalandComplian...
Hello,
(module-compile-to-standalone "hello" 'hello)
It works (and produced working executable) :-)
Kind regards,
Vladimir
Please access the attached hyperlink for an important electronic communications disclaimer: http://www.lse.ac.uk/collections/planningAndCorporatePolicy/legalandComplian...
(module-compile-to-standalone "hello" 'hello)
Is it possible to compile an executable that will not include all the modules but resolve them at runtime? Also is it possible for it to behave like gsi-script... (Call the main procedure)
-
Jeremie Lasalle Ratelle -
Per Eckerdal -
Vladimir Konrad