QNX compilation inside dev containers

[TimofteBogdan1900]

Proposal for solution how to build for QNX in the dev containers.

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
2026/03/09 11:51:45 Downloading https://releases.bazel.build/8.3.0/release/bazel-8.3.0-linux-x86_64...
Extracting Bazel installation...
Starting local Bazel server (8.3.0) and connecting to it...
INFO: Invocation ID: 693a2443-e158-4a60-a711-9408e2be014b
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
WARNING: For repository 'googletest', the root module requires module version googletest@1.17.0, but got googletest@1.17.0.bcr.2 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 5 packages loaded
Loading: 5 packages loaded
    currently loading: 
Loading: 5 packages loaded
    currently loading: 
Loading: 5 packages loaded
    currently loading: 
Loading: 5 packages loaded
    currently loading: 
Analyzing: target //:license-check (6 packages loaded, 0 targets configured)
Analyzing: target //:license-check (6 packages loaded, 0 targets configured)

Analyzing: target //:license-check (28 packages loaded, 9 targets configured)

Analyzing: target //:license-check (91 packages loaded, 9 targets configured)

Analyzing: target //:license-check (102 packages loaded, 9 targets configured)

Analyzing: target //:license-check (156 packages loaded, 2526 targets configured)

Analyzing: target //:license-check (170 packages loaded, 4419 targets configured)

Analyzing: target //:license-check (176 packages loaded, 7618 targets configured)

Analyzing: target //:license-check (177 packages loaded, 7626 targets configured)

Analyzing: target //:license-check (177 packages loaded, 7626 targets configured)

Analyzing: target //:license-check (177 packages loaded, 7626 targets configured)

Analyzing: target //:license-check (180 packages loaded, 9645 targets configured)

Analyzing: target //:license-check (181 packages loaded, 9769 targets configured)

Analyzing: target //:license-check (181 packages loaded, 9769 targets configured)

Analyzing: target //:license-check (182 packages loaded, 9889 targets configured)

Analyzing: target //:license-check (182 packages loaded, 9889 targets configured)

Analyzing: target //:license-check (182 packages loaded, 9889 targets configured)

INFO: Analyzed target //:license-check (183 packages loaded, 11824 targets configured).
[9 / 13] [Prepa] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes
INFO: From Generating Dash formatted dependency file ...:
INFO: Successfully converted 2 packages from Cargo.lock to bazel-out/k8-fastbuild/bin/formatted.txt
[11 / 13] [Prepa] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar
[12 / 13] Building license.check.license_check.jar (); 0s disk-cache, multiplex-worker
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 226.933s, Critical Path: 2.64s
INFO: 13 processes: 9 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 13 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt <args omitted>
usage: org.eclipse.dash.licenses.cli.Main [-batch <int>] [-cd <url>]
       [-confidence <int>] [-ef <url>] [-excludeSources <sources>] [-help] [-lic
       <url>] [-project <shortname>] [-repo <url>] [-review] [-summary <file>]
       [-timeout <seconds>] [-token <token>]

[github-actions]

The created documentation from the pull request is available at: docu-html

[mariuswbr]

Looks good to me.

[lurtz]

Something breaks with renaming the user. E.g. the main tag of the devcontainer got pytest via uv preinstalled in the user directory. This does not work anymore after the user has been renamed.

lure9428 ➜ ~/.../uv/tools/pytest/bin $ pytest --help
bash: /home/lure9428/.local/bin/pytest: cannot execute: required file not found

The reason is the following:

lure9428 ➜ ~/.../uv/tools/pytest/bin $ cat pytest 
#!/home/vscode/.local/share/uv/tools/pytest/bin/python
# -*- coding: utf-8 -*-
import sys
from pytest import console_main
if __name__ == "__main__":
    if sys.argv[0].endswith("-script.pyw"):
        sys.argv[0] = sys.argv[0][:-11]
    elif sys.argv[0].endswith(".exe"):
        sys.argv[0] = sys.argv[0][:-4]
    sys.exit(console_main())

As you can see the shebang still refers to the vscode home directory.

Is it possible to have a symlink from /home/vscode/ to /home/$USER/?

[mariuswbr]

As you can see the shebang still refers to the vscode home directory.

Is it possible to have a symlink from /home/vscode/ to /home/$USER/?

@lurtz
For whatever reason I cannot annotate your comment, therefore this separate one here.
Good catch, thank you! I only checked with the devcontainer v1.1.0

Added a symlink as you suggested and it seems to work: