asdf-devel

asdf-devel@common-lisp.net

1 participants
1378 discussions

[asdf-devel] New manual patch
by Robert Goldman 17 Aug '09

17 Aug '09

I was reading over the info again before my talk, and I realized that there was no discussion of the test-op as one of the predefined operations, although it is predefined. Patch attached. diff --git a/asdf.texinfo b/asdf.texinfo index cfef5c6..761d606 100644 --- a/asdf.texinfo +++ b/asdf.texinfo @@ -558,42 +558,59 @@ If you are creating a component type, you need to implement this operation - at least, where meaningful. @end deffn -@deffn Operation test-system-version &key minimum +@deffn Operation test-op -Asks the system whether it satisfies a version requirement. +This operation should carry out a test on the specified component. ASDF +does not (currently) provide a method for returning a value from the +test-op (or any other operation), so the implementor must ensure that +executing the @code{test-op} has the side effect of printing useful +information about the tests to the CL stream @code{*standard-output*}. -The default method accepts a string, which is expected to contain of a -number of integers separated by #\. characters. The method is not -recursive. The component satisfies the version dependency if it has -the same major number as required and each of its sub-versions is -greater than or equal to the sub-version number required. +The default method for @code{test-op} does nothing, and will have to be +overridden, but invoking @code{test-op} on a component for which nothing +is defined will be a simple no-op. -@lisp -(defun version-satisfies (x y) - (labels ((bigger (x y) - (cond ((not y) t) - ((not x) nil) - ((> (car x) (car y)) t) - ((= (car x) (car y)) - (bigger (cdr x) (cdr y)))))) - (and (= (car x) (car y)) - (or (not (cdr y)) (bigger (cdr x) (cdr y)))))) -@end lisp - -If that doesn't work for your system, you can override it. I hope -you have as much fun writing the new method as @verb{|#lisp|} did -reimplementing this one. +The default dependency for @code{test-op} on a system is to require +@code{load-op} on that system. @end deffn -@deffn Operation feature-dependent-op -An instance of @code{feature-dependent-op} will ignore any components -which have a @code{features} attribute, unless the feature combination -it designates is satisfied by @code{*features*}. This operation is -not intended to be instantiated directly, but other operations may -inherit from it. +@c @deffn Operation test-system-version &key minimum -@end deffn +@c Asks the system whether it satisfies a version requirement. + +@c The default method accepts a string, which is expected to contain of a +@c number of integers separated by #\. characters. The method is not +@c recursive. The component satisfies the version dependency if it has +@c the same major number as required and each of its sub-versions is +@c greater than or equal to the sub-version number required. + +@c @lisp +@c (defun version-satisfies (x y) +@c (labels ((bigger (x y) +@c (cond ((not y) t) +@c ((not x) nil) +@c ((> (car x) (car y)) t) +@c ((= (car x) (car y)) +@c (bigger (cdr x) (cdr y)))))) +@c (and (= (car x) (car y)) +@c (or (not (cdr y)) (bigger (cdr x) (cdr y)))))) +@c @end lisp + +@c If that doesn't work for your system, you can override it. I hope +@c you have as much fun writing the new method as @verb{|#lisp|} did +@c reimplementing this one. +@c @end deffn + +@c @deffn Operation feature-dependent-op + +@c An instance of @code{feature-dependent-op} will ignore any components +@c which have a @code{features} attribute, unless the feature combination +@c it designates is satisfied by @code{*features*}. This operation is +@c not intended to be instantiated directly, but other operations may +@c inherit from it. + +@c @end deffn @node Creating new operations, , Predefined operations of asdf, Operations @comment node-name, next, previous, up

1 1

[asdf-devel] ASDF manual
by Robert Goldman 17 Aug '09

17 Aug '09

The asdf manual seems to document two non-existent operations: feature-dependent-op and test-system-version. Any reason not to excise them from the manual? R

2 2

[asdf-devel] and of course I forgot the attachment....
by Robert Goldman 17 Aug '09

17 Aug '09

Here's David's patch.... --- asdf.lisp-orig 2007-04-07 20:49:06.000000000 +0200 +++ asdf.lisp 2007-04-07 20:51:42.000000000 +0200 @@ -355,13 +355,22 @@ (let ((name (coerce-name system))) (block nil (dolist (dir *central-registry*) - (let* ((defaults (eval dir)) - (file (and defaults - (make-pathname - :defaults defaults :version :newest - :name name :type "asd" :case :local)))) - (if (and file (probe-file file)) - (return file))))))) + (let ((defaults (eval dir))) + (when defaults + (let* ((file (make-pathname + :defaults defaults :version :newest + :name name :type "asd" :case :local)) + #+win32 + (lnk (make-pathname + :defaults defaults :version :newest + :name name :type "asd.lnk" :case :local))) + (when (probe-file file) + (return file)) + #+win32 + (when (probe-file lnk) + (let ((target (parse-windows-shortcut lnk))) + (when target + (return (pathname target)))))))))))) (defun make-temporary-package () (flet ((try (counter) @@ -1172,6 +1181,84 @@ (hyperdocumentation (symbol-package name) name doc-type)) +;;;; Windows shortcut support. Based on: + +;;; Jesse Hager: The Windows Shortcut File Format. +;;; http://www.wotsit.org/list.asp?fc=13 + +(defparameter *link-initial-dword* 76) +(defparameter *link-guid* #(1 20 2 0 0 0 0 0 192 0 0 0 0 0 0 70)) + +(defun read-null-terminated-string (s) + (with-output-to-string (out) + (loop + for code = (read-byte s) + until (zerop code) + do (write-char (code-char code) out)))) + +(defun read-little-endian (s &optional (bytes 4)) + (let ((result 0)) + (loop + for i from 0 below bytes + do + (setf result (logior result (ash (read-byte s) (* 8 i))))) + result)) + +(defun parse-windows-shortcut (pathname) + (with-open-file (s pathname :element-type '(unsigned-byte 8)) + (handler-case + (when (and (= (read-little-endian s) *link-initial-dword*) + (let ((header (make-array (length *link-guid*)))) + (read-sequence header s) + (equalp header *link-guid*))) + (let ((flags (read-little-endian s))) + (file-position s 76) ;skip rest of header + (when (logbitp 0 flags) + ;; skip shell item id list + (let ((length (read-little-endian s 2))) + (file-position s (+ length (file-position s))))) + (cond + ((logbitp 1 flags) + (parse-file-location-info s)) + (t + (when (logbitp 2 flags) + ;; skip description string + (let ((length (read-little-endian s 2))) + (file-position s (+ length (file-position s))))) + (when (logbitp 3 flags) + ;; finally, our pathname + (let* ((length (read-little-endian s 2)) + (buffer (make-array length))) + (read-sequence buffer s) + (map 'string #'code-char buffer))))))) + (end-of-file () + nil)))) + +(defun parse-file-location-info (s) + (let ((start (file-position s)) + (total-length (read-little-endian s)) + (end-of-header (read-little-endian s)) + (fli-flags (read-little-endian s)) + (local-volume-offset (read-little-endian s)) + (local-offset (read-little-endian s)) + (network-volume-offset (read-little-endian s)) + (remaining-offset (read-little-endian s))) + (declare (ignore total-length end-of-header local-volume-offset)) + (unless (zerop fli-flags) + (cond + ((logbitp 0 fli-flags) + (file-position s (+ start local-offset))) + ((logbitp 1 fli-flags) + (file-position s (+ start + network-volume-offset + #x14)))) + (concatenate 'string + (read-null-terminated-string s) + (progn + (file-position s (+ start remaining-offset)) + (read-null-terminated-string s)))))) + + (pushnew :asdf *features*) #+sbcl

1 0

[asdf-devel] announce : 1.357
by Gary King 12 Aug '09

12 Aug '09

(small steps forward!) test-op depends on load-op (thanks to rpgoldman(a)sift.info) * Improve error message for bad dependencies * New default is for test-op to depend on load-op * tweak run-program for SBCL so that ACL isn't #+no #+no bothered * tweak write-test-web-page and write-license * tweak some tests Thanks Robert, et. al. for good discussion, etc. -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

1 0

Re: [asdf-devel] About regression tests and libraries
by Tobias C. Rittweiler 12 Aug '09

12 Aug '09

Juan Jose Garcia-Ripoll writes: > What I would like to ask CL developers is to begin shipping regression > tests with their libraries, and perhaps agree on an standard so that > one can programatically check whether a library builds or not. This > feature could be even included in ASDF, asdf-install, etc, just like > "make check" is now a de-facto standad in Autoconf. There's (ASDF:OOS 'ASDF:TEST-OP <system>), and on very recent revisions even (ASDF:TEST-SYSTEM <system>) as an abbeviation. I don't think this has been properly documented in the manual of ASDF yet. I hence CC'd the asdf-devel mailing list so this will hopefully get promoted with the due it deserves. -T.

7 20

[asdf-devel] version numbers
by Daniel Herring 07 Aug '09

07 Aug '09

ASDF has a poorly-defined versioning system. I thought the following link may be of general interest. http://www.dagolden.com/index.php/369/version-numbers-should-be-boring/ There sure are many ways to mess this up. I'm not convinced there are any ways to not mess it up. Related links http://www.gnu.org/software/libtool/manual/html_node/Libtool-versioning.html http://stackoverflow.com/questions/663209/can-someone-explain-about-linux-l… http://www.linux.com/archive/feature/45507?theme=print Given the way ASDF is used today and the rapidly changing ABI of many CL implementations, binary compatibility is a nonexistant issue. Today's CL cares rather about compile-time compatibility. Either way, I almost think the correct solution is to say - each library release will have a unique version number - each library release will have a list of old version numbers for which it is upwards compatible - each dependent library or application will list which versions it was developed for - the "linker" (require or asdf) selects the newest version compatible with the version specified by the dependent This is similar to the libtool scheme, but using general data structures rather than trying to encode everything into the filename. How would asdf respond to two files named X.asd? It doesn't scan all such files looking for the most recent version, does it? (end rambling) - Daniel

2 1

[asdf-devel] Three queries ..
by Greg Bennett 05 Aug '09

05 Aug '09

Good afternoon from Greg Bennett. I am trying to convert some mk-defsystem files to asdf and find myself a bit stuck over source and output files, as well as over asdf conventions about the case of certain text items. My mk-defsystem files contain the two keywords :source-pathname and :binary-pathname As far as I can see, :pathname in asdf plays the role of :source-pathname. In looking for examples, I found the following in the mcclim.asd file: .. ((:module "Tests" :pathname #.(make-pathname :directory '(:relative "Drei" "Tests")) :components .. And indeed there is a subdirectory Tests of the directory Drei which is in the right place relative to the opening directory of the .asd file for :relative to make sense. Q1: Is it possible/permitted to say things like: '(:relative "One" "Two" "Three") to have asdf look two subdirectories down the tree ? I have been unable to find examples of the use of :output-files in asdf. This option seems to provide the role of :binary-pathname in mk-defsystem. Currently, all tour project's binary files are stored in their own tree with its own root but with the structure of the source tree maintained. Q2: Does the syntax of :output-files permit this sort of thing ? I would seem to need a statement of the form #.(make-pathname :directory '(:absolute "Whatever")) since this is a separately rooted tree. Unless I find a positive answer to Q1, in which case, presumably the syntax of :output-files will be similar and I can locate the driving .asd file high enough up in the whole project for everything to be relative. From the code (above) I cut from mcclim.asd it seems that mixed case pathnames are allowed. Q3: Have I misunderstood the on-line manual here ? In discussing components it seems insistent on lower case, which I had assumed asdf would 'demand' everywhere. Thanks for any and all assistance and insights, Cheers /Greg Bennett

3 2

[asdf-devel] announce: 1.356
by Gary King 21 Jul '09

21 Jul '09

> Tue, 21 Jul 2009 13:39:33 -0400 > Gary King > fix my bad in `directory-pathname-p` > * Patch from Joyce Chen for a braindead directory-pathname-p error > on my part * remove debugging statement in check-component-input and documentation improvements... -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

1 0

[asdf-devel] Small fixup of bogus function in directory-pathname-p
by Joyce Chen 21 Jul '09

21 Jul '09

Fare's small fixup of bogus function in directory-pathname-p. ccl complained about x not being used. I don't have commit privileges, so if someone could kindly review the change and commit it :) Thanks, Joyce diff --git a/asdf.lisp b/asdf.lisp index 1e1118d..714c529 100644 --- a/asdf.lisp +++ b/asdf.lisp @@ -448,12 +448,11 @@ ways that the filename components can be missing are for i Note that this does _not_ check to see that `pathname` points to an actually-existing directory." - (let ((null-components (list nil :unspecific ""))) - (flet ((check-one (x) - (not (null (member (pathname-name pathname) null-components - :test 'equal))))) + (flet ((check-one (x) + (member x '(nil :unspecific "") :test 'equal))) (and (check-one (pathname-name pathname)) - (check-one (pathname-type pathname)))))) + (check-one (pathname-type pathname)) + t))) #+(or) ;;test

2 1

Re: [asdf-devel] [cclan-list] How to depend on a system optionally?
by Nikodemus Siivola 21 Jul '09

21 Jul '09

2009/5/18 Robert Goldman <rpgoldman(a)sift.info>: > Tobias C. Rittweiler wrote: >> I've read several times that it's a head ache to configure optional >> dependencies with ASDF. >> >> How true is that? Could we perhaps provide another clause >> :OPTIONALLY-DEPEND-ON in DEFSYSTEM which would load a system only if >> available? Doesn't :WEAKLY-DEPENDS-ON do what you want? Cheers, -- Nikodemus

4 14

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel