miniforge VS Vcpkg

Nope they don't use venv for any of the oobabooga# variants nor is it recommended for the git version. I'm using https://github.com/conda-forge/miniforge#mambaforge-pypy3 (better version of the recommended conda) for the git variant. The oobabooga* variant uses micro/miniconda (I suck with names) which you can easily drop into with cmd_?something? and does it all internally. Like whoever built that whole environment setup for the _windows/linux/mac did a great job.

wget https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-Linux-aarch64.sh .

Mambaforge!

Just to further clarify: you don't need mamba to avoid the Anaconda distribution. The place you get mambaforge also supplies (and originally supplied) miniforge, which is miniconda with conda-forge set as the default channel. All the *forge installers do in this regard is automatically set conda-forge as the default (and only) channel, which is something one can do manually with miniconda.

I'd recommend using miniforge if you're comfortable with CLIs, otherwise https://www.anaconda.com/.

Tip 1: To use less of your Codespaces resources start with a smaller image like Miniconda or Miniforge and install only what you need.

miniforge, no need to deal with conda environments anymore. https://github.com/conda-forge/miniforge

5.4.5 can be compromised

https://github.com/microsoft/vcpkg/issues/37197

vcpkg may expire assets after 1.5 years, so achieve long-term reproducibility you will need to cache your dependencies.... Somewhere. Not sure what the expected solution is.

https://github.com/microsoft/vcpkg/pull/30546#issuecomment-1...

There were various approaches recommended depending on our language and ecosystem. My classmates who developed using Node.js were recommended npm, and PyPI or poetry for Python. Since my program is written in C++, I was recommended to look into one of vcpkg or conan, but I ultimately did not use either package manager.

Which dependencies are not in vcpkg? We can ask them to add it. It’s pretty easy just open an issue there https://github.com/microsoft/vcpkg/issues .

./vcpkg search netcdf gdal[netcdf] Enable NetCDF support minc 2.4.03#3 MINC - Medical Image NetCDF or MINC isn't netCDF minc[minc1] Support minc1 file format, requires NETCDF netcdf-c 4.8.1#2 A set of self-describing, machine-independent data formats that support th... netcdf-c[dap] Build with DAP remote access client support netcdf-c[hdf5] Build with HDF5 support netcdf-c[nczarr] Build with NCZarr cloud storage access support netcdf-c[nczarr-zip] Build with NCZarr ZIP support netcdf-c[netcdf-4] Build with netCDF-4 support netcdf-c[platform-default-features] Enable platform-dependent default features netcdf-c[tools] Build utilities netcdf-cxx4 4.3.1#4 a set of machine-independent data formats that support the creation, acces... The result may be outdated. Run `git pull` to get the latest results. If your port is not listed, please open an issue at and/or consider making a pull request. - https://github.com/Microsoft/vcpkg/issues

The hyperscan update to vcpkg seems to have happened from 5.4.0 to 5.4.2 in this commit on Apr 20.

Dear Fictrac team, I am hoping to install Fictrac in our windows 11 x64 laptop (Visual Studio 2019, cMake 3.26.4). I followed the installation guideline on github page fictrac and used the latest vcpkg

This works fine if one wants to do stuff like clang main.cpp -lvulkan, or even find_package(Vulkan REQUIRED) in CMake, but it doesn't define VULKAN_SDK, and therefore doesn't work with vcpkg's Vulkan support, for instance. A fair bit of Vulkan development, tutorials, etc. assume that the entire SDK is installed, as-is.