X-Spam-Check-By: sourceware.org From: "Hannu E K Nevalainen" <_garbage_collector_@telia.com> To: Subject: RE: executable = exe + data Date: Sun, 1 Jan 2006 22:37:58 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Sam Steingold wrote: Hannu: >> Then your options seems to have shrunk to a "launcher" that basicly >> does >> >> system("lisp.exe -M lispinit.mem") > > :-) > > this is what we have been doing for well over 15 years ... well, time for some progress ;-) >> Can you elaborate on _why_ the "single executable" is so important? > > It is not important to _me_, but this is a recurring request by lisp > newbies who ask something like "how do I create an executable from my > lisp application, similar to C and C++?" Ahh... Well. I wonder, would it not be possible to extract portions of code from "lisp.exe" above (looking for the "-M" option - assuming you have access to the source, GPL?), such that the code does what you're asking for - given some tweaking. That combined with the linker object thingies discussed earlier -> Voilá. Maybe add some "automatic" scripting and you're finally "home". /H -- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/