asdf-devel December 2014

asdf-devel@common-lisp.net

5 participants
3 discussions

[Asdf-devel] Registering preloaded systems for Quicklisp/ASDF
by Dave Cooper 05 Jun '15

05 Jun '15

Hi, I know this has been discussed, but what is currently the best practice for registering a preloaded system after loading Quicklisp? That is, I have a pre-built image with some Quicklisp/ASDF systems in it, which were loaded through so-called monolithic-fasls (now known as compile-bundles). So the pre-built image doesn’t itself have ASDF or Quicklisp. A downstream user then loads Quicklisp and ASDF (I take steps to ensure that they are loading the matching version of ASDF and Quicklisp as was used to build the image). Now I need to do something to tell Quicklisp and ASDF that certain systems are already loaded in this image, so it won’t try to re-load them as depended-upon systems. In this specific case, I don't want it to try to fetch and reload Gendl when the user does (ql:quickload ...) on an application which :depends-on :gendl (because gendl is already built into this image). asdf/find-system:register-preloaded-system seems like it should be the answer if we’re talking about plain ASDF, because it will prevent ASDF from raising a “missing-component” error for the system in question, if some other system :depends-on it and yet no source code is found. But in my case I can’t guarantee that “no source code is found.” The source might be there in the quicklisp dist directory. So apparently I need something stronger than register-preloaded-system? Or something else? -- My Best, Dave Cooper

3 21

[Asdf-devel] :homepage :bug-tracker :mailto :long-name :source-control
by Faré 12 Mar '15

12 Mar '15

Shamed by a tweet by @hexstreamsoft, I made a very minimal attempt at documenting the existence since ASDF 2.27 of the :homepage :bug-tracker :mailto :long-name :source-control keywords to defsystem. I will leave for someone else to make real manual entries out of the information. NB: AFAIR, none of the types of these arguments is enforced by ASDF. Good luck! —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Efficiency is doing things right; effectiveness is doing the right things. — Peter Drucker

3 5

[Asdf-devel] Program with metaclass on MKCL.
by D. Martinez 05 Dec '14

05 Dec '14

Hello. Being new to "serious" CL programming I am hitting a brick wall right now in one CLOS project. After some time of infructuous searching I cannot find the source of my problem, which may be of either MKCL or ASDF but I lack the knowledge to debug this. Mr. JCB, who I have seen active on this list, may (hopefully!) be able to shed some light on the issue. The bug I encounter happens when I load the project by the means of ASDF. I can not reproduce it otherwise. It is triggered by a use of a custom metaclass, and it suggests that a file is loaded more times than it should. I have narrowed down the problem to a small program, so here it is: ;;;; hello.asd (asdf:defsystem #:hello :description "Describe hello here" :author "Your Name <your.name(a)example.com>" :license "Specify license here" :serial t :components ((:file "package") (:file "a")) :depends-on ()) ;;;; package.lisp (defpackage #:hello (:use #:cl)) ;;;; a.lisp (in-package #:hello) (defclass A-class (standard-class) ()) (defclass A (standard-object) () (:metaclass A-class)) * Case 1: load with MKCL only: mkcl -load package.lisp -load a.lisp OK, works as expected. * Case 2: compile with MKCL only and load: mkcl -load package.lisp -compile a.lisp OK, it produces a fas (shared library). I load it from REPL. It works. * Case 3: load or build with ASDF It fails (at the definition of class A). The error message is this: -> When redefining a class, the metaclass can not change.. It acts as if a.lisp was actually loaded twice. Same error as loading a twice in a row, as by this command. mkcl -load package.lisp -load a.lisp -load a.lisp My ASDF command: (asdf:operate 'asdf:load-op :hello) Same problem with compile-op and program-op. However, load-source-op does work without problem. (I always make sure to clear cache between asdf operations) I will happily provide more specific info at request. The bug occured on MKCL 1.1.9 and 1.1.10 git with bundled ASDF.

4 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel December 2014