openframeworks / openframeworks/openFrameworks
Better handling of side by side MSYS2 flavors
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
When switching from mingw64 to ucrt64, unexpected compilation errors happen.
Also, when swithcing back and forth, a new download of libs is required.
proposal : manage libs and objs in msys2/${msystem}/ instead of msys2/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the MSYS2 build and dependency-management entry points that create or consume paths under msys2/. Reproduce switching between mingw64 and ucrt64 and inspect how libraries and objects are selected. Done means each flavor uses its own msys2/${msystem}/ paths without unexpected compilation errors or repeated library downloads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100