Can Boost be built in Manifest mode ?

[johne53]

If I'm in classic mode (i.e. in the vcpkg root folder) this command will show me a list boost packages to be built:-

./vcpkg install boost --dry-run

But if I'm in Manifest mode (i.e. in vcpkg/ports/boost) and I issue this command:-

../.../vcpkg install --dry-run

it complains that Boost cannot be built:-

error: D:\vcpkg-stuff\gnu-windows\src\vcpkg\ports\boost\vcpkg.json was rejected because it uses "version>=" and does not have a "builtin-baseline". This can be fixed by removing the uses of "version>=" or adding a "builtin-baseline".
See vcpkg help versioning for more information.

I've built various other ports which specified a version number but no builtin-baseline but the difference in ports/boost is that vcpkg.json specifies version numbers for its dependencies (which the others didn't, so far).

I'm sure I can add a builtin-baseline but I figured I should flag this up to the support guys.

[johne53]

Groan... this isn't as simple as I thought. Prior to installing boost I'd just spent nearly 2 hours installing glib. But after copying boost's vcpkg.json file (into my build folder) I added the builtin-baseline and ran a dry run - but vcpkg now gives me this message:-

The following packages will be removed:
    gettext:x64-windows
    gettext-libintl:x64-windows
    glib:x64-windows
    libiconv:x64-windows
    pcre:x64-windows
    pcre2:x64-windows

Instead of copying boost's vcpkg.json file, should I have just added its contents to the manifest I'd already created for glib?

[Edit...] Or is there maybe a command-line option I can send to vcpkg.exe to tell it not to uninstall the stuff I've already built?

[johne53]

Actually I'm not having much success building Boost in Classic mode either. I started a build earlier (I can't quite remember how many packages it wanted to build but it was something like 159). But when it gets to 35 packages from the end it gives me the text (and error) shown below...

Is there any way to fix this?:-

openssl:x64-windows@3.6.1#2 package ABI: e91d37696eb6dafeced2a77d41b633ad53e47e978a5426bfa9abd00fd3a02f49
Building openssl:x64-windows@3.6.1#2...
-- Using cached openssl-openssl-openssl-3.6.1.tar.gz
-- Cleaning sources at D:/vcpkg-stuff/gnu-windows/src/vcpkg/buildtrees/openssl/src/nssl-3.6.1-c0028aa207.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source D:/vcpkg-stuff/gnu-windows/src/vcpkg/downloads/openssl-openssl-openssl-3.6.1.tar.gz
-- Applying patch cmake-config.patch
-- Applying patch command-line-length.patch
-- Applying patch script-prefix.patch
-- Applying patch windows/install-layout.patch
-- Applying patch windows/install-pdbs.patch
-- Applying patch windows/install-programs.diff
-- Applying patch unix/android-cc.patch
-- Applying patch unix/move-openssldir.patch
-- Applying patch unix/no-empty-dirs.patch
-- Applying patch unix/no-static-libs-for-shared.patch
-- Applying patch fix-mingw-build.patch
-- Using source at D:/vcpkg-stuff/gnu-windows/src/vcpkg/buildtrees/openssl/src/nssl-3.6.1-c0028aa207.clean
-- Getting CMake variables for x64-windows
-- Loading CMake variables from D:/vcpkg-stuff/gnu-windows/src/vcpkg/buildtrees/openssl/cmake-get-vars_C_CXX-x64-windows.cmake.log
-- Using cached strawberry-perl-5.42.0.1-64bit-portable.zip
CMake Error at scripts/cmake/vcpkg_extract_archive.cmake:19 (message):
  D:/vcpkg-stuff/gnu-windows/src/vcpkg/downloads/tools/perl/5.42.0.1 was an
  extraction target, but it already exists.
Call Stack (most recent call first):
  scripts/cmake/vcpkg_find_acquire_program.cmake:247 (vcpkg_extract_archive)
  ports/openssl/windows/portfile.cmake:6 (vcpkg_find_acquire_program)
  ports/openssl/portfile.cmake:78 (include)
  scripts/ports.cmake:206 (include)

[johne53]

Sorry guys, I know it's a Sunday and I don't want to disturb anyone's weekend but I desperately need some help with this error:-

-- Using cached strawberry-perl-5.42.0.1-64bit-portable.zip
CMake Error at scripts/cmake/vcpkg_extract_archive.cmake:19 (message):
  D:/vcpkg-stuff/gnu-windows/src/vcpkg/downloads/tools/perl/5.42.0.1 was an
  extraction target, but it already exists.

If I'm reading this correctly, Boost has reached a stage where it's trying to install openssl ver3.6.1#2 and for whatever reason, it needs to install strawberry-perl ver5.42.0.1. But it can't install it because it's already installed (which begs the question... why is vcpkg even trying to re-install it??)

If someone can figure out a fix for this, do please let me know!

[Edit..] The issue I reported below isn't urgent but I could definitely do with some help for that one. In the meantime however I've gotten a tiny bit further with openssl:-

I navigated to the folder called vcpkg\download\tools and deleted the subfolder called perl. I then ran the openssl build again and the last few lines looked like this:-

-- Getting CMake variables for x64-windows
-- Loading CMake variables from D:/vcpkg-stuff/gnu-windows/src/vcpkg/buildtrees/openssl/cmake-get-vars_C_CXX-x64-windows.cmake.log
Downloading https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/download/SP_54201_64bit/strawberry-perl-5.42.0.1-64bit-portable.zip -> strawberry-perl-5.42.0.1-64bit-portable.zip
Successfully downloaded strawberry-perl-5.42.0.1-64bit-portable.zip
Downloading nasm-3.01-win64.zip, trying https://www.nasm.us/pub/nasm/releasebuilds/3.01/win64/nasm-3.01-win64.zip
Successfully downloaded nasm-3.01-win64.zip
-- Getting CMake variables for x64-windows
Downloading jom_1_1_6.zip, trying https://download.qt.io/official_releases/jom/jom_1_1_6.zip
Successfully downloaded jom_1_1_6.zip

At that point the build hung (for over half an hour) before adding these 2 lines:-

-- Prerunning x64-windows-dbg
-- Building x64-windows-dbg

and it's now been stuck there for over 20 minutes!

So either there's some weird speed issue at my end (unlikely) or maybe the openssl build has been broken for a while but it just so happens that no-one's noticed yet :-(

[johne53]

And also this one if someone's got some time:-

The following packages will be removed:
    gettext:x64-windows
    gettext-libintl:x64-windows
    glib:x64-windows
    libiconv:x64-windows
    pcre:x64-windows
    pcre2:x64-windows

Is there maybe a command-line option I can send to vcpkg.exe to tell it not to uninstall the stuff I've already built?

I'm not sure if it'll be relevant in Manifest mode but when trying a build just now in Classic mode I noticed this message:-

Use --editable to skip cleaning for the packages you specify.

Is that potentially a way to prevent Manifest mode from removing previously built packages when it needs to install some unrelated package? And if so, can someone point me to an example somewhere?