asdf-devel

asdf-devel@common-lisp.net

1376 discussions

[asdf-devel] Various issues
by Tobias C Rittweiler 24 May '12

24 May '12

Hi there! Thanks to the ASDF maintainers. I just visited ASDF's website on common-lisp.net since a long time, and it makes a nicely maintained impression! Well done. I have the following issues: * The rather old ASDF version that I'm using ("2.010") does not seem to be able to cope with multiple :depends-on clauses. (Only one clause seems to be used.) Is this intended behaviour? Might it be fixed in more recent versions? * :STATIC-FILE (and :FILE for that matter) are not discussed or explained in the manual. * We generate a 'version.lisp' with a (DEFPARAMETER ...) form in it when using "make" to build a Lisp binary using buildapp. Is there a component that loads a file if it exists and if it does not exist just skips the clause? Thanks, T

4 5

[asdf-devel] asdf-bundle
by Faré 18 May '12

18 May '12

asdf-bundle is now working (hopefully) on SBCL and CCL as well as ECL, by concatenating fasls. It won't work for systems where CFFI creates .so. Try it! (require :asdf) (require :asdf-bundle) (asdf:oos 'asdf::load-fasl-op :your-favorite-system) It creates a your-favorite-system.system.fasl in the fasl cache. Actually, I'm not sure about ECL anymore - load-fasl-op fails at the last minute (after the fasl-op itself) because it tries doing something with a .fasb even though I didn't enable the bytecode compiler. Since I leveraged that part of the code from asdf's asdf-ecl.lisp, I suspect it is broken there already. Juanjo: can you give a look when you have time? Others: you're welcome to contribute support for your favorite implementations. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Don't have good ideas if you aren't willing to be responsible for them. — Alan Perlis

2 1

[asdf-devel] Tests on Mac OS X
by Robert Goldman 17 May '12

17 May '12

I tested on the following lisps ccl clisp sbcl ecl abcl allegro allegromodern with success. Haven't tried on CMUCL yet, because of prior problems. I will see about picking up a snapshot sometime.

1 0

[asdf-devel] lisp source debugger
by Yuan Luo 13 May '12

13 May '12

Hi, This maybe an irrelevant question, if so, please point me to the best list to ask. But I am wondering whether you guys can recommend some source level debugger that can POINT ME PRECISELY to where the error was. For example, Allegro CL cannot because many times it tells me that there is an error in a function, but it doesn't tell me which line even if I set their debug flag to 3 the highest level and suppressed everything else, speed, optimization etc. (my function has hundreds of lines then I am frustrated ...) Best, Yuan

3 2

[asdf-devel] :default-component-class and custom module classes
by Nikodemus Siivola 07 May '12

07 May '12

I was trying to make a custom module class, which would have provided its own :DEFAULT-COMPONENT-CLASS via :DEFAULT-INITARGS, but (setf (module-default-component-class ret) (or default-component-class (and (typep parent 'module) (module-default-component-class parent)))) means that does work as I hoped it would. The closest I can get is by overriding ASDF::MODULE-DEFAULT-COMPONENT-CLASS method, but that seems fairly icky. Is there a better way? Cheers, -- Nikodemus

2 1

[asdf-devel] Reloading a .asd
by Stelian Ionescu 07 May '12

07 May '12

I'm using the elisp snippet below(courtesy of Stas Boukarev with some modifications) to reload a .asd file. Is asdf::load-sysdef the best way to trigger a reload(but not recompilation) ? Use case: I want to work on a system that isn't in the ASDF path, it being one of the many development trees I have around(e.g. CFFI), so I want to be able to say that "this cffi.asd is the CFFI to use during this session". Any ideas ? (defvar slime-custom-file-loaders '(("asd" . slime-load-asdf) ("lisp" . slime-load-file))) (defun slime-load-asdf (filename) (slime-eval-with-transcript `(asdf::load-sysdef ,(file-name-sans-extension filename) ,(slime-to-lisp-filename (expand-file-name filename))))) (defun slime-custom-load-file () (interactive) (unless buffer-file-name (error "Buffer %s is not associated with a file." (buffer-name))) (check-parens) (when (and (buffer-modified-p) (y-or-n-p (format "Save file %s? " (buffer-file-name)))) (save-buffer)) (let* ((type (file-name-extension buffer-file-name)) (loader (cdr (assoc-string type slime-custom-file-loaders t)))) (funcall (or loader 'slime-load-file) buffer-file-name))) (define-key slime-mode-map (kbd "C-c C-l") 'slime-custom-load-file) -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. http://common-lisp.net/project/iolib

3 8

[asdf-devel] asdf 2.21 released
by Faré 29 Apr '12

29 Apr '12

I am pleased to announce the release of ASDF 2.21. Since previous release 2.20, the changes are as follow: * New features: * Most importantly, encodings. ASDF now lets you specify an :encoding for a system, module or component, that is used when loading or compiling Lisp files. See the documentation. By default, the only useful value is :utf-8, and we recommend you use UTF-8 everywhere. We intend to make UTF-8 the default in the future (current default is the legacy behavior of using whichever implicit default your underlying implementation is currently configured to use). An extension asdf-encodings is available that supports more encodings, including autodetection of encoding from either emacs-style declaration -*- Mode: Lisp ; coding: utf-8 -*- or content. * require-system works like load-system, but won't try to load or update systems that have already been loaded, as listed by loaded-systems. More generally, you can specify a list of systems as :force-not argument to load-system and the specified systems won't be loaded or updated. * You can specify :force-not and a list of systems when loading a system, * You can now specify :hostname in your asdf-output-translations, so you can easily share a home directory via the network yet split its fasl cache between several subtly different machines. * Bug Fixes: * lp#982285. since 2.014.4, the default source-registry was skipping anything from /usr or XDG_DATA_DIRS, because of a missing test in getenv-absolute-pathnames. Fixed in .15. * In 2.019.9 aka 2.20, ECL support was broken by using a function in the wrong package (defined in cl-user). Fixed in .1. * logical-pathname support was somewhat broken since 2.017.6, due to the way most implementations fail to read physical namestrings when *default-pathname-defaults* is a logical-pathname. Fixed, together with other logical-pathname issues, and a test case was added to the test suite to ensure no further regression. Works great modulo quirks around implementation bugs on CLISP and Allegro. * Make upgrading ASDF more robust on CMUCL, LispWorks, SBCL. * Minor tweaks: * Use :unspecific in pathname components on more implementations. * export and/or document more utilities. * add a few missing compatfmt for Genera. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org As Marx should have said, the principle of communism is From each according to what he can't get out of doing. To each according to whom he knows. — John McCarthy

1 0

[asdf-devel] ASDlite - light-weight excerpt from ASDF
by Dmitriy Ivanov 26 Apr '12

26 Apr '12

Hello folks, Excuse my bothering if this is not a correct place to announce. Nonetheless... ASDlite Design Goals 1. Small footprint. 2 Ease of embedding into applications and systems not related to "compile-and-load Lisp files" tasks. For example: YstokHelp (http://lisp.ystok.ru/yhelp/) 3. ASDF compatibility for basic needs. 4. Operation arguments specification in dependencies. Observation and Rationale 1. The ASDF built-in operation hierarchy is actually of two-level depth. Original ASDF code does not exploit operation inheritance much (though something can be found in asdf-ecl.lisp). 2. The operation slots are rather useless: original-initargs Is only referred in print-object parent In principle, indicates the target operation that required this one. But due to reusing operation objects in make-sub-operation, this is not the case. Also used for marking along with other visiting slots during traverse but we follow another approach. Adding entirely new operations, i.e. on the first level, is fine. But there is comfortable way to refine existing operations: the easiest way is to add slots to base operation classes as only those properties do get passed into dependency operations. There is a more simple way pass arguments from operate to operation functions - by means of key arguments! 3. The :do-first initarg is actually ignored by ASDF - its always set to ((compile-op (load-op ,@depends-on)))) 4. Avoid inline methods, which are rather inelegant in ASDF: - they rely on eval, - ASDF tries to remove a method from a generic function of a different name. Due to non-standard behavior of remove-method in LW 4.4, system redefinition intrusively signals about this. 5. Referring to features in component definition is more useful than for dependency rules. Operations in ASDlite operation ::= keyword | operation-instance operation-type ::= keyword | type-symbol operation-designator ::= keyword | (keyword . plist) | type-symbol | operation-instance Operations are passed to perform and other operation-specific methods. Operation designators can be used in the right-hand side of rules. We encourage using simple keywords like :compile or :load. For these, ASDlite defines corresponding methods with eql specializers. The plist allows you to pass key arguments to the operation methods. In the "normal" mode, ASDlite accepts only keyword-based forms. If you feel these are not enough and need "full-fledged" ASDF operation classes, you can switch to the ASDF compatibility mode as follows: - push :asdf-compat into *features* before compiling asdlite.lisp, - refer to asdf:compile-op, asdf:load-op and the like, - define your own subclasses of the operation class etc. In the compatibility mode, ASDlite accepts all the above forms of operations and designators. Downloads and Details http://lisp.ystok.ru/asdlite/ -- Sincerely, Dmitriy Ivanov lisp.ystok.ru

2 2

[asdf-devel] asdf-bundle
by Faré 26 Apr '12

26 Apr '12

Dear Juanjo, is it OK with you if unbundle asdf-ecl from asdf.asd, and instead create a somewhat portable asdf extension called asdf-bundle.asd ? Impact: when the unbundling is complete, ecl users will be encouraged to (require :asdf-bundle) instead or in addition to (require :asdf) if they want to use the extensions currently provided in asdf-ecl. But it will make the bundle-op operations available to other implementations in a more portable way. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org To authorize all commercial relations between consenting adults.

2 3

[asdf-devel] Tool for transcoding lisp source files and adding coding file options.
by Douglas Crosher 25 Apr '12

25 Apr '12

A tool to add the coding file option to lisp source files is now available. This can also be used to transcode all the files to UTF-8, or to attempt transcoding to ISO-8859-1 or US-ASCII with loss in comments. There is an example for the current Quicklisp releases with a few required exceptions. This is experimental, particularly the transcoding to ISO-8859-1 or US-ASCII. Please backup your code before giving this a try! See: http://www.scieneer.com/files/transcode.lisp With the coding file option in place, the developmental version of ASDF is able to pass the correct external-format to 'load and 'compile-file. Note the lambda-reader is handled by substituting references to the lambda character back to "(lambda". Since the :encoding file option should become unnecessary with the coding file option, and also because it would be invalid upon any transcoding, it is removed from .asd files. I don't think it would be practical to try and update the :encoding declarations. With the coding file option on all the files, all that asdf-encodings needs to do is read this file option. The UTF-8 and other detection could be removed and moved into a tools such as this. If some of the CL implementations would add the reading of the file option as an external-format then the coding file option could be used by 'load and 'compile-file outside of ASDF - then for these CL implementations asdf-encodings would not be necessary and ASDF could pass on the encoding-file-option reading external-format which may well be the :default. I will look at implementing this for the Scieneer CL, and perhaps take a look at CMUCL, but it would be best optimized for each CL implementation. Regards Douglas Crosher

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel