| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Checked in the SCons/__init__.py instead of the changes to the
sconsign manpage. Restoring the former and updating the latter.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|\ |
|
| |
| |
| |
| | |
The filter is a fnmatch pattern matched against output file.
|
|/
|
|
|
|
| |
The filter is a fnmatch pattern matched against output file.
Also rename target->output in docs to match the output of compilation_db.
|
|
|
|
| |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|
|
|
| |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|\
| |
| | |
Tweaks to variantdir documentation
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Move the Repositories chapter to just after the Variantdirs
chapter, since they're the same general topic - controlling
source and destination locations in bulk. Also moved the
internationalization chapter near the end, since it didn't
seem to fit in the logical flow where it was.
No doc contents changed - just order.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
| |
| |
| | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Manpage/shared VariantDir function wording tries to make more
clear that build happens in the variant. Other tweaking.
User guide variant description similarly updated. A (worded) example
of why one might want variants is added.
Formerly separate chapter doc/user/variants.xml is now included
as a section in the previous chapter. An additional example
is enabled (was in the file but commented out), which some
introductiory wording. The introduction to the other sample
in the file is also built up slightly.
Dropped embedded comments that were the old Cons documentation
for these topics.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|/ |
|
|\
| |
| | |
Include SideEffect section into the UserGuide
|
| |
| |
| |
| | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
| |
| |
| | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
| |
| |
| | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
| |
| |
| |
| |
| |
| | |
Existing written doc, but was not included - now added to the
Miscellaneous chapter. Some rewriting.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
| |
| |
| | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
| |
| |
| | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add note to manpage that Variables names should not conflict with
existing constructions variables.
Fix a broken User Guide example which was hitting a Py2/Py3
transition - was displaying "Unknown variables: dict_keys(['NOT_KNOWN'])"
instead of "Unknown variables: NOT_KNOWN"
Added a User Guide note on how to make sure a Variable is actually
supplied, if that's what you want (making the default an invalid value).
This is supported by an additional output of an existing example
(it's not a new example, just called a different way).
Slightly built up the explanation of UnknownVariables not being
usable until variables object has been passed to an env.
Examples reformatted using Black, which changed some line numbers
in example outputs.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | |
|
|/
|
| |
I guess, double that is typo
|
|\
| |
| | |
Updated docs on Actions for output control
|
| |
| |
| |
| | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
| |
| |
| | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Manpage now mentions specifically generating your own Action object
in order to control the output string. Calls out using None as the
command-output specifier to avoid output: Action(foo, None) and
Action(foo, cmdstr=None), as well
Userguide got a mention of using the action kwarg for readability
and an example showing creating the Action for Command manually
to set the output string.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|/
|
|
|
|
|
|
| |
Troubleshooting section had a remaining link to tigris.org.
Now points to scons website - not to github, because we don't
encourage directly filing a bug before first discussing.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|\
| |
| | |
man: expand explanations on selecting Tool modules
|
| |
| |
| |
| |
| |
| | |
skip]
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
| |
| |
| | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|/
|
|
| |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|
|
|
| |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In DESCRIPTION, turn function references into clickable links.
Also turn special variables into link references, which necessitated
defining identifiers for them, as these are not part of the
generated entities process.
Introduce the term "execution environment" in the intro section
for terminology consistency, since this term is defined in
the User Guide (Chapter 7, Environments).
Change wording of the -c option slightly.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|
|
|
| |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|\
| |
| | |
Trivial: add a comment about options to manpage source
|
| |
| |
| |
| | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Explain why we don't use this form of listing options in manpage:
<varlistentry><term>-A</term><term>--a-long-opt</term>...
i.e. a term for each variant of an option.
This is a comment only, no change to actual manpage.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
| |
| |
| | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|\ \
| | |
| | | |
[WIP] Enforcing HTML output encoding to UTF-8.
|
| |/
| |
| |
| |
| |
| |
| |
| | |
The stylesheet for the single HTML outputs (not chunked) get adapted,
such that UTF-8 is always used as output encoding for all chunks.
In addition, the HTML header now contains a corresponding
"content" tag, displaying the used charset=UTF-8.
[skip ci]
|
|\ \
| | |
| | | |
Update docs on argument passing to Environment, etc.
|
| | |
| | |
| | |
| | | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Simplified the guide wording on source/target kwargs to
get rid of an ambifuity.
Some tweaking of the manpage on overrides and parse_args.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Review comments noted that there was perhaps more assumptions
about Python knowledge than warranted, added some things to
address that, including an intro to dictionaries.
Markup changes in environment chapter, plus more wording tweaks.
Filled out an example of of overriding when calling a builder,
and added a note on when that is not sufficient, and separate
envs are needed.
Dropped a python2 paragraph.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Adds a new uguide Ch 7 section on using the parse_flags method (with Ex.)
Moves the section on overrides in calls to Builders to Chap 7 -
it was using concepts not introduced yet where it was placed.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Two manpage options from a previous commit had the option-argument
listed in caps to match the --help output. A review comment
suggested not to do this, as all-caps indicates a construction
variable. Question: should the AddOption calls for these two
set a metavar to match the current documentation?
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Renamed those documentation files named __init__.xml to the name of the
component directory.
Merged SCons/Tool/packaging.xml (which had no unique content) into
the renamed SCons/Tool/packaging/packaging.xml
Considerable rework was needed to the packaging content to
fill in some gaps:
* properly named the commandline option
* add the option to the manpage (with a note it's not always avail)
* only list the packagers once
* add example of selecting packaging tool, and of specifying multiple packagers
* more description of source, target and metadata for Packaging
* mention use of PACKAGEROOT
* redo tag description
* add a bit of explanation to the complete packaging example
Signed-off-by: Mats Wichmann <mats@linux.com>
|