Vcpkg: Library purge leaves build tree on the disk.

Created on 28 Sep 2017 · 8Comments · Source: microsoft/vcpkg

I've noticed that currently if I try to remove the library it's sources and build files from 'buildtrees' folder are left untouched. Supplying --purge flag doesn't change anything.
Isn't it would be logical to remove everything from the library with --purge flag? Maybe downloaded archive could be left for future use but build tree should be removed IMO.

vcpkg-feature

Source

lazyhamster

👍2

Most helpful comment

It looks to me that the buildtree is only useful for debugging purposes.

This is very important though. I'd hate to be left with the choice to either A) download the source files (and the correct version) manually after vcpkg installation, or B) have to keep both the source files in vcpkg as well as all these gigabytes of build artefacts.

vcpkg should:

Leave the source files intact
Have the ability to purge intermediate build files, like the .pch files, which are actually the files taking most of the space.

patrikhuber on 19 Jan 2018

👍3

All 8 comments

I also think the build files from older sources should be deleted too. My current vcpkg folder currently is exceeding 250gb.

jasjuang on 1 Oct 2017

I also realized the buildtree folder is taking 200gb out of 250gb of my vcpkg folder. I would even like to see an option to purge the buildtree after installation. It looks to me that the buildtree is only useful for debugging purposes.

jasjuang on 2 Oct 2017

👍3

I also think that some tools to cleanup the vcpkg folder would be very usefull.

MikeGitb on 19 Nov 2017

👍3

Oh wow this doesnt exist? OK Hmmm. Interesting to know. I Came here also to find out the proper way how to do this.

genbtc on 25 Dec 2017

It looks to me that the buildtree is only useful for debugging purposes.

vcpkg should:

Leave the source files intact
Have the ability to purge intermediate build files, like the .pch files, which are actually the files taking most of the space.

patrikhuber on 19 Jan 2018

👍3

@patrikhuber I think a first approximation of this would be pretty easy. Within the buildtrees/<portname> directory, there is a subdirectory src and a subdirectory for each build (with name <triplet>-<dbg or rel>). So a vcpkg option to purge build files could just delete these subdirectories while leaving src.

This would have some problems. Generated source files, e.g. as created by protoc or moc, would be deleted. But I think that, to since problems like that, you would need help from individual ports rather than a heuristic algorithm.