| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
select either have ValidateOptions() issue error message and exit,or throw an exception and then you can handle it your own way. per dmoody's sugguestion
|
|
|
|
| |
being flagged as undefined. Per mwichmann's feedback
|
| |
|
|
|
|
| |
either SCons specified or specifie by AddOption calls. It will error out if there are any unknown options. Resolves Issue #4187
|
| |
|
|
|
|
|
|
|
| |
These parameters need to be passed to both the compiler and the linker,
otherwise lots of "undefined reference to `__asan_stack_malloc_0'"
errors get emitted at link time, since the appropriate library is not
linked in.
|
| |
|
|
|
|
| |
found policy and msvc script error policy to Policy.py. Rework vcvars bugfix handling for SxS toolset 14.28. Add method to return msvc toolsets. Add experimental function to return msvc version and msvc toolset version given a version specification (proxy for selection). Add API.py to manage symbols imported in vc.py. Update documentation.
|
|
|
|
| |
documentation. Add additional exceptions for SDK version not found, toolset version not found, and spectre libraries not found. Add data structure for platform type.
|
|
|
|
| |
MSVC_TOOLSET_VERSION documentation.
|
|
|
|
| |
documentation artifacts.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add to the existing manpage section on Fortran system-specific behavior
notes that SCons provides construction environment sets for six "dialects",
so that each can be individually tuned based on the file suffix.
The PR author considers this system to be of dubious utlity - it only has
any real effect in a project with files of many different suffixes where
each suffix indicates different handling, within a single build. Since
such builds might theoretically exist (there must have been some reason
this setup was designed), just try to document what there is.
Related in a proximate way only (i.e. next item in manpage),
the note on cygwin+Python is amended to also mention msys2.
Fixes #4173
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|
|
|
| |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The HOST_ARCH/TARGET_ARCH functions have been defined in two
places, generic and Windows, these are consolidated into one,
leaving a comment in the msvc.xml file to show where that version
went to. HOST_OS/TARGET_OS also got some tweaks - this was in
line with these now being set by default for all platforms.
The $TERMPFILE construction var was not defined; added and the
whole family had docs updated.
A small tweak to Split wording.
References to Python changed to entity references (there are still
more of these to change).
lambda as an entity reference is not correct (generated docs show
the symbol, but Python does not use the lambda symbol to refer
to lambda expressions).
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|
|
|
| |
Before this commit, these were only defined for Win32 and OS/2
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Review comments suggested for consistency env.Tool should also
return the Tool instance.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | |
|
| | |
|
| |
| |
| |
| | |
changes
|
|/ |
|
| |
|
|
|
|
| |
variable is set as it uses it
|
|
|
|
| |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add an example on adding an emitter to an existing builder,
based on a mailing-list discussion with Jeremy Elson.
Also:
* Try to model "best practice" by changing instances of hand-modifying
env['ENV']['PATH'] in examples to using AppendENVPath function.
* Fixed a couple of Py2-style print statements.
* Tweaked markup on a couple of instances of site_scons.
* Black-formatted examples in the two userguide sections that
were otherwise modified.
* Dropped old cons doc content which was included as a big
comment at the fromt of builders-writing.xml.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Use os.environ.copy() in examples - better not to get the
Python proxy class that is os.environ, and instead a real dict.
* Fix spelling on a python dict method: set_default -> setdefault
* Update some wording on prepending in the user guide (where it
still said "append to the beginning")
* Change the rather oblique note in the recently modified section
on Append of values to CPPDEFINES with something more explicit.
* And, modify the sphinx config to get the version from SCons
rather than hardcoding.
Fixes #3867
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Try to be a bit more descriptive about compilation databases.
Two of the User Guide examples now use the scons_examples style
to show a little more what happens.
Fixes #3845.
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
|
| |
| |
| |
| |
| |
| |
| | |
Existing written doc, but was not included - now added to the
Miscellaneous chapter. Some rewriting.
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>
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|