I'm also interested in the tooling around statically linked eggs, or
at least finding ways to better document the process. I've had mixed
results, sometimes it's easy, others it's incredibly painful. If
anyone has ideas on how to improve this I'd be willing to help out.
On 19 May 2015 at 06:18,
Caolan McMahon writes:
I'm also interested in the tooling around statically linked eggs, or
at least finding ways to better document the process. I've had mixed
results, sometimes it's easy, others it's incredibly painful. If
anyone has ideas on how to improve this I'd be willing to help
Evan Hanson writes:
Hi Nick,
On 2015-05-18 9:12, Nick Andryshak wrote:
Would it be feasible to make my own object files for eggs that don't
include them by using chicken-install -retrieve, and then compiling the
sources?
Yes, and it's straightforward to do for most extensions -- I've
I see, thanks for the reply!
Would it be feasible to make my own object files for eggs that don't
include them by using chicken-install -retrieve, and then compiling the
sources?
- Nick
___
Chicken-users mailing list
Chicken-users@nongnu.org
Hi Nick,
On 2015-05-18 9:12, Nick Andryshak wrote:
Would it be feasible to make my own object files for eggs that don't
include them by using chicken-install -retrieve, and then compiling the
sources?
Yes, and it's straightforward to do for most extensions -- I've used
this approach for a
Hi Nick,
On 2015-05-11 13:31, Nick Andryshak wrote:
But can you statically link Eggs anymore? There's like 40 files in the
deployment folder after deploying only one extension, I'd like a single,
static executable. Is this possible?
It's possible if all of the eggs you need to use provide
It looks like this was once possible with the `-static-extension[s]` option
in csc, but I can't figure out how to do this currently.
You can deploy a static executable like this:
$ csc -static -deploy app.scm
And deploy extensions like:
$ chicken-install -p $PWD/app -deploy fmt
But can you
