[Ecls-list] Building native EXE on Windows is too hard!

Ralph Möritz ralph.moeritz at outlook.com
Wed Nov 14 07:30:45 UTC 2012


> Sorry, my name is Juanjo, not Franjo :-)

Apologies, no disrespect intended.

> Regarding compile-in-constants, I think you guys do not know the real
> history. Microsoft's compiler has a severe limitation in compiler
> string size. This means we cannot build constant data that takes more
> than 64k. The only way we escape this in FASL files is by appending
> the data to the compiled file. This *does not work*with standalone
> executables for various reasons: we cannot append the data to the
> object files (the linker complains); even if this was solved, we
> cannot append it to the executable, because there is no way to locate
> it (other than searching through the path, but not even that,
> always).

I don't think 64k is such a severe limitation; for code using very
long string literals couldn't we use embedded resources instead?

> In any case, it is not that hard to do this one-liner
>
> $ ecl -eval '(ext:install-c-compiler)' -o foo.o -compile foo.lsp -s

Very nice! Thank you Juanjo.

Ralph. 		 	   		  



More information about the ecl-devel mailing list