Support both libtool and non-libtool style library names on Windows
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 491
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Description
Depending on how things are built you can either get libcairo-2.dll (libtool) or cairo.dll for example.
I have made a very lazy patch to workaround this before but the more robust solution upstream is probably for it to simply attempt loading both on windows.
Contributor guide
No contributing guide indexed for this repository
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
No source file, test, or entry point is named. Trace the Windows library-loading path and compare it with the linked workaround; done means both libtool-style and non-libtool-style names are attempted, with tests covering the two naming forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100