Some modules of OCCT seems to change the return code

[Meakk]

Describe the bug When building OCCT with some modules, failing tests are not seen because the returned code is always 0

To Reproduce Steps to reproduce the behavior:

1. Build f3d without OCCT module
2. Run f3d --invalid-option, return code is non-zero
3. Build f3d without OCCT module (with OCCT build containing DRAW modules)
4. Run f3d --invalid-option, return code is zero

Note it's not reproducible with the release packages because problematic OCCT modules are not included.
I'm suspecting there is a std::atexit call hooking the return code.

Help Wanted We are looking for an OCCT expert that could identify where this issue is coming from in OCCT.