Add Intermediate Directory Option #1236
Description
Is your feature request related to a problem? Please describe.
N/A
Describe the solution you'd like
The ability to set the build output intermediate directory
Describe alternatives you've considered
N/A
Additional context
For many years, I have wanted the ability in CDT to be able to set the intermediate directory for managed build. Something seemingly so simple, but watching for 10 years and it still doesn't exist.
Today the outputs for all build configurations with a managed build are put in the respective ${CONFIG_NAME} folder under the project root. This directory gets used for all of the intermediate files of the build such as object files and also the desired output files. It would be desirable to set a directory where these outputs are placed within the project instead.
With the following build configurations:
- RELEASE
- DEBUG
The output folder structure relative to the project today is:
- RELEASE/
- DEBUG/
The ask is to be able to set the intermediate directory. For example: "artifacts". The structure would then look like this
- artifacts/RELEASE/
- artifacts/DEBUG/
Setting the intermediate directory is desirable for organizational purposes. Additionally, it can make a .gitignore simple as we only need to ignore the artifacts directory.
I would be willing to take a stab at making this contribution myself; however, this is one massive project. I don't know where to start. Furthermore, it would seem to be an extremely simple change in theory to just add an intermediate directory option. However, I have no clue how ingrained the current intermediate directory is within the current codebase and if it would be a monster to implement...