| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Use GoogleTest instead of our own framework
|
| |\ |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | | |
Fixes #1248.
|
| | | | |
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
Python 3.12 deprecated the pipes module and it will be removed
in Python 3.13. In configure.py, I have replaced the usage of pipes.quote
with shlex.quote, which is the exactly same function as pipes.quote.
For more details, refer to PEP 0594: https://peps.python.org/pep-0594
|
| | |
| | |
| | |
| | |
| | | |
We already did this in some, this converts the rest.
Also chmod +x on write_fake_manifests.py while here.
|
|\ \ \
| | | |
| | | | |
Detect whether VC++ compiler can be found in configure.py
|
| |\ \ \ |
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The first experience for most developers who start working on ninja is
this cryptic error message:
bootstrapping ninja...
Traceback (most recent call last):
File "configure.py", line 329, in <module>
if platform.msvc_needs_fs():
File "configure.py", line 89, in msvc_needs_fs
stderr=subprocess.PIPE)
File "python\bin\lib\subprocess.py", line 394, in __init__
errread, errwrite)
File "python\bin\lib\subprocess.py", line 644, in _execute_child
startupinfo)
WindowsError: [Error 2] The system cannot find the file specified
This message happens when bootstrap.py first tries to invoke cl.exe and
it cannot be found. This change looks for cl.exe and warns if it is not
in the user's path, leading to this friendlier message:
bootstrapping ninja...
Traceback (most recent call last):
File "configure.py", line 317, in <module>
raise Exception('cl.exe not found. Run again from the Developer Command Prompt for VS')
Exception: cl.exe not found. Run again from the Developer Command Prompt for VS
|
| |_|/ / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The `--no-version` command line argument was introduced with re2c
v0.15.3.
See https://re2c.org/releases/changelog/changelog.html
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
ken-matsui/support-building-libninja-re2c-on-configure-py
Support building `libninja-re2c.a` on `configure.py`
|
| | |/ / /
| |/| | | |
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Build ninja with C++11
In order to allow future use of std::chrono to make the stats code
portable it is desirable to compile with C++11. Doing so also allows use
of std::unordered_map, and reduces the number of #ifdefs in the ninja
source code.
Switching to C++11 requires modifying both CMakeLists.txt and
configure.py, for MSVC and for other build systems. For MSVC the
required change is adding /Zc:__cplusplus to tell the compiler to
give a more accurate value for the __cplusplus macro. For other
platforms the change is to add -std=c++11 or the CMake equivalent.
This change makes some progress towards resolving issue #2004.
* Delete code and instructions
C++11 guarantees that string::data() gives null-terminated pointers, so
explicitly adding a null terminator is no longer needed.
The Google C++ Style Guide already recommends avoiding unnecessary use
of C++14 and C++17 so repeating this in CONTRIBUTING.md is not critical.
These changes both came from PR-review suggestions.
* Only set cxx_std_11 if standard is 98
* Return to unconditional target_compile_features use
After much discussion it sounds like using target_compile_features
unconditionally is best.
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The checked in sources (depfile_parser.cc and lexer.cc) have the re2c version
embedded in it. The output didn't change since re2c 1.3, except for the
different version number.
A reproducible build would use a pinned version of re2c anyway, so there
is no need to hardcode its value in the checked in generated files.
|
|\ \ \
| |/ /
|/| | |
win: Use cl /help to test for /FS requirement
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
missingdeps tool, take 2
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The tool looks for targets that depend on a generated file, but do not
properly specify a dependency on the generator. It needs to be run after
a successful build, and will list all potential flakes that may have
broken the build, but didn't due to accidental build step ordering.
The search relies on the correctness of depfile and generator output
information, but these are usually easier to get right than dependencies.
The errors found can usually be verified as actual build flakes by trying
to build the listed problematic files alone in a clean build directory.
Such builds usually fail with a compile job lacking a generated file.
There is some overlap between this tool and 'gn check', but not everyone
uses gn, not everyone using gn uses gn check, and most importantly, gn
check is more about modularity, and less about actual build-time deps
without flakes.
The tool needs to be run after a build completes and depfile data is
collected. It may take several seconds to process, up to a dozen or
two on a large, chromium-sized build.
|
|/
|
|
|
|
| |
Make BuildStatus an abstract interface, and move the current
implementation to StatusPrinter, to make way for a serialized
Status output.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Both hash_collision_bench and manifest_parser_perftest crash on AIX with
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
IOT/Abort trap (core dumped)
32-bit AIX applications by default allocates only a single 256M segment
for stack and heap for 32-bit applications, which is insufficient for
these tests. When building these tests on AIX in 32-bit mode, increase
the max number of segments so they will run without crashing.
|
|
|
|
| |
`configure.py` assumes `g++` is present on the system, which is not the case, e.g. for FreeBSD.
`c++` should be used insted, which should be a link to system c++ compiler. This will be `g++` for linux, but `clang++` for FreeBSD.
|
|
|
|
|
| |
The README file was renamed to README.md in commit
a37da20ae74c81703b1c811182fc154d95ed46fe.
|
| |
|
| |
|
|
|
|
| |
* No perfstat for IBM i (OS400) AIX variant
* Allow for future IBM i to identify as 'os400'
|
|
|
|
| |
processor-group Windows API
|
|
|
|
|
| |
Add a LoadDyndeps method to load a dyndep file and update
the edges that name it in their dyndep binding.
|
|
|
|
|
|
|
|
| |
Define a file format suitable for specifying dynamically-discovered
dependency information for build edges. Design a format inspired by the
build manifest format and using the same lexer. Start with a required
format version specification followed by "build" statements that add
implicit inputs and outputs to existing edges.
|
|
|
|
|
|
| |
Create a Parser base class that holds parser functionality not specific
to the build manifest file format. This will allow it to be re-used for
other parsers later.
|
| |
|
|
|
| |
Fixes #1411.
|
|\
| |
| | |
Two fixes for NetBSD
|
| | |
|
| |
| |
| |
| | |
Taking care of printf format specifiers and large files using compiler macros in configure.py
|
|/ |
|
|
|
|
|
| |
DragonFly uses a fork of FreeBSD ports, and also uses the /usr/local prefix.
And ppoll is also available in DragonFly.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Following functions are implemented for further performance
optimization.
* JoinStringPiece
* SplitStringPiece
* EqualsCaseInsensitiveASCII
* ToLowerASCII
To improve performance of CLParser, I will introduce above functions
into include_normalize-win32.cc.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
.\src\clparser.cc(56): note: see reference to function template instantiation '_OutIt std::transform<std::_String_iterator<std::_String_val<std::_Simple_types<char>>>,std::_String_iterator<std::_String_val<std::_Simple_types<char>>>,int(__cdecl *)(int)>(_InIt,_InIt,_OutIt,_Fn1)' being compiled
with
[
_OutIt=std::_String_iterator<std::_String_val<std::_Simple_types<char>>>,
_InIt=std::_String_iterator<std::_String_val<std::_Simple_types<char>>>,
_Fn1=int (__cdecl *)(int)
]
D:\bin\dev\VS\2017\BuildTools\VC\Tools\MSVC\14.10.24911\include\algorithm(946): warning C4244: '=': conversion from 'int' to 'char', possible loss of data
|
| |
|
|
|
|
|
|
|
|
|
| |
This makes it possible to run most of the clparser tests on non-Windows,
and is potentially useful for cross-compiling on non-Windows hosts.
Also, the manual didn't document this as Windows-only previously.
If you use this on non-Windows, please let me know, else I might undo
this change again in the future.
|
|\
| |
| | |
win: Only drop /showIncludes in bootstrap builds.
|
| |
| |
| |
| | |
Fixes #1103.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The standard headers for Visual Studio 2008 generate a warning about
constant conditional expressions when compiled with exception support
disabled. This is caused by the _CATCH_ALL macro in xstddef which is
defined thusly:
#ifdef _HAS_EXCEPTIONS
#define _CATCH_ALL } catch (...) {
#else
#define _CATCH_ALL } if (0) {
#endif
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The pull request that introduced building from a directory other
than the source dir, https://github.com/ninja-build/ninja/pull/979,
made it so all source paths are effectively absolute paths. This
change restores the old behavior in the case when you are building
in the source. See the comments there.
|