asdf-devel May 2011

asdf-devel@common-lisp.net

14 participants
18 discussions

[asdf-devel] source file encoding
by Anton Vodonosov 16 Apr '12

16 Apr '12

Hello. How to specify source files encoding in ASD2? I.e. what value to pass to the :external-format argument of the compile-file? In the old ASDF I did it by (let ((asdf:*compile-file-external-format* #+:clisp charset:cp1251 #+:sbcl :cp1251)) (asdf:operate 'asdf:load-op :mysystem)) But today the variable asdf:*compile-file-external-format* does not exist. Also, it of course would be better to specify the encoding in the .asd file (the system author knows the files encoding, and should care about this, but not the system user). Could you advise me how to do it? Best regards, - Anton

13 61

[asdf-devel] Disabling "built-in" output translation
by Mark Evenson 21 Jun '11

21 Jun '11

ASDF contains some specialized code for ABCL that enable the translation of ASDF systems whose source is packaged into jar files to locate the corresponding object files in ASDF's user cache. In trying to figure out the correct mechanism to allow for "binary" ASDF distribution under ABCL that would include both the source and the fasls in the same jar file, I need to disable the jar file translation mechanism. I expected that invoking DISABLE-OUTPUT-TRANSLATIONS would clear this built-in translation mechanism, but it doesn't seem to do this. Only invoking CLEAR-OUTPUT-TRANSLATIONS seems to actually change the output translation map. To wit: ASDF> (disable-output-translations) ((T T) (#P"/Users/evenson/.cache/common-lisp/abcl-0.26.0-dev-fasl37-macosx-java/**/*.*" T) (#P"/___jar___file___root___/**/*.*" #P"/Users/evenson/.cache/common-lisp/abcl-0.26.0-dev-fasl37-macosx-java/**/*.*") (#P"jar:file:/**/*.jar!/**/*.*" #<FUNCTION TRANSLATE-JAR-PATHNAME {771931F8}>) (T #P"/Users/evenson/.cache/common-lisp/abcl-0.26.0-dev-fasl37-macosx-java/**/*.*")) ASDF> (output-translations) ((#P"/Users/evenson/.cache/common-lisp/abcl-0.26.0-dev-fasl37-macosx-java/**/*.*" T) (#P"/___jar___file___root___/**/*.*" #P"/Users/evenson/.cache/common-lisp/abcl-0.26.0-dev-fasl37-macosx-java/**/*.*") (#P"jar:file:/**/*.jar!/**/*.*" #<FUNCTION TRANSLATE-JAR-PATHNAME {771931F8}>) (T T) (T #P"/Users/evenson/.cache/common-lisp/abcl-0.26.0-dev-fasl37-macosx-java/**/*.*")) ASDF> (disable-output-translations) ((T T) (#P"/Users/evenson/.cache/common-lisp/abcl-0.26.0-dev-fasl37-macosx-java/**/*.*" T) (#P"/___jar___file___root___/**/*.*" #P"/Users/evenson/.cache/common-lisp/abcl-0.26.0-dev-fasl37-macosx-java/**/*.*") (#P"jar:file:/**/*.jar!/**/*.*" #<FUNCTION TRANSLATE-JAR-PATHNAME {771931F8}>) (T #P"/Users/evenson/.cache/common-lisp/abcl-0.26.0-dev-fasl37-macosx-java/**/*.*")) ASDF> (output-translations) ((#P"/Users/evenson/.cache/common-lisp/abcl-0.26.0-dev-fasl37-macosx-java/**/*.*" T) (#P"/___jar___file___root___/**/*.*" #P"/Users/evenson/.cache/common-lisp/abcl-0.26.0-dev-fasl37-macosx-java/**/*.*") (#P"jar:file:/**/*.jar!/**/*.*" #<FUNCTION TRANSLATE-JAR-PATHNAME {771931F8}>) (T T) (T #P"/Users/evenson/.cache/common-lisp/abcl-0.26.0-dev-fasl37-macosx-java/**/*.*")) ASDF> (clear-output-translations) ; No value ASDF> (output-translations) NIL ASDF> Should DISABLE-OUTPUT-TRANSLATIONS actually push that (T T) list into the beginning of that (OUTPUT-TRANSLATION) list or does the API expect that the user use it something like ASDF> (setf (output-translations) (disable-output-translations)) Should ASDF under ABCL strip out the jar translation mechanism as well, or should the ASDF API expect that the user would actual issue a (CLEAR-OUTPUT-TRANSLATIONS)? I confess that I am a bit confused when one would ever use DISABLE-OUTPUT-TRANSLATIONS as opposed to CLEAR-OUTPUT-TRANSLATIONS. Once I understand the ASDF API here a bit better, I will work on the necessary ABCL specific ASDF patches if necessary. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

2 6

[asdf-devel] upcoming asdf 2.016
by Faré 30 May '11

30 May '11

Dear ASDF users, I'd like to release ASDF 2.016 next weekend. Can you powerusers test the current ASDF, and tell me if you find anything wrong? Since 2.015, changes include: * Fix to load-source-op (broken in 2.014.13) (thanks to Martin Simmons) * Fix infinite loops in some .asd containing multiple defsystem's and available both in and out of quicklisp. (Thanks to Nikodemus and Zach) * Fixes for ECL and RMCL (thanks to binghe and Terje Norderhaug) * Fixes for configuration under Windows (many thanks to Martin Simmons) * Minor documentation updates. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Success is getting what you want. Happiness is wanting what you get. — Dale Carnegie

1 0

[asdf-devel] MCL issue
by Chun Tian (binghe) 29 May '11

29 May '11

Hi, ASDF developers Some time ago I can use ASDF with Macintosh Common Lisp, but recently I can't any more. I updated to latest ASDF 2 and compile/load it into MCL (my current version is 6.0, but 5.2.1 has the same problem): ? (pushnew #P"Macintosh HD:Users:binghe:Lisp:usocket:branches:0.5.x:" asdf:*central-registry* :test 'equal) (#P"Macintosh HD:Users:binghe:Lisp:usocket:branches:0.5.x:") ? (asdf:load-system :usocket) > Error: Not an absolute pathname: #4P"home:" > While executing: ASDF::RESOLVE-ABSOLUTE-LOCATION-COMPONENT > Type Command-. to abort. See the Restarts… menu item for further choices. 1 > I don't know what does ASDF::RESOLVE-ABSOLUTE-LOCATION-COMPONENT try to do, but I see a fact that MCL's standard function USER-HOMEDIR-PATHNAME can only return the MCL installation directory but current Mac user's home directory: ? (user-homedir-pathname) #4P"home:" ? (truename *) #P"Macintosh HD:Users:binghe:Lisp:MCL 6.0:" I think above function should return #P"Macintosh HD:Users:binghe:" instead. And I see ASDF depend on USER-HOMEDIR-PATHNAME, so that there's no way to store compiled fasls into "~/.cache/common-lisp" ... Regards, Chun Tian (binghe)

5 25

[asdf-devel] RMCL vs. ASDF
by Pascal Costanza 28 May '11

28 May '11

Hi, Here is what happens in RMCL when the configuration says :inherit-configuration. At startup, I get an error message that says this: ; NOTE: *TERMINAL-IO* was #<CCL::INITIALIZATION-OUTPUT-STREAM #x4453B26>, was reset to #<CCL::TERMINAL-IO #x4A0FE26> . > Error in process Startup: File #4P"home:" does not exist. > While executing: TRUENAME This is triggered by the function user-homedir. While RMCL is still in debug mode for this error, (truename (user-homedir-pathname)) fails. However, afterwards, it returns correctly (for some value of "correct"): ? (truename (user-homedir-pathname)) #P"Macintosh HD:Users:costanza:lisp:RMCL 5.2.1:" My guess is that user-homedir-pathname returns #4P"home:" as a constant value, even before the logical pathname translation for it is defined during startup. The deeper problem is, again, that the notion of a home directory doesn't make sense in RMCL (at least not by default). If ASDF wants to have a notion of a home directory, it should be a configurable parameter of ASDF that in most systems can indeed default to the result of (user-homedir-pathname). But it should be possible to explicitly set it in some way before ASDF decides to go looking for it. (This would make ASDF more robust for potential future CL systems that may not have a notion of a home directory either, however unlikely this may be.) Pascal -- Pascal Costanza The views expressed in this email are my own, and not those of my employer.

2 2

[asdf-devel] Logical pathnames....
by Robert Goldman 22 May '11

22 May '11

FWIW, I am just working on a project that has some CL people and some non-CL people. The fact that pathnames with underscores (that C programmers, e.g., are fond of) break decoding when they appear in logical pathnames is a real stinker. This alone is almost enough to rule out of court the use of logical pathnames, IMO.... Cheers, r

2 4

Re: [asdf-devel] Tutorial ASDF(?)
by Ernst van Waning 21 May '11

21 May '11

Dear Robert, >> However, I have one question: what is the reason that these >> output translations are apparently not applied to the .asd >> files? The way I understand my output-translations, I have >> globally specified that all fasls are in an >> implementation-specific directory just below my source >> files. For me, .asd files are just source files, so why not >> place them where the other fasls are written? > Not sure I fully understand. As you say, the .asd files are just > source files, and they are never compiled, so there is no need > to do any output translations for them. > I may not have fully followed the question.... concerning the .asd files, I use cl path/to/..asd in the REPL and both sbcl and acl try to find fasls for them. If there is no corresponding fasl, they write one. At present, I do an explicit (load #P"path/to/system.asd") to prevent Lisp from writing fasls. So, the question comes from a habit developed over the years: why aren't defsystem files trated the same way as source files, i.e., treated according to what is specified in asdf-output-translations.conf? Hopefully this explains a bit of the backgrond of my question. Further comments later. Kind regards, good weekend, Ernst asdf-devel-request(a)common-lisp.net schreef op vr 20-05-2011 om 12:00 [-0700]: > Re: Tutorial ASDF(?)

7 10

[asdf-devel] Tutorial ASDF(?)
by Ernst van Waning 20 May '11

20 May '11

After some unplanned adventures asdf writes and reads fasls from implementation-specific directories. It was simple and the code is in the manual: simply put (:output-translations (:root (:root :**/ :implementation-type :*.*.*)) :inherit-configuration) in ~/.config/common-lisp/asdf-output-translations.conf and it works like magic. As :root is actually mentioned as magic in the manual, you can imagine how glad I am to have offered to contribute tutorial stuff :-) I will go through the code to try to demystify it for myself and try to find the words to explain it. Being a noob with configurations, maybe I should even try to explain this topic in the case of asdf. However, I have one question: what is the reason that these output translations are apparently not applied to the .asd files? The way I understand my output-translations, I have globally specified that all fasls are in a implementation-specific directory just below my source files. For me, .asd files are just source files, so why not place them where the other fasls are written? Hoping to hear, Kind regards, Ernst

2 1

Re: [asdf-devel] MCL issue
by Chun Tian (binghe) 19 May '11

19 May '11

Great, then why not replace ASDF's function user-homedir into this one: (defun* user-homedir () #+mcl (ccl::findfolder #$kuserdomain #$kCurrentUserFolderType) #-mcl (truenamize (pathname-directory-pathname (user-homedir-pathname)))) I've made a patch (in attach), include above new definition and some notes. I hope Faré could merge it. We still love MCL even though it has so much difference from other modern CL platforms. --binghe 在 2011-5-19，07:05， Terje Norderhaug 写道： > On May 17, 2011, at 10:26 PM, Chun Tian (binghe) wrote: >>> Some time ago I can use ASDF with Macintosh Common Lisp, but recently I can't any more. >> >> I found a workaround for myself: >> >> (in-package :asdf) >> >> (defun user-homedir () >> #P"Macintosh HD:Users:binghe:") >> >> with above code loaded as a ASDF patch, I can load other packages well. > > Alternatively, when using ASDF with MCL, bind ccl::*user-homedir-pathname* to the pathname for the ~/ home directory of the current user: > > (ccl::findfolder #$kuserdomain #$kCurrentUserFolderType) > > The ccl::user-homedir-pathname function returns the value of ccl::*user-homedir-pathname* when called with no arguments. > > I have made a note about it in the ASDF section of <http://code.google.com/p/mcl/wiki/Portability>. > > -- Terje Norderhaug > terje(a)in-progress.com > > > > >

2 4

[asdf-devel] Tutorial for asdf?
by Ernst van Waning 18 May '11

18 May '11

Robert, As you see I do follow this thread since some time :-) Thank you for your answer. Tomorrow I will look into the asdf-code again and see what I will discover. I'll keep you informed. Kind regards, Ernst asdf-devel-request(a)common-lisp.net schreef op di 17-05-2011 om 14:40 [-0700]: > Is there a tutorial for asdf?

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel May 2011