Configure output location of built artifacts
- Dominant language
- No language data
- Stars
- 94
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
# Background
Configuring the location of built artifacts is important when configuring a project convention. The software model plugins allow configuration for output locations directly on the `*BinarySpec` which are translated to the right property for the various compile tasks.
The MSVC and MinGW tool chains allow more customization when specifying the import library of a shared library. In fact, MSVC provide the [linker flag `/implib`](https://docs.microsoft.com/en-us/cpp/build/reference/implib-name-import-library) and MinGW provide the [linker flag `--out-implib`](http://www.mingw.org/wiki/msvc_and_mingw_dlls). See https://github.com/gradle/gradle/issues/2649.
Contributor guide
Research direction
Start by examining the software model plugins and how output locations on BinarySpec are translated to compile-task properties. Then inspect the MSVC and MinGW toolchain handling described in the issue and issue 2649; done means shared-library import-library locations can be configured using the respective linker flags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100