Thanks Matt, apologies for top-posting - I know it's bad form but I'm using a web interface to reply. 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' Cheers, Ralph
---------------------------------------- > Date: Wed, 7 Nov 2012 17:33:17 -0500 > From: mm_li...@pulsar-zone.net > To: ecls-list@lists.sourceforge.net > Subject: Re: [Ecls-list] Building native EXE on Windows is too hard! > > On Wed, 7 Nov 2012 15:16:57 +0200 > Ralph Möritz <ralph.moer...@outlook.com> wrote: > > > 2. Why do we manually have to set C::*COMPILE-IN-CONSTANTS* to T? > > Some compilers have difficulty with large C constant strings, such that > ECL had to append the data to the fasl files instead, but I thought > that this problem was mainly a Visual C++ limitation (perhaps it's no > longer the case if *COMPILE-IN-CONSTANTS* now works for you)? > > I admit having to myself enable this as part of my build scripts, as > it's no problem with GCC and it's friendlier to binutils. > I guess that at ECL build time, if autoconfiguration can reliably test > for this limitation, it'd be possible to have it default to T with > compilers that support large string constants? > > > 3. A command-line switch like Gambit-C's -exe to build an EXE from Lisp > > code would be nice :) > > Does "ecl -o <executable> -link <objects>" work? I personally have > no experience with ECL on Windows though. > -- > Matt > > ------------------------------------------------------------------------------ > LogMeIn Central: Instant, anywhere, Remote PC access and management. > Stay in control, update software, and manage PCs from one command center > Diagnose problems and improve visibility into emerging IT issues > Automate, monitor and manage. Do more in less time with Central > http://p.sf.net/sfu/logmein12331_d2d > _______________________________________________ > Ecls-list mailing list > Ecls-list@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ecls-list > ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
