asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

[asdf-devel] Replace *DEFAULT-PATHNAME-DEFAULTS*
by Thomas M. Hermann 24 Dec '10

24 Dec '10

There are several places where ASDF relies on *DEFAULT-PATHNAME-DEFAULTS* to provide a default path. The value of this variable is "An implementation-dependent pathname, typically in the working directory that was current when Common Lisp was started up." [ http://www.lispworks.com/documentation/HyperSpec/Body/v_defaul.htm ] I think it would be better to define a variable, like asdf:*pathname-defaults*, asdf:*registry-pathname-defaults, etc., that is explicitly set using feature expressions. The biggest argument for not making this change is that some systems may rely on the value of *DEFAULT-PATHNAME-DEFAULTS*. I don't think it would be too difficult to correct those systems, but admit that it might not be worth the effort. My motivation for making this change was prompted by the function default-source-registry. It creates a :directory entry in the source registry that is constructed from the TRUENAME of the value returned by *DEFAULT-PATHNAME-DEFAULTS*. The first point is that the value *DEFAULT-PATHNAME-DEFAULTS* is implementation dependent. For the cases I tested using CCL 1.6 and LispWorks 6.0.1 on Windows 7, the value is the empty path #P"". The second point is that the pathname returned by TRUENAME when it is given the empty path is implementation dependent. In the case of CCL, (TRUENAME #P"") returns the working directory that was current when Common Lisp was executed. In the case of LispWorks, (TRUENAME #P"") returns #P"C:/Windows/system32/". This may be the working directory that was current when LispWorks was started, but it is clearly not a desirable place for ASDF systems. In either case, the result is a :directory entry in the source registry that is not well defined. I think it is better to have the default pathname well defined. Thank you, ~ Tom ---------------------------------------------------------------- Thomas M. Hermann Odonata Research LLC http://www.odonata-research.com/ http://www.linkedin.com/in/thomasmhermann

3 5

[asdf-devel] textual representation of plan, asdf:explain
by Tobias C Rittweiler 15 Dec '10

15 Dec '10

What is the way to get a textual representation of the plan of a system? I would have thought that this is what ASDF:EXPLAIN is for, but grepping through asdf.lisp did not make me believe that's true. Also, is there some fundamental reason why (asdf:explain 'asdf:compile-op :system-name) could not be the interface for ASDF:EXPLAIN? -T.

2 1

[asdf-devel] ASDF Git: please remove tags, etc.
by Faré 15 Dec '10

15 Dec '10

Apparently, for quite a few months (did it start with me or with gwking?), we've been misusing git tag -f FOO as if the latest version of the tag would be propagated when we push, whereas it isn't - on purpose - since tags are meant to be constant. I invite all committers to run the following Makefile target to erase git tags that have been misused this way, as well as an obvious typo: make fix-local-git-tags (That would be mostly me and rpg). It's not a bad thing to do if you're using ASDF from git, even without being a committer. To future maintainers: I have also written a script bin/bump-version.sh to bump the version. For users, since 2.011, we've improved the source-registry and output-translations configuration DSLs, given examples in the documentation of how to configure AOT to store things in a subdirectory of the current one, and made, fix a bug in corner cases, etc. I intend to release 2.012 before the end of the year. Will hopefully be my last. (I've said that in the past.) I took over the asdf-announce mailing-list for announcing releases. I invite Lisp implementers, distribution makers, etc., to subscribe to it (rather than to this mailing-list) to know when to update their software. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] No man would listen to you talk if he didn't know it was his turn next. — Edgar Watson Howe

1 0

[asdf-devel] Store all fasl files in a relative directory to the .asd file
by Jianshi Huang 08 Dec '10

08 Dec '10

Hi, Could anybody show me what's the recommended approach to make all the compiled files to be stored in a relative directory, either in .asd file or by lisp code? I'm using ASDF 2.010 Say, if I have a project in $HOME/prj/ with prj.asd defined, and all it's dependencies in $HOME/prj/lib/. When I load the project in sbcl, I want all the compiled fasl files to be stored under $HOME/prj/fasl/sbcl/. I can only find configuration files in manual and am not sure about the usage of other APIs. An pseudo-code example would be very helpful. P.S. I was doing (setf asdf::*user-cache* ...) and it worked fine in 2.009, but it seems not working in 2.010. -- Jianshi Huang

3 3

[asdf-devel] Problem with time skew
by Sid H 05 Dec '10

05 Dec '10

Hi, I'm using ASDF on CCL running on a TI ARM Cortex A8 processor with Linux. I have a very simple hello world system written that I'm trying out. When I try to load, I find that that find-system is called continuously and this never ends. I see the following on my slime window. CL-USER> (asdf:oos 'asdf:load-op 'cl-syslink) ; Loading system definition from /home/root/ccl/tools/cl-syslink.asd into # <Package "ASDF0"> ; Registering #<SYSTEM "cl-syslink"> as cl-syslink ; Loading system definition from /home/root/ccl/tools/cl-syslink.asd into # <Package "ASDF1"> ; Loading system definition from /home/root/ccl/tools/cl-syslink.asd into # <Package "ASDF2"> .... On investigation I found that the universal-time stored in *defined-systems* is just slightly behind the file-write-date. The dates I see are in-memory: 3499707641 and safe-file-write-date 3500387179. I'm not sure why the time skew exists but I can always abort the recursive calls after a few times and then use the system. Any thoughts on this? Is this seen on any other implementation/OS? --Sid

2 4

[asdf-devel] Just closed out the HERE-DIRECTIVE topic branch
by Robert Goldman 02 Dec '10

02 Dec '10

I have merged into master (with much assistance from Faré) and tested. Tests were run on ABCL, ACL (ANSI and Modern), CCL and SBCL on Mac OS X. If someone can test on Linux and Windows, I'd be grateful. Also LispWorks on any platform.... Cheers, r

1 0

[asdf-devel] New version of the here-directive topic branch pushed
by Robert Goldman 29 Nov '10

29 Nov '10

Note that this is not a fast-forward push, because it was rebased on top of Faré's latest version of ASDF on master. cheers, r

1 0

[asdf-devel] Pushed :here-directive topic branch
by Robert Goldman 29 Nov '10

29 Nov '10

This branch has patches that add the :here directive to Faré's configuration DSL. This allows for configuration files to have contents like: (:source-registry (:tree (:here "src/lisp/")) (:tree (:here "extlib/lisp")) (:directory (:here "outlier/"))) ... which means if, for instance, I have a source repo with a complex set of directories and .asd files, I can commit a .conf file into the repo and tell you just to "source" it through ASDF, and you'll automagically see all the .asd files in the directory. This is particularly useful when you don't want people to have to have ASDF grovel over the entire source tree in their working directories. I have found this to be desirable, as I often work in source trees that contain not just lisp code, but Java code (which generates /very/ big trees to search) and data files. I think this meets Faré's design principle that "everyone can specify what he knows, but doesn't have to specify what he doesn't know." I am checking this in on a topic branch for easy inspection before inclusion (I hope). The new feature of the DSL is also documented in the texinfo manual. Cheers, r

4 8

[asdf-devel] ASDF 2.011
by Faré 29 Nov '10

29 Nov '10

Dear Lispers, I'm pleased to announce the release of ASDF 2.011. As compared to ASDF 2.010, it only sports a series of minor changes, which I think is sign of ASDF 2 becoming mature: * minor portability tweaks, to make GCL (2.010.1) and Allegro (2.010.5) happy * minor fixes, to an error in error (2.010.8) * minor API cleanups, exporting symbol operation-description (2.010.6) and accepting keywords as component class names (2.010.3) * minor internal refactoring (2.010.4, 2.010.7 + 2.010.9) * minor improvement in dealing with incompatibility, refusing to run if asdf-binary-locations was loaded as it only works with asdf 1, with useful error message (2.010.7) * minor improvements in compatibility with cl-launch (2.010.2) and xcvb (2.010.4) If you missed it, 2.010 had a notable speedup in addition to minor fixes. It would be very nice of vendors to update the version of ASDF they ship with their respective implementations, or to start shipping it when they don't do it yet (LispWorks, SCL; Corman, GCL - if they are still being developed). PS: I think we should create an asdf-announce mailing-list so that vendors may subscribe to it and only get traffic relevant to releases. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Every technique is first developed, then used, important, obsolete, normalized, and finally understood.

1 0

[asdf-devel] poor error reporting in ASDF
by Cyrus Harmon 23 Nov '10

23 Nov '10

Dear ASDF developers, While trying to load a project of mine that depends on alexandria on a box that didn't have alexandria installed, I got the attached error message. It would be nice if there were better reporting letting one know that the dependency was not satisfied. thanks, Cyrus There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION ASDF:COMPONENT-NAME (1)> when called with arguments (#:ALEXANDRIA). [Condition of type SIMPLE-ERROR] Restarts: 0: [RETRY] Retry calling the generic function. 1: [ABORT] Return to sldb level 1. 2: [RETRY] Retry SLIME REPL evaluation request. 3: [*ABORT] Return to SLIME's top level. 4: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" RUNNING {1002FA0451}>) Backtrace: 0: ( ) 1: (SB-PCL::CALL-NO-APPLICABLE-METHOD ) 2: (ASDF::COMPONENT-FIND-PATH ) 3: ( ) 4: ( ) 5: (SB-IMPL::STRINGIFY-OBJECT ) 6: (PRINC-TO-STRING ) 7: (SWANK::FORMAT-RESTARTS-FOR-EMACS) 8: (SWANK:DEBUGGER-INFO-FOR-EMACS 0 20) 9: (SWANK::CALL-WITH-BINDINGS ) 10: (SWANK::SLDB-LOOP 1) 11: ( ) 12: (SWANK::DEBUG-IN-EMACS ) 13: (SWANK:INVOKE-SLIME-DEBUGGER ) 14: (SWANK-BACKEND::CALL-WITH-BREAK-HOOK ) 15: ( ) 16: (SWANK:SWANK-DEBUGGER-HOOK ) 17: (SB-DEBUG::RUN-HOOK *DEBUGGER-HOOK* ) 18: (INVOKE-DEBUGGER ) 19: (ERROR ASDF:MISSING-DEPENDENCY :REQUIRED-BY :REQUIRES ) 20: (ASDF::%DO-ONE-DEP ASDF:COMPILE-OP NIL) 21: (ASDF::DO-ONE-DEP ASDF:COMPILE-OP NIL) 22: ( ASDF:COMPILE-OP NIL) 23: (ASDF::DO-DEP ASDF:COMPILE-OP ) 24: ( ) 25: (ASDF::DO-ONE-DEP ASDF:COMPILE-OP NIL) 26: ( ASDF:COMPILE-OP NIL) 27: (ASDF::DO-DEP ASDF:COMPILE-OP ) 28: ( ) 29: (ASDF::DO-ONE-DEP ASDF:COMPILE-OP NIL) 30: ( ASDF:COMPILE-OP NIL) 31: (ASDF::DO-DEP ASDF:COMPILE-OP ) 32: ( ) 33: ( ) 34: ( ASDF:LOAD-OP CHEMICL) ...

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