The orchestrator path inside the test workspace (test/configs) is
build/make, which is different from the current path in multitree
(build/build/make). This was causing `python test_lunch.py` to fail
Rather than restructing the test workspace to build/build/make now (and
build/ later when the orchestrator is in its own project), create a
Context object which can be mocked.
Test: python test_lunch.py
Change-Id: Ibd89c3ff0204ebad320c90a05bab4c0f8c86b3a0
This reduces the scope of the demo to just building and installing
a single .so, but it makes the demo actually build that single .so.
Next up, writing some unit tests and fleshing out functionality.
Test: see the README
Change-Id: I560904b786fbf69d3a83dbb08d496dba5a3192ca
Summary:
- Create python classes for ninja vocbulary in `ninja_syntax.py`. These
classes will be serialized to a ninja file
- Create a Writer class in `ninja_writer.py`. The current API supports
adding variables,rules,build actions, etc. This can be extended in the
future (See `test_ninja_writer.py` for examples)
Future Work:
- Update the `Subninja` class once chDir is supported (aosp/2064612)
- Support a width parameter that will be used to wrap long lines of
text. This will improve readability of the generated files
Expected Use Case: Multi-tree build orchestrator
Test: python ./test_ninja_syntax.py
Test: python ./test_ninja_writer.py
Change-Id: I90c7ee69ddeb7c20c3fd4fca5a911dddbf2253bd
The code assumes a different source structure. It requires updating
the path configurations.
Bug: 230448564
Test: N/A
Change-Id: I38bf181eecdd291712212ba8ee6d61b85c3fbb07
