Ardu waf rebase on waf 2.0.23 from gitlab #11

Its only built if gfortran is used at least with version 6.

Also build a main program that uses the parent module.

Signed-off-by: Mickaël Schoentgen <[email protected]>

…o input files generated during build

…n build Most of the ant_globs used are explicitly and knowingly on build directory (ie. javadoc, jar re) so the warning is quite spurious. The only one that may be in doubt is the source re one: I added also here because if you use a code generator (ie. protoc) then it is also correct to glob on builds and the warning is misleading.

The previous patches to workaround http://support.microsoft.com/kb/830473 drastically over estimated the number of characters in commands by treating the repr() version of the command array as a reasonable estimator of commandline length. This caused commands attempt to write argsfiles before they should have. The new calculation calculates the number characters in the command array and adds the number of spaces that would be added by ' '.join(cmd) this provides a much closer estimate of the commandline length. This also limits the CLI-length on non windows platforms to 200kB. This prevents us hitting the much larger argument limits on Linux/BSD/MacOS platforms.

This patch addresses the bug described in issue #2225 where in using posix paths and an empty PREFIX value can result in files being installed to the root of the drive specified by destdir instead of to the desired prefix value. This is a bug in the assumption that user specified paths that are strings will contain directory separators that match the target operating system.

Not all tools executed by tasks support the '@argsfile' syntax for shunting commandline arguments to a file. This means that if such commands are shunted to a file early, he command will not work. On windows the rc.exe command is such an example, but some tools on linux have similar limitations. In the posix case, we artifically limit our commandline size because it is difficult/variable to caluclate what the actual limit is (it is partially dependent on environment size). This could artifically cause commands to fail due to commandline length when they otherwise wouldn't. This patch fixes this issue by adding the 'allow_argsfile' flag to the task. This way certain task instances will be able to specify if they are compatible with the '@argsfile' syntax or not.

TypeError: can only concatenate list

This patch attempts to detects if, when we are running from within an MSYS2 environement (MSYSTEM is set) we are also executing inside an MSYS2 provided version of python. It does this by assuming that if we are not in a cygwin environment and we are building on windows, If the value of sys.executable is /usr/bin or /bin or /usr/local/bin (somethign unixy) then we are running in an MSYS2 python interpreter and shoudl compensate for msys2 root paths. Otherwise we shouldn't be doing extra path manipulation.

…Task class #2216 The class waflib.Tools.winres.rc_parser is not a subclass of waflib.Task.Task: rc_parser -> c_preproc.c_parser -> object

…nt contains UTF-8 chars

…ault

mac-o symbols are prefixed with an underscore. when specifying multiple sub-regexes (e.g. 'sym1|sym2|sym3'), only the first will be matched (since the expansion turns into '(?P<symbol>_?sym1|sym2|sym3)'). here, this is remedied by wrapping the symbol regex in a paren group.

Currently PDBs are only installed if the /DEBUG flag appears in the current toolchain's LINKFLAGS attribute. This patch expands support so that /DEBUG:FULL and /DEBUG:FASTLINK also cause PDBs to be installed.

@include

The order of the lines in a doxyfile are important. This patch uses an ordered dictionary to keep the keys of the doxyfile in the same order. This is particularly important for doxyfiles that contain @include lines. In such cases, if the dictionary is not ordered, the @include line can end up in the middle of the generated doxyfile and thus override all entries that were seen before it.

This patch corrects an error in the exec_response_command exception handler which always assumed that the execution's stdout would be bound to the the WafError exception object. However, this assumption is only true when the execution completes with a non-zero status code. For other exceptions, the stdout attribute is not bound. Now, when stdout is not available, the WafError msg will be used instead.

Make javadoc optional to support builds on platforms that don't include javadoc in their Java distribution.

….ant_glob

…ntains Python files Files are also listed in a static arbitrary order.

Previously one could explicitly state to use PySide2 or PyQt4 but not PyQt5 which was picked just by default. In this way the option can override local configurations and also this prevents to have mixed tools versions if we are sure we need PyQt5.

… tasks. In this case we point to the directory instead of the JAR file

… files

ant_matcher() converts an ANT glob pattern to an equivalent regex pattern. This commit adds support for escaping parenthesis in the input pattern so they don't end up being treated as a regex capture group. Also add a unit test to verify ant_glob()'s ability to handle special characters in the input pattern.

Rework how msvcdeps' cached_nodes lock is used so acquiring the lock is only necessary on a cache miss. Also use a "with" context manager to simplify management of the lock lifecycle.

Make path_to_node() only accept a path as a string instead of also as a list. That requires joining the list of path components in the relative path case before calling path_to_node(). Also use path.pop(0) to remove the first path component instead of copying the remainder of the path using a slice operator.

When using msvcdeps, header dependencies are not detected reliably for generated source files. The root cause is a bug in versions of MSVC prior to VS2019 16.0 in which it emits lower-case path prefixes when resolving include paths relative to the containing file. Absolute paths and paths relative to include directories passed in the MSVC command line are, in contrast, case-correct. Such a file-relative include directive with an incorrect lower-case prefix derails waf's node hash signature handling and fails silently. This change uses ant_glob() with the ignorecase keyword argument to find the file on the filesystem with the correct case. The prior case-correction code has been superseded and was removed. See the following Visual Studio bug report for details on the issue: https://developercommunity.visualstudio.com/content/problem/233871/showincludes-lowercases-some-path-segments.html

As recommended in the docs, to support both 3.8 and previous versions, we try to use python3-config --embed and fallback to the previous behavior. Fixes https://gitlab.com/ita1024/waf/issues/2239 See https://docs.python.org/dev/whatsnew/3.8.html#debug-build-uses-the-same-abi-as-release-build

Signed-off-by: Piotr Szubiakowski <[email protected]>

…llation test

…f with standard waf_unit_test Tool

…using QtTest"

https://gitlab.com/ita1024/waf/merge_requests/2248/diffs

…lib in PYTHONPATH

* OUTPUT_DIRECTORY now is created for a present parameter in `pars` of the task.

conf.check(..., execute=True, test_args=['--abc=def'])

…e database by request without rebuilding, add tests (WIP)

…/Jython)

…/ JEP)

Fixes #1731

… throw a stacktrace if no sources was added

Shared libraries often use a suffix encoding their version which should be handled when parsing linker flags.

…env vars

… #2273

variable x is used in the outer loop and gets corrupted by inner enumeration in case of non-jar dependency to reproduce: use the demos/java and run waf build twice: the first time will work (since no class files around) while the second will not since will by bad luck pick a class file in the inner loop

Add support for generating and using gcc's native dependency files with the GNU Assembler in addition to the existing C/C++ support. When the gas and gccdeps tools are loaded, the configure step will test whether gcc operating on an assembly file supports the -MMD argument. If so, waf will pass the -MMD argument to .S files assembled with gcc which will cause it to generate .d dependency files. Waf will then parse those files for dependency information. Note: This will only work for assembly files compiled through the gcc frontend, not with GNU as directly. It also requires assembly files to use the uppercase .S file extension.

Print out which source file waf is gathering dependencies for and leave the leading spaces in the dependency debug output because it can be helpful to see the dependency hierarchy.

…build)

The return type of .keys() in Python 3 is no longer a list, but a 'dict_keys', which does not support the '+' operator.

…e the configure() method or its parameter is mentioned.

…en the cnf and bld parameters to their respective methods.

Add support for MinIO object storage (https://min.io/) using the MinIO client (https://github.com/minio/mc) to wafcache. MinIO is an open-source, self-hostable, S3 compatible cache. The MinIO client supports MinIO connections as well as normal S3/GCS storages by configuring aliases beforehand. Hint: some distributions have `mc` (the GNU Midnight Commander) installed which is not the minio client, be aware of this (or your build may get stuck with waf waiting for `mc` to never finish)

- Exclude classes having folder or symlinks - Exclude well-known Task classes from wafcache processing - Remove stale 'waflib.Task.Task.chmod' processing

…piler with --compiler-options

As this is run in the non-waf process we don't have Logs, so we write to stderr instead or we will get a NameError name 'Logs' is not defined.

The unit test tool moved from a simple split to using shlex.split for handling the unit test command. This results in the path separators on windows being treated as escapes. To handle this the unit test exec command is properly escaped before joining so that the subsequent split restores the original arguments. The quote function is also exposed in the Utilities module so that wscripts making use of the unit test tool can properly quote their contributions to the command as well.

In order to correctly set a default project in visual studio any folders must be listed at the top of the solution file. This change ensures that any folders included in generated solutions sort to the top of the .sln file. The default project, if one exists, will be located after the folders. Note that it should also be correct to place the default at the top of the file, followed by any folders.

Visual Studio returns paths to dependencies with incorrect case. ant_glob() is very slow for this use case (40~50% impact to overall build time). This patch uses os.listdir() to find the correct case of each path component.

Just a few small changes to make msvcdeps.py align with gccdeps.py better.

Rename some local variables to clarify their purpose and to align with msvcdeps.py.

Move the scan() method down in the file to match msvcdeps' method ordering. This makes it easier to compare gccdeps.py and msvcdeps.py to keep them in sync.

Rework how gccdeps' cached_nodes lock is used so acquiring the lock is only necessary on a cache miss. Also use a "with" context manager to simplify management of the lock lifecycle. Ported from 8b5a2a2

Handles presence of \r in module name (ie. DOS mode swig .i files) Should fix #2350

In the current implementation if a project is using build variants it's not possible to use the clang_compilation_database plugin because it strips the variant information from the build object.

Add automatic generation of editor language settings for C and C++, so the automatic code correction uses the correct compiler and compiler flags, including for example the correct C/C++ standard so construct from such standards are correctly managed by the IDE. Correct compiler and flags are automatically generated using the build environment data gathered during configure phase. The playground example has been modified to contain some code that is standard specific to demonstrate the new feature when run under Eclipse.

Make sure just unique include paths (both system and local) are added to prevent overcrowding with useless redundant include paths that grow up a lot the generated XML file and make the usage of the GUI messy. The filter was already there for Java/Python.

Make it easy to add custom target executions in the automatic eclipse configuration generation, for example to call other standard waf targets from other tools or with specific options.

Where default compiler is gcc

__xrange()__ was removed in Python 3 in favor of a reworked version of __range()__. Discovered via ArduPilot/ardupilot#10278

https://gitlab.com/ita1024/waf/blob/master/playground/compress/optim.py

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Ardu waf rebase on waf 2.0.23 from gitlab #11

Ardu waf rebase on waf 2.0.23 from gitlab #11

Commits on Apr 25, 2022

Ardu waf rebase on waf 2.0.23 from gitlab #11

Are you sure you want to change the base?

Ardu waf rebase on waf 2.0.23 from gitlab #11

Commits on Apr 25, 2022