Félix Baylac Jacqué
671739ca79
Well, this was as painful as expected. Introducing a proper autotool-based tracy build. I don't think this is the right approach, but hey, it works. Tracy is not distributing any pkg-config file, so we had to fallback to a more "manual" method to propagate the headers path. Instead of having a plain enable/disable flag, we send the path to the tracy /public subfolder (~= $out in the Tracy Nix derivation). The flake Nixpkgs is currently pointing to 23.05. The tracy derivation was only building the visualizer, not the client library back then. We introduce a 23.11 Nixpkgs and build its Tracy derivation with the 23.05 toolchain to go around some glibc ABI incompatibilities. Kudos to Mic92 for the help for the flake bit. Co-authored-by: Jörg Thalheim <joerg@thalheim.io> |
||
---|---|---|
.. | ||
build-remote | ||
libcmd | ||
libexpr | ||
libfetchers | ||
libmain | ||
libstore | ||
libutil | ||
nix | ||
nix-build | ||
nix-channel | ||
nix-collect-garbage | ||
nix-copy-closure | ||
nix-env | ||
nix-instantiate | ||
nix-store | ||
resolve-system-dependencies | ||
toml11 |