AcademySoftwareFoundation / AcademySoftwareFoundation/OpenRV
[Bug]: CY2024 PySide6 docker build on Rocky contains large volume of Qt debug files
- Dominant language
- C++
- Stars
- 764
- Forks
- 246
- Avg merge
- 6d 12h
- Merged PRs (30d)
- 13
Description
### What happened?
I have successfully built the current main branch using the Rocky9 Docker workflow for both the CY2023 and CY2024 docker files (using the workaround described in #853 of building dependencies before main_executable).
The resulting tree in _build/stage/app that I've copied out of the docker container varies in size considerably and I think this is due to the Qt debug files that exist in the Qt6 version as opposed to the Qt5 build:
```
$ du -sh *
7.8G rv_3.0.0-c83f458-pyside6
5.2G rv_3.0.0-d69c055-pyside2
```
The PySide6 build has lots of debug files in its lib and plugins/Qt folders that the PySide2 version does not have (around 4GB worth of it). For example, lib/Qt6WebEngineCore.debug almost weighs 1 GB in of itself.
### List all the operating systems versions where this is happening
Rocky 9
### On what computer hardware is this happening?
quadcore AMD Ryzen 7 3750H
### Relevant console log output
```shell
```
### Environment variables
_No response_
### Extra information
_No response_
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Start with the Rocky 9 Docker workflow and compare the CY2023 and CY2024 Docker files, focusing on the staged tree under _build/stage/app and the Qt6 lib and plugins directories. Check the workaround described in #853 and determine how the debug files enter the PySide6 build; done means the CY2024 runtime image no longer contains unnecessary debug files and its size is reduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100