November 2012 - asdf-devel - mailman3.common-lisp.net

[asdf-devel] asdf-bundle and ECL
by Faré 30 Nov '12

30 Nov '12

> Found a problem: https://github.com/quicklisp/quicklisp-client/issues/68 OK, so Quicklisp was failing on older ECLs, because 1- it saw that older ECLs had an old ASDF, so it loaded its own more recent one (2.26) 2- when it loads a more recent ASDF, that invalidated the asdf-bundle part of ECL's ASDF. 3- when it further tried to (require :sockets), that failed, because require depends on asdf-bundle. Therefore, it looks like asdf-bundle is required when upgrading ASDF on ECL for Quicklisp. I bundled (pun intended) asdf-bundle into a single Lisp file asdf-bundle.lisp, so it's easier to deploy, either as part of ECL or of Quicklisp. Along the way, I fixed it for SBCL (some recent changes must have broken it), and tested it on SBCL and ECL: (asdf:load-system :asdf-bundle) (trace load) (asdf:operate asdf:load-fasl-op :fare-utils) Does what I expect from a fresh Lisp image where the fasls have been compiled already. Now, do we want to distribute asdf-bundle.lisp as a separate system asdf-bundle.asd? Do we want to distribute it as part of asdf.asd the way we used to do asdf-ecl.lisp? Do we want to just add its contents to asdf.lisp, a growth of a bit over 10% in size, for additional functionality on many platforms and much less headaches on ECL? —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org An anarchist is a man who is careful to always use pedestrian crossings, because he utterly detests talking with policemen. — Georges Brassens

2 2

[asdf-devel] Patch with ABCL specific changes
by Mark Evenson 29 Nov '12

29 Nov '12

Attached please find a patch synchronizing the version of ASDF we intend to ship with abcl-1.1.0 with the canonical version. These changes deal with bugs when using systems contained in jar archives via the ABCL implementation specific extension of CL:PATHNAME.

2 3

[asdf-devel] ASDF 2.26 in Quicklisp
by Faré 29 Nov '12

29 Nov '12

At Xach's suggestion, I wrote this article on my livejournal about what has changed since Quicklisp's previous ASDF 2.014.6: http://bit.ly/WXJ8Kx —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Ever wonder why the SAME PEOPLE make up ALL the conspiracy theories?

7 19

[asdf-devel] ASDF-bundle and cross-compiling with ECL
by Sylvain Ageneau 28 Nov '12

28 Nov '12

Hello, I'm looking for input/suggestions about something I've been working on that is related to asdf-bundle. I'm trying to come up with a good solution to do cross-compiling of ASDF packages using ECL. For example I want to be able to create a bundle for a system that looks like this: (asdf:defsystem openglsample :components ((:file "package") #+cross (:file "shader-vao" :depends-on ("package"))) :depends-on (#+iphone iphone #+android android #+android cl+j #+(or android iphone) cl-opengl)) Using this system definition, I'd like to be able to create monolithic bundles libopenglsample_iphone.a and libopenglsample_android.a with the constraint that the android version will include the "android" and cl+j systems and the iPhone version will contain the "iphone" system. I tried adding new operations to asdf "cross-compile-op" "cross-lib-op" see here: https://github.com/ageneau/ecl-android/tree/master/lisp-packages/asdf-cross. This mostly works but the handling of the different *features* for each target is a bit of a mess since the host and the target can have different system definitions. Also because of side-effects, cross-compiling of a particular source file might depend on the host having loaded some dependencies first except the host will load this dependency with *features* that might be different than the target. I'm wondering would this be better suited for xcvb? In particular can xcvb cross-compile a system without the host doing the cross-compilation having to load the system definition for the system it is compiling? Regards, Sylvain

2 1

[asdf-devel] Fwd: asdf 2.26 released
by Faré 02 Nov '12

02 Nov '12

Dear Lisp hackers, I am pleased to announce the release of ASDF 2.26. Since previous release 2.25, the changes are as follow: Portability: * Lispworks: enable sys:get-folder-path on Personal Edition for Windows. * ECL: add proper wrapping-source-registry -- very important. Other: * Package change: removed the old ASDF-UTILITIES package nickname for ASDF. Please use the separate ASDF-UTILS system and package for utilities. * compile-file-pathname* bug fix for :output-file nil. Fixes lp#1067617. * get-folder-path factored out of various functions, thanks to Martin Simmons for the suggestion: at long last a change that REDUCES the amount of code in ASDF! As usual, developers, please test and enjoy, vendors, please update your implementation or distribution. (And yes, it would be nice if Quicklisp updated its ASDF at least once a year) —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org You think that by not releasing your in-house software, you save engineering resources. You only get yourself out of the loop.

2 1