microsoft / microsoft/mimalloc
Mimalloc with vcpkg on Windows
- Dominant language
- C
- Stars
- 13.4k
- Forks
- 1.2k
- Avg merge
- 4d 45m
- Merged PRs (30d)
- 13
Description
Hi,
I was able to integrate mimalloc into my project, with great results: before the parallel execution was negated by the allocation, now with mimalloc, the speedup is almost linear.
However, I spent quite some time with the integration. Compared with other libraries, which I integrated by just installing them to vcpkg, the mimalloc did not work that way. There is a package mimalloc on vcpkg, but it obviously does not work as expected, even with the override component. In the end, I just gave up and build mimalloc manually using the solution in the mimalloc project, linked it from CMake with an absolute path, and manually copied the dll to my project.
I just wonder, is there some principal problem with the vcpkg/CMake integration on Windows or can I fix it with just a little effort?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the mimalloc CMake integration and the vcpkg mimalloc package on Windows, then reproduce the reported need for an absolute library path and manual DLL copying. Done means a documented or corrected vcpkg/CMake integration that builds and links mimalloc without those manual steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cmake
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100