On Sat, Mar 13, 2010 at 8:50 PM, Faré <span dir="ltr">&lt;<a href="mailto:fahree@gmail.com">fahree@gmail.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Where is the file to be when you compile?<br>
Where is the file to be when you load?<br>
How do you currently do things, and what breaks?<br>
Could say, a logical pathname host LIB:<br>
help locate the libraries?<br>
How do you do things without ASDF?<br></blockquote><div><br>There is not going to be any file that gets compiled. There is not going to be any lisp sources.<br><br>The goal is to replace a set of sources + asdf file with a set of compiled files (one static library, one FASL files) and a hacked *.asd file that relies only on those binary files.<br>
<br>An important component is that users are able to build these sets of *.asd+*.lib+*.fasl file with something like (asdf:make-standalone-system &#39;some-system-name) and then installed anywhere.<br><br>I mean that the set of files should then be installed anywhere the user wants -- as far as it is a path reachable by ASDF and the files remain together, in the same directory. Using logical pathnames is not an option because we can not know where the user wants to have the files.<br>
<br>What is the purpose of this? Well, it would make software distribution very easy, in particular for Linux-like distributions, but it would also be useful for users that want to deliver a program and a set of extensions in the form of ASDF system definitions -- a tool they are already familiar with --.<br>
<br>Juanjo<br></div></div><br>-- <br>Instituto de Física Fundamental, CSIC<br>c/ Serrano, 113b, Madrid 28006 (Spain) <br><a href="http://juanjose.garciaripoll.googlepages.com">http://juanjose.garciaripoll.googlepages.com</a><br>