Search Criteria
Package Details: heaptrack-git 682.c6ef628-1
| Git Clone URL: | https://aur.archlinux.org/heaptrack-git.git (read-only) |
|---|---|
| Package Base: | heaptrack-git |
| Description: | A heap memory profiler |
| Upstream URL: | http://milianw.de/tag/heaptrack |
| Licenses: | |
| Conflicts: | |
| Provides: | |
| Submitter: | stativ |
| Maintainer: | stativ |
| Last Packager: | stativ |
| Votes: | 4 |
| Popularity: | 0.000000 |
| First Submitted: | 2015-03-29 11:43 |
| Last Updated: | 2017-11-29 17:25 |
Dependencies (9)
- boost-libs
- kdiagram (kdiagram-git)
- kio (kio-git, kio-osync)
- kitemmodels (kitemmodels-git)
- threadweaver (threadweaver-git)
- boost (make)
- extra-cmake-modules (extra-cmake-modules-git) (make)
- git (git-git) (make)
- sparsehash (make)
Required by (2)
- kdevelop-git (requires heaptrack) (optional)
- lib32-heaptrack-git
Latest Comments
Nephyrin commented on 2018-12-18 22:15
I have taken a shot at packaging a lib32-heaptrack-git package that provides the necessary libraries to also target 32bit applications. (@stativ let me know if you'd like to maintain that and I'll pass it over)
Hello71 commented on 2017-10-30 23:38
also it should have conflicts=(heaptrack); provides=(heaptrack)
stativ commented on 2017-06-26 19:54
Sigh, how often I going to explain this. The arch "any" is meant only for packages that doesn't pack any architecture dependent files (eg. you can build them on x86_64 and they will work on i686, too).
And sorry, I'm not going to add arm* to supported architectures, as I can't guarantee the package will work on ARM in the future and ARM is not an officially supported architecture anyway.
wolfpld commented on 2016-11-13 13:51
Heaptrack works on armv7l and aarch64 architectures, please add them to the arch list (or consider using "any").
cdkitching commented on 2016-09-13 02:42
Oh, and there seem to be newer commits on their github than on the kde-hosted repo:
https://github.com/KDE/heaptrack
cdkitching commented on 2016-09-13 02:23
This tool is very much more useful with its GUI. Their cmake configuration is a bit weird: it defaults to building the GUI, but if packages needed for the GUI are absent, it will silently not build it. As a result, your PKGBUILD exhibits different behaviour depending on what packages the user has installed.
If you wish to make your package consistently build the GUI (please do), please add the following packages as dependencies:
extra-cmake-modules
kitemmodels
kdiagram
threadweaver
Installing this and rerunning your PKGBUILD caused the GUI to be built and installed.
Alternatively, pass `-DHEAPTRACK_BUILD_GUI=OFF` to cmake, so you consistently _don't_ build the GUI.
Or perhaps do something with optional dependencies, or get super fancy and make a second package for the GUI.
Anonymous comment on 2015-09-20 22:33
Add i686 to the support architectures, please.