summaryrefslogtreecommitdiff
path: root/pkgs/development/libraries/mimalloc (follow)
Commit message (Expand)AuthorAgeFilesLines
* mimalloc: 2.1.6 -> 2.1.7R. Ryantm2024-06-101-2/+2
* mimalloc: 2.1.4 -> 2.1.6R. Ryantm2024-05-171-2/+2
* mimalloc: 2.1.2 -> 2.1.4R. Ryantm2024-04-291-2/+2
* mimalloc: 2.0.9 -> 2.1.2R. Ryantm2023-04-301-2/+2
* mimalloc: fix static buildYureka2023-01-151-2/+6
* mimalloc: 2.0.7 -> 2.0.9R. Ryantm2022-12-261-2/+2
* mimalloc: 2.0.6 -> 2.0.7 (#199488)Yureka2022-11-041-2/+2
* treewide: optional -> optionals where the argument is a list•••the argument to optional should not be list Artturin2022-10-101-1/+1
* mimalloc: 2.0.5 -> 2.0.6Mario Rodas2022-05-201-10/+2
* mimalloc: 2.0.2 -> 2.0.5Kevin Amado2022-02-281-6/+20
* mimalloc: revert doCheck enable•••For some reason, test fails with binary not being able to find libmimalloc.so.2.0. Manually specifying LD_LIBRARY_PATH gets it working, which does not look like a very viable fix. Mark Vainomaa2021-06-291-2/+0
* mimalloc: make use of MI_INSTALL_TOPLEVEL•••Fixes: - Gross file moving in postInstall (maintenance burden) - Usability of CMake files Also enables check phase Mark Vainomaa2021-06-291-21/+15
* mimalloc: 2.0.0 -> 2.0.2Mark Vainomaa2021-06-291-2/+2
* mimalloc: 1.6.7 -> 2.0.0R. RyanTM2021-03-201-2/+2
* pkgs/development/libraries: stdenv.lib -> libBen Siraphob2021-01-211-4/+4
* treewide: remove enableParallelBuilding = true if using cmakeBen Siraphob2021-01-031-1/+0
* mimalloc: 1.6.4 -> 1.6.7R. RyanTM2020-11-031-2/+2
* mimalloc: 1.6.3 -> 1.6.4R. RyanTM2020-08-261-2/+2
* mimalloc: 1.6.1 -> 1.6.3R. RyanTM2020-05-271-2/+2
* mimalloc: 1.1.0 -> 1.6.1ajs1242020-02-191-12/+16
* mimalloc: fix one final time•••The library link name is embedded in the ELF executable, so renaming the file doesn't work. This patch just bites the bullet and writes two separate code paths for the secure vs non-secure build... Signed-off-by: Austin Seipp <aseipp@pobox.com> Austin Seipp2019-12-061-6/+10
* mimalloc: (really) unbreak dynamic linking•••4d392099 didn't quite do the trick, but this should finally fix everything -- namely, the -secure.so symlink was broken, and libmimalloc.so itself was also a symlink that needed to be replaced with the real shared object file. Signed-off-by: Austin Seipp <aseipp@pobox.com> Austin Seipp2019-12-041-4/+7
* mimalloc: un-break dynamic linking•••Previous versions of the build assumed libmimalloc.so would be a hard copy of mimalloc-secure.so iff secureBuild == true, but in 1.1.0 and later it seems libmimalloc.so is a symlink to the -secure variant. This apparently rectifies some behavior I noticed that was strange previously. This breakage wasn't caught because the 1.1.0 update was automatic in 5596317d4; there should be a checkPhase to ensure this doesn't happen again... Signed-off-by: Austin Seipp <aseipp@pobox.com> Austin Seipp2019-12-031-8/+9
* mimalloc: 1.0.8 -> 1.1.0•••Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/mimalloc/versions R. RyanTM2019-10-221-2/+2
* mimalloc: init at 1.0.8•••Signed-off-by: Austin Seipp <aseipp@pobox.com> Austin Seipp2019-09-231-0/+46