Márcio Faustino <marciombfaust...@gmail.com> writes:

> Hi,
>
> Whenever I install a package via Quicklisp, "xmls" for example, when it is 
> compiled the object files (*.fas, *.obj) are placed at:
> C:\Users\marcio\AppData\Roaming\common-lisp\cache\ecl-11.1.1-win-x86\C\Users\marcio\quicklisp\dists\quicklisp\software\s-xml-20101006-http\src
>
> It seems there's a problem there, because the drive letter is used as if it 
> was a directory. For that same package the source files are located at:
> C:\Users\marcio\quicklisp\dists\quicklisp\software\s-xml-20101006-http\src
>
> Is this an issue with ECL or Quicklisp? I'm using ECL 11.1.1, with Visual 
> Studio 2005, on Windows 7 64-bit.

ASDF2 introduced a system of separating FASL files from source files.
It's similar similar to the older asdf-binary-locations library. ASDF2
constructs the fasl pathname by translating the source pathname in a
particular way.

It's described in section 3.3 of the ASDF manual - see
http://common-lisp.net/project/asdf/asdf.html for details.

If you don't want the feature, you can turn it off with
(asdf:disable-output-translations).

Zach

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list

Reply via email to