Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
A
asdf
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Pascal J. Bourguignon
asdf
Commits
ad43c36f
Commit
ad43c36f
authored
Sep 16, 2016
by
Robert Goldman
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Expand shell-friendly syntax for output translations.
parent
b12a48c5
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
18 additions
and
11 deletions
+18
-11
doc/asdf.texinfo
doc/asdf.texinfo
+18
-11
No files found.
doc/asdf.texinfo
View file @
ad43c36f
...
...
@@ -4233,23 +4233,30 @@ or namestring in an @code{:include} directive, e.g.:
@node Output Shell
-
friendly syntax for configuration, Semantics of Output Translations, Output Configuration Directories, Controlling where ASDF saves compiled files
@section Shell
-
friendly syntax for configuration
When considering environment variable @code
{
ASDF
_
OUTPUT
_
TRANSLATIONS
}
ASDF will skip to the next configuration if it's an empty string.
It will @code
{
READ
}
the string as an SEXP in the DSL
if it begins with a paren @code
{
(
}
and it will be interpreted as a list of directories.
Directories should come by pairs, indicating a mapping directive.
When processing the environment variable
@code
{
ASDF
_
OUTPUT
_
TRANSLATIONS
}
:
@itemize
@item ASDF will skip to the next configuration if it's an empty string.
@item ASDF will @code
{
READ
}
the string as an SEXP in the DSL, if it
begins with a parenthesis @code
{
(
}
.
@item Otherwise ASDF will interpret the value as a list of directories
(
see below
)
.
@end itemize
In the directory list format,
directories should come in pairs, each pair indicating a mapping directive.
Entries are separated
by a @code
{
:
}
(
colon
)
on Unix platforms
(
including
cygwin
)
,
by a @code
{
:
}
(
colon
)
on Unix platforms
(
including
Mac and cygwin
)
, and
by a @code
{
;
}
(
semicolon
)
on other platforms
(
mainly, Windows
)
.
The magic empty entry,
if it comes in what would otherwise be the first entry in a pair,
indicates the splicing of inherited configuration.
If
it comes as the second entry in a pair
,
it indicates that the directory
specified first
is to be left untranslated
If
the second entry in a pair is empty
,
it indicates that the directory
in the first entry
is to be left untranslated
(
which has the same effect as if the directory had been repeated
)
.
Thus @code
{
"
/
foo:
/
bar::
/
baz:"
}
means that
For example, @code
{
"
/
foo:
/
bar::
/
baz:"
}
means that
things under directory @file
{
/
foo
/
}
are translated to be under @file
{
/
bar
/
}
,
then include the inherited configuration,
...
...
@@ -4708,7 +4715,7 @@ and get inspiration (or disinspiration)
from what it does in @file
{
header.lisp
}
and @file
{
upgrade.lisp
}
.
@end defun
@defun register
-
preloaded
-
system name @Arest
{}
keys @Akey
s
{}
version @AallowOtherKeys
{}
@defun register
-
preloaded
-
system name @Arest
{}
keys @Akey
{}
version @AallowOtherKeys
{}
A system with name @var
{
name
}
,
created by @code
{
make
-
instance
}
with extra keys @var
{
keys
}
(
e.g. @code
{
:version
}
)
,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment