On Thu, Nov 8, 2012 at 9:04 AM, Ralph Möritz <firstname.lastname@example.org> wrote:
Re. #2, I don't really mind what ECL does with large constant strings behind the
scenes, the point is that ECL *knows* which compiler it's using so it *could* do whatever is necessary such as setting *COMPILE-IN-CONSTANTS* or passing the appropriate compiler switches to find the ECL libs. If Franjo & the regulars don't have time to implement this, I'll be happy to do it myself & post a patch - Just let me know where in the source to start looking.
Re. #3, `ecl -o <executable -link <object>` works, but only after producing the object file, which still
requires all the manual steps mentioned because `ecl -compile <lisp>` produces a FASL file, and `ecl -o
<object> -compile <lisp>` gives the following error: (Provided `(ext:install-c-compiler)` is in your .eclrc,
otherwise it just produces FASL output)
LINK : fatal error LNK1149: output filename matches input filename 'C:\Users\ralphm\Temp\src\experiments\lisp\hello-ecl\hello.obj'