Re: "non-local" components in asdf

james anderson <[email protected]> writes:

> i don't understand how to succinctly express non-local components. is
> there a way to do this, or does asdf argue against them? by
> "non-local" i mean a file component which is not in the directory
> designated by the path in effect for its module. i tried to just go
> ahead and give such a component a relative pathname as a name, but
> that did not have the desired effect.

Component names are not pathname designators, or anything like that,
so it's not too surprising it didn't work.  Pathnames for components
are computed using an excitingly twisted bunch of methods which, in
the absence of any information to the contrary, end up defaulting the
pathname from the component name.

Bits of this mechanism can be overridden.  Probably the easiest thing
to do in your situation is specify the component pathname explicitly,
using the :pathname option.  So, for example

  (:file "system-stty" :pathname #p"/usr/include/stty.h"
         :depends-on ("defpackage"))

(this should be correct, but it's from memory, so please try it and
let the list know).  Note that you need to give the component a name as
well as a pathname, and the name is the thing that will be used
e.g. if later components want to depend on it.

If the component is a module, strange things will probably happen if
you set the pathname to something that's not a directory.

Hope this helps

-dan

-- 

   http://www.cliki.net/ - Link farm for free CL-on-Unix resources 


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com