Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Generally these system tools should allow that. All you need is the system description and the FASL files. The system tool should then use the FASL files for loading. One only needs to make sure that it does not have a hard dependence on some source file.</p> <p>This way software has delivered in the Lisp world for decades (> 30 years). There is nothing wrong with that approach. If a particular tool (here ASDF, but there are others) has a problem with that, one should complain to the authors.</p> <p>If you have a practical problem with it, you should discuss it on the ASDF mailing list or post a question here. Do you have a practical problem with it?</p> <p>This will not help you directly, but it may give you some hints how a system tool usually works|ed.</p> <p><strong>Example with LispWorks 6 and its own DEFSYSTEM</strong></p> <p>We have three files in a directory FOO:</p> <pre><code>RJMBA:foo joswig$ ls -l -rw-r--r-- 1 joswig admin 13 22 Jul 20:42 a.lisp -rw-r--r-- 1 joswig admin 14 22 Jul 20:42 b.lisp -rw-r--r-- 1 joswig admin 331 22 Jul 20:41 system.lisp </code></pre> <p>system.lisp contains the following system description:</p> <pre><code>(defvar *foo-directory* (make-pathname :name nil :type nil :directory (pathname-directory *load-pathname*) :defaults *load-pathname*)) (defsystem foo (:default-pathname *foo-directory*) :members ("a" "b")) </code></pre> <p>Above sets the <code>*foo-directory*</code>pathname based on the pathname of the loaded file. Thus we can set a real absolute pathname, but don't have to manually specify it. Alternatively we could use relative pathnames - this depends on what one wants to use. I chose this to show how to set up an absolute pathname automagically.</p> <p>Now I load this file into LispWorks then compile the system:</p> <pre><code>CL-USER 12 &gt; (compile-system 'foo) ;;; Compiling file /Lisp/foo/a.lisp ... ;;; Safety = 3, Speed = 1, Space = 1, Float = 1, Interruptible = 1 ;;; Compilation speed = 1, Debug = 2, Fixnum safety = 3 ;;; Source level debugging is on ;;; Source file recording is on ;;; Cross referencing is on ; (TOP-LEVEL-FORM 0) ; (TOP-LEVEL-FORM 1) ;; Processing Cross Reference Information ;;; Compiling file /Lisp/foo/b.lisp ... ;;; Safety = 3, Speed = 1, Space = 1, Float = 1, Interruptible = 1 ;;; Compilation speed = 1, Debug = 2, Fixnum safety = 3 ;;; Source level debugging is on ;;; Source file recording is on ;;; Cross referencing is on ; (TOP-LEVEL-FORM 0) ; (TOP-LEVEL-FORM 1) ;; Processing Cross Reference Information (FOO) </code></pre> <p>We have created two fasl files.</p> <p>Now I copy the system.lisp file and the fasl files into a new directory:</p> <pre><code>RJMBA:Lisp joswig$ mkdir bar RJMBA:Lisp joswig$ cp foo/system.lisp bar/system.lisp RJMBA:Lisp joswig$ cp foo/a.64xfasl bar/a.64xfasl RJMBA:Lisp joswig$ cp foo/b.64xfasl bar/b.64xfasl </code></pre> <p>Now I'll start a fresh LispWorks in the <code>b</code>directory, load the system.lisp file and then load the system:</p> <pre><code>RJMBA:Lisp joswig$ cd bar RJMBA:bar joswig$ lispworks LispWorks(R): The Common Lisp Programming Environment Copyright (C) 1987-2009 LispWorks Ltd. All rights reserved. Version 6.0.0 User joswig on RJMBA.local ... CL-USER 1 &gt; (load "system.lisp") ; Loading text file /Lisp/bar/system.lisp ;; Creating system "FOO" #P"/Lisp/bar/system.lisp" CL-USER 2 &gt; (load-system 'foo) ; Loading fasl file /Lisp/bar/a.64xfasl "a" ; whatever the file does ; Loading fasl file /Lisp/bar/b.64xfasl "b" ; whatever the file does (FOO) </code></pre> <p>Done and works.</p> <p>Additionally this can be done with relative directories or so-called logical pathnames. Logical pathnames have a mapping from some pathname to a physical pathname, thus enable to use system-independent pathnames - independent from architecture, OS and directory structures. This gives an additional level of independence from the specific deployment scenario.</p>
    singulars
    1. This table or related slice is empty.
    1. POUsing asdf can I load a system providing only previously made FASLs
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRainer Joswig
    1. USRainer Joswig
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYes and I posted it: I want to know if ASDF is supposed to be able to load FASLs only. As I understand this issue has not come up often, which is a bit surprising to me. Fare says that this hasn't been though of, so I guess I have to take a shot at an extension maybe or a hack like the one he proposes. So to answer your question, whether I have a practical problem with ASDF, depends on whether the function of ASDF I am asking for should be there, and this depends on the definition of "should". You say in your comment, that it should. Fare implies that it wasnt designed for it.
      singulars
      1. PO
      1. USParalife
    2. CO@Paralife: see my edit above for an example with the DEFSYSTEM from LispWorks.
      singulars
      1. PO
      1. USRainer Joswig
    3. COthanks, I understand. I guess I will try to mess with asdf to see why it seems to demand .lisp files even when .fasl files exist. I say "seems" because it may be my mistake. Maybe somewhere in my system I implicitly create a dependency on a lisp source file that I am not aware of. I will try a very simple defsystem like yours to verify that this is not the case.
      singulars
      1. PO
      1. USParalife
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload