asdf-devel February 2011

asdf-devel@common-lisp.net

6 participants
6 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] moving old to new asdf
by Antony 04 Apr '11

04 Apr '11

Hi I have tried to use the newer version of asdf (been using 1.x for long time). I put in (asdf:initialize-source-registry (list :source-registry (list :tree #P"C:/git/") :inherit-configuration)) (asdf:initialize-output-translations (list :output-translations (list "C:/temp/.fasl/") :inherit-configuration )) I like all of my fasls to go under appropriate subdirs of C:/temp/.fasl/ But, they are all going to c:/Users/Antony/AppData/Roaming/common-lisp/cache... I do not want to create any config files. What code would do that. -Antony

3 2

[asdf-devel] System naming conventions
by David Wang 03 Apr '11

03 Apr '11

Hello, QUESTION: 1. Could someone add a system naming convention section to the ASDF documentation, to help future users with similar problems? 2. If someone knows whether my rules-of-thumb (below) are right or wrong, let me know. EXPLANATION: I've been porting a large code base from Franz/Allegro's defsystem to ASDF 2.012. I was originally writing the .ASD files on Windows and recently tried testing the build with the same .ASD files on the Linux variant, Fedora 14, but had some problems with various missing-components. I realized the problem had something to do with the treatment of case in filenames, and ended up fixing problem by examining the ASDF code and inventing some rules-of-thumb: 1. When using Strings to name a system, make sure the filename of the ASD file, the name of the system defined in that file, and any uses of the system-name in other ASD files all have the same case. i.e.: In the file "SyStEmA.asd": (asdf:defsystem "SyStEmA" ...) In the file "SyStEmB.asd" (asdf:defsystem "SyStEmB" :depends-on ("SyStEmA")) 2. If you ever want to use a Symbol to name a system, make sure the filename of the ASD file is all lowercase. The name of the system defined in that file and any uses of the system-name in other ASD files should either be a symbol or a lowercase string. In the file "systema.asd": (asdf:defsystem #:SYSTEMA ...) In the file "systemb.asd" (asdf:defsystem "systemb" :depends-on ("systema")) I don't know if they are correct for all combinations of OSes, CL-variants, and system names, but from my limited knowledge of ASDF's code I think they'll work well. - Thanks! - David Wang P.S. Thanks for helping develop ASDF. I couldn't imagine a [Lisp] world in which it didn't exist.

2 1

[asdf-devel] (asdf:load-system :iterate) loads :iterate-pg & :iterate-tests
by Frank 02 Apr '11

02 Apr '11

Hello there, I've been using iterate for a short while. I noticed that it always loads :iterate-pg and :iterate-tests on (asdf:load-system :iterate). Do those modules have to be pulled in for just the basic :iterate part? I'm using ccl-1.6 and the quicklisp iterate version. Thanks Frank

2 1

[asdf-devel] ASDF2: run-shell-command for clisp: what is the correct :output?
by Mirko Vukovic 22 Feb '11

22 Feb '11

Hello, The asdf:run-shell-command for clisp is specified to use the output as terminal. That makes its output unavailable to clisp. Instead, one should have something like this: (read (ext:run-shell-command command :output :stream :wait t)) I am cross-posting this to the clisp mailing list. Folks there know much more about this than I do. Mirko

2 1

[asdf-devel] Minor simplification
by Juan Jose Garcia-Ripoll 06 Feb '11

06 Feb '11

Right now there are hooks in ASDF which are used by ECL in a perhaps too complicated way. More precisely, ECL requires to make an object file and a FASL file out of every compiled file, so that other operations (LOAD-FASL-OP, monolithic building, standalone executables, etc) become easier. Right now this is done using an :AFTER method on PERFORM. I suggest this patch (already in ECL's tree) which removes that method, removes the upgradability hacks and insteads wraps around COMPILE-FILE* (which now becomes redefinable at run time). Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com

3 14

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel February 2011