I was given some code to extract all of the source files that a system requires for building.
It gave me what you see below:
How would I get the full pathname of one of these CL-SOURCE-FILE objects?
saw file: #<CL-SOURCE-FILE "cleavir-io" "packages" @0x113ac3518> saw file: #<CL-SOURCE-FILE "cleavir-io" "io" @0x113bacdd8> saw file: #<CL-SOURCE-FILE "cleavir-meter" "packages" @0x1152baf68> saw file: #<CL-SOURCE-FILE "cleavir-meter" "meter" @0x1153b4068> saw file: #<CL-SOURCE-FILE "cleavir-ast" "packages" @0x115d73ba8> saw file: #<CL-SOURCE-FILE "cleavir-ast" "general-purpose-asts" @0x115f98b08> saw file: #<CL-SOURCE-FILE "cleavir-ast" "fixnum-related-asts" @0x115a1a978> saw file: #<CL-SOURCE-FILE "cleavir-ast" "float-related-asts" @0x11549ce78> saw file: #<CL-SOURCE-FILE "cleavir-ast" "cons-related-asts" @0x115027ab8> saw file: #<CL-SOURCE-FILE "cleavir-ast" "standard-object-related-asts" @0x115196838> saw file: #<CL-SOURCE-FILE "cleavir-ast" "array-related-asts" @0x115303658> saw file: #<CL-SOURCE-FILE "cleavir-ast" "graphviz-drawing" @0x1153fdec8> saw file: #<CL-SOURCE-FILE "cleavir-ast" "map-ast" @0x114073f68> saw file: #<CL-SOURCE-FILE "cleavir-ast-transformations" "packages" @0x113d2ffb8> saw file: #<CL-SOURCE-FILE "cleavir-ast-transformations" "clone" @0x113e0ec48> saw file: #<CL-SOURCE-FILE "cleavir-ast-transformations" "replace" @0x113ed67e8> saw file: #<CL-SOURCE-FILE "cleavir-ast-transformations" "hoist-load-time-value" @0x113f9bba8> saw file: #<CL-SOURCE-FILE "cleavir-primop" "packages" @0x1140c5c98> saw file: #<CL-SOURCE-FILE "cleavir-internationalization" "packages" @0x1144b0928> … Deleted another 100 entries ...
Christian Schafmeister
On Sat, Mar 21, 2015 at 11:27 PM, Christian Schafmeister chris.schaf@verizon.net wrote:
I was given some code to extract all of the source files that a system requires for building.
It gave me what you see below:
How would I get the full pathname of one of these CL-SOURCE-FILE objects?
asdf:component-pathname
The manual could admittedly explain these things better, but oh well, at this point, I'll direct you to using apropos and to browsing the source-code, and I'll invite you to write the missing pieces of the manual.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org There is only one way to console a widow. But remember the risk. — Robert Heinlein, "Time Enough For Love"
Faré wrote:
On Sat, Mar 21, 2015 at 11:27 PM, Christian Schafmeister chris.schaf@verizon.net wrote:
I was given some code to extract all of the source files that a system requires for building.
It gave me what you see below:
How would I get the full pathname of one of these CL-SOURCE-FILE objects?
asdf:component-pathname
The manual could admittedly explain these things better, but oh well, at this point, I'll direct you to using apropos and to browsing the source-code, and I'll invite you to write the missing pieces of the manual.
I have just pushed a version of the ASDF manual that adds documentation for COMPONENT-PATHNAME.
Currently it's only in the git repo.
cheers, r
-
Christian Schafmeister -
Faré -
Robert P. Goldman