asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

Start a nNew thread

[asdf-devel] commit emails
by Nikodemus Siivola 07 Oct '09

07 Oct '09

Do we have these? If not, can we get them? Cheers, -- Nikodemus

4 4

[asdf-devel] Note on ASDF getting started guide...
by Robert Goldman 06 Oct '09

06 Oct '09

A couple of points I noticed while doing my backport to info: 1. We start by saying "you can just use require," but then we say "you only need to load asdf.lisp." I think it would be better to say "if this require trick works, you can skip over the section about loading asdf." 2. We might want to say "you might want to install ASDF yourself if you want to get a particular version of ASDF." HtH, r

3 4

Re: [asdf-devel] Recognizing directories in a component name
by Faré 28 Sep '09

28 Sep '09

2009/9/27 Gary King <garywarrenking(a)gmail.com>: > This is _finally_ out; please let me know if anything seems amiss. Thanks a lot! What you have does the trick for me wrt directories in the name, but now that I think of it, to fully solve the problem of source-file-type being NIL (for e.g. static-file) as experienced by several other hackers (and me before I tweaked my .asd files), a cleaner and more effective version should be as attached. I also updated the test script to actually work, as opposed to dying after the first quit-on-error (that also quits without error). I also renamed the fasl directory to .cache/common-lisp/ which you might want to undo. I added newlines in the script-support results. I moved around a function to remove an annoying "undefined function" (actually forward reference) message when loading asdf on SBCL. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Time and money spent in helping men to do more for themselves is far better than mere giving. -- Henry Ford

1 0

[asdf-devel] announce: asdf 1.366
by Gary King 27 Sep '09

27 Sep '09

Thanks to all the contributions and please let me know if anything seems awry. * rename *place-binaries-in-implementation-specific-directories* to *enable-asdf-binary-locations* * Daniel Herring's CLISP/Windows/Symlink patch #+(and (or win32 windows) (not :clisp)) * Faré's patch for better module-pathname handling * test for same * Fix for my head-slap regex s&r madness. -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

2 1

[asdf-devel] Obscure A-B-L bug?
by Daniel Herring 26 Sep '09

26 Sep '09

Hi, The following is representative of an obscure bug I'm trying to resolve (without direct access to the computer). It affects A-B-L 0.3.8 and a recent release of ASDF, but I don't see any relevant changes to either project in the past couple years. To set up this example, # cd /path/to/.asdf # ln -s ../asdf-binary-locations/asdf-binary-locations.asd . Then under LispWorks on a PPC mac, CL-USER > (push #P"/path/to/.asdf/" asdf:*central-registry*) CL-USER > (asdf:operate 'asdf:load-op :asdf-binary-locations) ; loading system definition from ; /path/to/.asdf/asdf-binary-locations.asd into ; #<The ASDF0 package, 0/16 internal, 0/16 external> ; Loading text file /path/to/.asdf/asdf-binary-locations.asd ; registering #<SYSTEM ASDF-BINARY-LOCATIONS 200B9373> as ASDF-BINARY-LOCATIONS Error: The file #P"/path/to/.asdf/dev/main.lisp" does not exist. ASDF is clearly resolving the symlink to read A-B-L.asd; but its using the wrong path to load the source files. Is the custom load-op for load-only-cl-source-file somehow skipping the normal truename/path merging process? Any other ideas or things to look for? Thanks, Daniel

3 2

[asdf-devel] patch system-source-file
by Greg Pfeil 25 Sep '09

25 Sep '09

Here are a couple changes to ASDF that I made in the process of creating an ASDF browser for CCL's IDE: • system-source-file now works for systems without their own .asd • optional parts of systems (version, maintainer, etc.) don't leave their slots unbound

7 17

[asdf-devel] directly evaluating .asd file
by Tobias C. Rittweiler 25 Sep '09

25 Sep '09

Visiting an .asd file and using C-c C-k to compile-and-load would make the system properly available in past. This does not seem to work since a few revisions. It now tries to load the files specified in the system relative to the current working directory. When I C-c C-l, that is just load without compiling, it still works as it did in past. Is this a known regression? -T.

1 0

[asdf-devel] [RfC] default value for *central-registry*
by Tobias C. Rittweiler 24 Sep '09

24 Sep '09

I hate that I have to push a commonly shared directory onto *central-registry* for each implementation and thus have to know the rc files of every implementation. (I was recently bidden by some classic rm -rf ~, and had to redo all these kinds of infrastructure woes.) Would anyone mind ASDF coming with an additional default value of ~/.asdf/systems/? -T.

6 10

[asdf-devel] updating ccl's bundled asdf
by R. Matthew Emerson 24 Sep '09

24 Sep '09

[sorry if this is duplicate] We bundle an ASDF version that's about a year old or so (1.130) with Clozure CL. If I want to bundle a newer ASDF with CCL, what version should it be? There seem to have been half a dozen releases in the past couple of months. Would it be best to wait a little longer for things to settle down?

4 6

[asdf-devel] ASDF features under discussion
by Juan Jose Garcia-Ripoll 23 Sep '09

23 Sep '09

Now that this discussion is opened, I would like to add a small question and a petition. First the question. What is the level of integration of ASDF with different implementations? Does ASDF support all lisp implementations equally? Does SBCL (and perhaps other) ship the latest versions of ASDF? I am asking this because ECL has some pretty special needs. Namely, ASDF currently relies on compile-file / load for everything and for us it is more efficient to compile many files into a single binary that is loaded at a later point. Currently ECL solves this using a slightly outdated version of ASDF, providing its own operations and imposing around methods on different operations. http://ecls.git.sourceforge.net/git/gitweb.cgi?p=ecls/ecl;a=blob;f=contrib/… For instance, we have a LOAD-FASL-OP that joins three steps: 1) a LOAD-OP that thanks to the around methods produces both FASLs and object files, 2) linking the object files into a big FASL, 3) loading the big FASL. If the big FASL has been produced, then only step 3) is performed. But in addition to this ECL provides operations for creating standalone executable files, shared libraries and statically linked libraries http://ecls.sourceforge.net/new-manual/ch16.html I am aware that ASDF is a rapidly evolving architecture and I am afraid that things would break. It is for this reason that I would like to ask for help in one of these ways: 1) providing a stable way for us to implement these extensions or 2) including those operations in ASDF. Juanjo On Wed, Aug 19, 2009 at 3:11 PM, Gary King<gwking(a)metabang.com> wrote: > For the record, we've had recent (but not definitive) discussions of: > > * whether or not optional parts of a system should be `nil` or unbound > > * version numbering > > * integrating ASDF and testing > > * ASDF and the windows symlink patch. > > If there are things I missed in the above list, please let me know. -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com

5 7

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel