| #
5488b945 |
| 10-Mar-2025 |
Manish Pandey <manish.pandey2@arm.com> |
Merge "build(poetry): install dependencies with `--no-root`" into integration
|
| #
c25405d6 |
| 10-Mar-2025 |
Chris Kay <chris.kay@arm.com> |
build(poetry): install dependencies with `--no-root`
More recent versions of Poetry introduced the `package-mode` key to configure whether the project should be used for dependency management only,
build(poetry): install dependencies with `--no-root`
More recent versions of Poetry introduced the `package-mode` key to configure whether the project should be used for dependency management only, but this is incompatible with the earlier versions of Poetry that we still support.
Instead, we rely on installing with the `--no-root` flag, which behaves similarly. Installing without passing the `--no-root` flag is deprecated, and in recent versions of Poetry has become a hard error.
This change ensures that the build system always installs dependencies with the required flag.
Change-Id: Ic1543511314dcd20c00b73fd9e8cfae3dd034a41 Signed-off-by: Chris Kay <chris.kay@arm.com>
show more ...
|
| #
9bc738d2 |
| 06-Nov-2024 |
Manish V Badarkhe <manish.badarkhe@arm.com> |
Merge changes I0448caa4,I8ee666ee into integration
* changes: build: install dependencies before doc build fix(docs): fix the example command for doc build
|
| #
50d9383b |
| 03-Sep-2024 |
Tamas Ban <tamas.ban@arm.com> |
build: install dependencies before doc build
Signed-off-by: Tamas Ban <tamas.ban@arm.com> Change-Id: I0448caa4e22c13d4dd821261642833d49ff7a234
|
| #
cd8eb18d |
| 17-Jun-2024 |
Manish Pandey <manish.pandey2@arm.com> |
Merge changes from topic "ck/tf-a/verbosity-cleanup" into integration
* changes: build: unify verbosity handling build: add facilities for interpreting boolean values build: add string casing
Merge changes from topic "ck/tf-a/verbosity-cleanup" into integration
* changes: build: unify verbosity handling build: add facilities for interpreting boolean values build: add string casing facilities to utilities
show more ...
|
| #
7c4e1eea |
| 02-May-2024 |
Chris Kay <chris.kay@arm.com> |
build: unify verbosity handling
This change introduces a few helper variables for dealing with verbose and silent build modes: `silent`, `verbose`, `q` and `s`.
The `silent` and `verbose` variables
build: unify verbosity handling
This change introduces a few helper variables for dealing with verbose and silent build modes: `silent`, `verbose`, `q` and `s`.
The `silent` and `verbose` variables are boolean values determining whether the build system has been configured to run silently or verbosely respectively (i.e. with `--silent` or `V=1`).
These two modes cannot be used together - if `silent` is truthy then `verbose` is always falsy. As such:
make --silent V=1
... results in a silent build.
In addition to these boolean variables, we also introduce two new variables - `s` and `q` - for use in rule recipes to conditionally suppress the output of commands.
When building silently, `s` expands to a value which disables the command that follows, and `q` expands to a value which supppresses echoing of the command:
$(s)echo 'This command is neither echoed nor executed' $(q)echo 'This command is executed but not echoed'
When building verbosely, `s` expands to a value which disables the command that follows, and `q` expands to nothing:
$(s)echo 'This command is neither echoed nor executed' $(q)echo 'This command is executed and echoed'
In all other cases, both `s` and `q` expand to a value which suppresses echoing of the command that follows:
$(s)echo 'This command is executed but not echoed' $(q)echo 'This command is executed but not echoed'
The `s` variable is predominantly useful for `echo` commands, where you always want to suppress echoing of the command itself, whilst `q` is more useful for all other commands.
Change-Id: I8d8ff6ed714d3cb401946c52955887ed7dca602b Signed-off-by: Chris Kay <chris.kay@arm.com>
show more ...
|
| #
0223d157 |
| 18-Apr-2023 |
Sandrine Bailleux <sandrine.bailleux@arm.com> |
Merge "feat(docs): allow verbose build" into integration
|
| #
f771a344 |
| 17-Mar-2023 |
Yann Gautier <yann.gautier@foss.st.com> |
feat(docs): allow verbose build
If V=1 is set (or directly Q="") in the 'make doc' command line, the sphinx command that builds the documentation is displayed.
Signed-off-by: Yann Gautier <yann.gau
feat(docs): allow verbose build
If V=1 is set (or directly Q="") in the 'make doc' command line, the sphinx command that builds the documentation is displayed.
Signed-off-by: Yann Gautier <yann.gautier@foss.st.com> Change-Id: I4961c124cc52d0183371f1d4bbc0e440f5ae6e63
show more ...
|
| #
fe4fa94e |
| 21-Apr-2020 |
Sandrine Bailleux <sandrine.bailleux@arm.com> |
Merge "doc: Treat Sphinx warnings as errors" into integration
|
| #
8b815a4e |
| 17-Apr-2020 |
Sandrine Bailleux <sandrine.bailleux@arm.com> |
doc: Treat Sphinx warnings as errors
'make doc' will now fail if Sphinx outputs any warning messages during documentation generation.
Change-Id: I3e466af58ccf29b14a7e61037539b79ab6fc6037 Signed-off
doc: Treat Sphinx warnings as errors
'make doc' will now fail if Sphinx outputs any warning messages during documentation generation.
Change-Id: I3e466af58ccf29b14a7e61037539b79ab6fc6037 Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>
show more ...
|
| #
12b67439 |
| 21-May-2019 |
Sandrine Bailleux <sandrine.bailleux@arm.com> |
Merge "doc: Add minimal Sphinx support" into integration
|
| #
653279b0 |
| 23-Jan-2019 |
Paul Beesley <paul.beesley@arm.com> |
doc: Add minimal Sphinx support
Add the essentials for supporting a Sphinx documentation build:
- A makefile under docs/ to invoke Sphinx with the desired output format - A Sphinx master configur
doc: Add minimal Sphinx support
Add the essentials for supporting a Sphinx documentation build:
- A makefile under docs/ to invoke Sphinx with the desired output format - A Sphinx master configuration file (conf.py) - A single, top-level index page (index.rst) - The TF.org logo that is integrated in the the sidebar of the rendered output
Change-Id: I85e67e939658638337ca7972936a354878083a25 Signed-off-by: Paul Beesley <paul.beesley@arm.com>
show more ...
|