[Ecls-list] compile package dependencies to C

[Sam Sam]

Yes, that worked.

Now, about the name mangling - is there any way to control it? For example, i had a (defun main ...
which
 got renamed to L1main(). Not so bad yet, but the top-level LISP code 
gets wrapped in a function with a completely random and unpredictable 
name like _eclpXiVf4X4_TkyRds01(cl_object flag). 

And this brings
 me to my next question - how do i keep the "startup" code so the C file
 can be built with gcc/ld at a later time? I didnt find it in the 
~/.cache/common-lisp/...

cheers!

From: juanjose.garciaripoll at gmail.com
Date: Sat, 2 Mar 2013 09:48:06 +0100
To: mm_lists at pulsar-zone.net
CC: ecls-list at lists.sourceforge.net
Subject: Re: [Ecls-list] compile package dependencies to C


On Fri, Mar 1, 2013 at 11:26 PM, Matthew Mondor <mm_lists at pulsar-zone.net> wrote:




I've not tried it with asdf, but does setting C::*DELETE-FILES* to NIL

help?
This will leave the files, but ASDF makes pretty ugly names and places the files in a common location (~/.cache/common-lisp/...) For debugging it is normally enough, though



-- 
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain) 
http://juanjose.garciaripoll.googlepages.com


------------------------------------------------------------------------------
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_feb
_______________________________________________
Ecls-list mailing list
Ecls-list at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20130307/2719aa6a/attachment.html>