Conversation
nradakovic
added
documentation
| ============================ | ||
|
|
||
| TBD | ||
| Welcome to Bazel C/C++ Toolchain Config documentation. This repository containts Bazel toolchain configurations for different platforms used within S-CORE modules. |
There was a problem hiding this comment.
| Welcome to Bazel C/C++ Toolchain Config documentation. This repository containts Bazel toolchain configurations for different platforms used within S-CORE modules. | |
| Welcome to Bazel C/C++ Toolchain Config documentation. This repository contains Bazel toolchain configurations for different platforms used within S-CORE modules. |
| - ``use_system_toolchain`` (bool): If true, do not download/link SDP archives (system toolchain mode). | ||
| - ``runtime_ecosystem`` (string): Runtime ecosystem identifier (default ``posix``). | ||
| - ``version`` (string): GCC toolchain version. | ||
| - ``license_info_url`` (string): URL of the license server (used for QNX flows). |
There was a problem hiding this comment.
What do you mean with "flows" here? Do you mean QNX "toolchains" or "flavors"? Or "workflows"?
But if it is meant to be used in workflows then it would be good to inject that parameter from the outside via command line parameter / bazelrc / environment variable because this kind of thing should not be baked into the module file, but is something determined by the execution environment. E.g. at ETAS we might have a different license server than at BMW.
There was a problem hiding this comment.
No, this has nothing to do with the workflows. QNX requires that each call to qcc or any other tool from their package verifies developers license information (which product under developer name is registered), so with this said, everyone should set their license under certian path. We agreed that default location will be: /opt/score_qnx/license/licenses. If this license file is missing, QNX wrappers will try to use predeclared enviorment variables to fetch information about license servers. This argument is for that.
Since the build is executed in sandbox, we're injecting license info over toolchain mechanism where the tools are executed. Option to do this directly from command line is very bad because every change to env/config, bazel will rebuild the whole toolchain.
2 participants
No description provided.