#vcpkg — Public Fediverse posts

@ocornut @bert_hubert @ariadne And then there are package managera like #vcpkg and devendor and patch and devendor and patch and ...

@ocornut @bert_hubert @ariadne And then there are package managera like #vcpkg and devendor and patch and devendor and patch and ...

@ocornut @bert_hubert @ariadne And then there are package managera like #vcpkg and devendor and patch and devendor and patch and ...

@ocornut @bert_hubert @ariadne And then there are package managera like #vcpkg and devendor and patch and devendor and patch and ...

Hey everyone! It's been a little bit since our last post, so we'll detail what's happening here!

Unfortunately, we don't have a whole lot to report, but we have been readying a new release of #libmad. The last thing we have will be for source packaging via CPack as we will now start providing our own source tarballs.

Once we get libmad 0.16.5 released and in #vcpkg, we'll get going on #Tenacity 1.3.5, which will feature updated dependencies mainly. That also means we'll update our Flatpak too!

Hey everyone! It's been a little bit since our last post, so we'll detail what's happening here!

Unfortunately, we don't have a whole lot to report, but we have been readying a new release of #libmad. The last thing we have will be for source packaging via CPack as we will now start providing our own source tarballs.

Once we get libmad 0.16.5 released and in #vcpkg, we'll get going on #Tenacity 1.3.5, which will feature updated dependencies mainly. That also means we'll update our Flatpak too!

Hey everyone! It's been a little bit since our last post, so we'll detail what's happening here!

Unfortunately, we don't have a whole lot to report, but we have been readying a new release of #libmad. The last thing we have will be for source packaging via CPack as we will now start providing our own source tarballs.

Once we get libmad 0.16.5 released and in #vcpkg, we'll get going on #Tenacity 1.3.5, which will feature updated dependencies mainly. That also means we'll update our Flatpak too!

Hey everyone! It's been a little bit since our last post, so we'll detail what's happening here!

Unfortunately, we don't have a whole lot to report, but we have been readying a new release of #libmad. The last thing we have will be for source packaging via CPack as we will now start providing our own source tarballs.

Once we get libmad 0.16.5 released and in #vcpkg, we'll get going on #Tenacity 1.3.5, which will feature updated dependencies mainly. That also means we'll update our Flatpak too!

One thing I don't like about CMake is that it stores so much state in the build directory and you have to nuke it all the time to be sure it's not picking up something old/wrong. Mainly an issue while you're trying to get a build going. As vcpkg also stores built stuff in the same directory you'll be staring at loooong builds just to try to get anything to build.

#cmake #vcpkg #winduhs

One thing I don't like about CMake is that it stores so much state in the build directory and you have to nuke it all the time to be sure it's not picking up something old/wrong. Mainly an issue while you're trying to get a build going. As vcpkg also stores built stuff in the same directory you'll be staring at loooong builds just to try to get anything to build.

#cmake #vcpkg #winduhs

One thing I don't like about CMake is that it stores so much state in the build directory and you have to nuke it all the time to be sure it's not picking up something old/wrong. Mainly an issue while you're trying to get a build going. As vcpkg also stores built stuff in the same directory you'll be staring at loooong builds just to try to get anything to build.

#cmake #vcpkg #winduhs

One thing I don't like about CMake is that it stores so much state in the build directory and you have to nuke it all the time to be sure it's not picking up something old/wrong. Mainly an issue while you're trying to get a build going. As vcpkg also stores built stuff in the same directory you'll be staring at loooong builds just to try to get anything to build.

#cmake #vcpkg #winduhs

Building your project and #vcpkg dependencies with your toolchain.

https://sdowney.org/posts/building-vcpkg-dependencies-with-project-toolchain/

Because someone was wrong on the internet.

Building your project and #vcpkg dependencies with your toolchain.

https://sdowney.org/posts/building-vcpkg-dependencies-with-project-toolchain/

Because someone was wrong on the internet.

Building your project and #vcpkg dependencies with your toolchain.

https://sdowney.org/posts/building-vcpkg-dependencies-with-project-toolchain/

Because someone was wrong on the internet.

Building your project and #vcpkg dependencies with your toolchain.

https://sdowney.org/posts/building-vcpkg-dependencies-with-project-toolchain/

Because someone was wrong on the internet.

#vcpkg
No matter what any summary says, in order to build dependencies with a project toolchain file, you need a custom "triple" file that defines VCPKG_CHAINLOAD_TOOLCHAIN_FILE.

In addition, there's a `vcpkg install` invocation between your cmake and vcpkg, so you need to communicate with the triple file via environment variable, e.g. $ENV{PROJECT_VCPKG_TOOLCHAIN}

No idea what violence this does to vcpkg caching yet.

#vcpkg
No matter what any summary says, in order to build dependencies with a project toolchain file, you need a custom "triple" file that defines VCPKG_CHAINLOAD_TOOLCHAIN_FILE.

In addition, there's a `vcpkg install` invocation between your cmake and vcpkg, so you need to communicate with the triple file via environment variable, e.g. $ENV{PROJECT_VCPKG_TOOLCHAIN}

No idea what violence this does to vcpkg caching yet.

#vcpkg
No matter what any summary says, in order to build dependencies with a project toolchain file, you need a custom "triple" file that defines VCPKG_CHAINLOAD_TOOLCHAIN_FILE.

In addition, there's a `vcpkg install` invocation between your cmake and vcpkg, so you need to communicate with the triple file via environment variable, e.g. $ENV{PROJECT_VCPKG_TOOLCHAIN}

No idea what violence this does to vcpkg caching yet.

#vcpkg
No matter what any summary says, in order to build dependencies with a project toolchain file, you need a custom "triple" file that defines VCPKG_CHAINLOAD_TOOLCHAIN_FILE.

In addition, there's a `vcpkg install` invocation between your cmake and vcpkg, so you need to communicate with the triple file via environment variable, e.g. $ENV{PROJECT_VCPKG_TOOLCHAIN}

No idea what violence this does to vcpkg caching yet.

@andrewnez #vcpkg relies on git. The version database is plain files with git-tree pointers into the history.

@andrewnez #vcpkg relies on git. The version database is plain files with git-tree pointers into the history.

@andrewnez #vcpkg relies on git. The version database is plain files with git-tree pointers into the history.

@andrewnez #vcpkg relies on git. The version database is plain files with git-tree pointers into the history.

**GitHub - doobiusP/cmexl**: Công cụ CLI xây dựng dự án CMake và template module linh hoạt, hỗ trợ pipeline full (from cấu hình đến đóng gói), tích hợp vcpkg, quản lý component riêng biệt, và cấu hình module linh hoạt. Dự án side project giúp tác giả học sâu về CMake & Go. 🚀 Học hỏi & chia sẻ kinh nghiệm về hệ thống build!

#CMake #OpenSource #SideProject #ViệcHọc #LậpTrình #GitHub #DevTools #MãMở #CôngCụPhátTriển #HọcCMake #ViệcSide #TechPost #DevLife #Cplusplus #Golang #Vcpkg #CMakeTool #Co

Its amazing that in C++ #cpp its practically impossible to get a decent #s3 client. The minio-cpp requires #vcpkg and the #aws sdk results in 22 GiB binary folder...

There is a small header only library but it has 0 stars and fails compilation because uint8_t is undefined.

What fun.

Its amazing that in C++ #cpp its practically impossible to get a decent #s3 client. The minio-cpp requires #vcpkg and the #aws sdk results in 22 GiB binary folder...

There is a small header only library but it has 0 stars and fails compilation because uint8_t is undefined.

What fun.

Its amazing that in C++ #cpp its practically impossible to get a decent #s3 client. The minio-cpp requires #vcpkg and the #aws sdk results in 22 GiB binary folder...

There is a small header only library but it has 0 stars and fails compilation because uint8_t is undefined.

What fun.

Dew Drop – October 2, 2025 (#4510)

https://fed.brid.gy/r/https://alvinashcraft.com/2025/10/02/dew-drop-october-2-2025-4510/

Dependabot support for vcpkg | by James Magee.

https://devblogs.microsoft.com/cppblog/dependabot-support-for-vcpkg/

#cpp #vcpkg #dependabot #devsecops

Dependabot support for vcpkg | by James Magee.

https://devblogs.microsoft.com/cppblog/dependabot-support-for-vcpkg/

#cpp #vcpkg #dependabot #devsecops

Dependabot support for vcpkg | by James Magee.

https://devblogs.microsoft.com/cppblog/dependabot-support-for-vcpkg/

#cpp #vcpkg #dependabot #devsecops

Dependabot support for vcpkg | by James Magee.

https://devblogs.microsoft.com/cppblog/dependabot-support-for-vcpkg/

#cpp #vcpkg #dependabot #devsecops

I po raz kolejny, przypadkowy projekt używający CMake psuje zgodność z systemami, na których jego zależności nie zbudowano przy pomocy CMake (tylko używając Mesona). Bo po co używać pkg-configa, jak można używać plików config, generowanych przez CMake?

https://github.com/Blosc/c-blosc2/issues/687

EDIT: wygląda na to, że to zmiany pod #VcPkg. Zapewne przypadkowe, ale czy warto przepuścić okazję, by winić #Microsoft za zepsucie paczek dla Linuksów?

https://github.com/Blosc/c-blosc2/pull/682

#Fedora #Gentoo

I po raz kolejny, przypadkowy projekt używający CMake psuje zgodność z systemami, na których jego zależności nie zbudowano przy pomocy CMake (tylko używając Mesona). Bo po co używać pkg-configa, jak można używać plików config, generowanych przez CMake?

https://github.com/Blosc/c-blosc2/issues/687

EDIT: wygląda na to, że to zmiany pod #VcPkg. Zapewne przypadkowe, ale czy warto przepuścić okazję, by winić #Microsoft za zepsucie paczek dla Linuksów?

https://github.com/Blosc/c-blosc2/pull/682

#Fedora #Gentoo

I po raz kolejny, przypadkowy projekt używający CMake psuje zgodność z systemami, na których jego zależności nie zbudowano przy pomocy CMake (tylko używając Mesona). Bo po co używać pkg-configa, jak można używać plików config, generowanych przez CMake?

https://github.com/Blosc/c-blosc2/issues/687

EDIT: wygląda na to, że to zmiany pod #VcPkg. Zapewne przypadkowe, ale czy warto przepuścić okazję, by winić #Microsoft za zepsucie paczek dla Linuksów?

https://github.com/Blosc/c-blosc2/pull/682

#Fedora #Gentoo

Once again, a #CMake project is breaking compatibility with systems that aren't building its dependencies via CMake (but are using Meson instead). Because why use pkg-config when you can use generated CMake configs instead?

https://github.com/Blosc/c-blosc2/issues/687

EDIT: looks like this was done to accommodate #VcPkg. Surely accidental, but why not bash #Microsoft for breaking Linux packages anyway?

https://github.com/Blosc/c-blosc2/pull/682

#Fedora #Gentoo #packaging

Once again, a #CMake project is breaking compatibility with systems that aren't building its dependencies via CMake (but are using Meson instead). Because why use pkg-config when you can use generated CMake configs instead?

https://github.com/Blosc/c-blosc2/issues/687

EDIT: looks like this was done to accommodate #VcPkg. Surely accidental, but why not bash #Microsoft for breaking Linux packages anyway?

https://github.com/Blosc/c-blosc2/pull/682

#Fedora #Gentoo #packaging

Once again, a #CMake project is breaking compatibility with systems that aren't building its dependencies via CMake (but are using Meson instead). Because why use pkg-config when you can use generated CMake configs instead?

https://github.com/Blosc/c-blosc2/issues/687

EDIT: looks like this was done to accommodate #VcPkg. Surely accidental, but why not bash #Microsoft for breaking Linux packages anyway?

https://github.com/Blosc/c-blosc2/pull/682

#Fedora #Gentoo #packaging

Once again, a #CMake project is breaking compatibility with systems that aren't building its dependencies via CMake (but are using Meson instead). Because why use pkg-config when you can use generated CMake configs instead?

https://github.com/Blosc/c-blosc2/issues/687

EDIT: looks like this was done to accommodate #VcPkg. Surely accidental, but why not bash #Microsoft for breaking Linux packages anyway?

https://github.com/Blosc/c-blosc2/pull/682

#Fedora #Gentoo #packaging

I was tired of adding libraries to my #cmake build files in one of my #opensource projects. It was all very tedious. Now, I've switched to #vcpkg , even though I initially rejected it completely. It wasn't standards-compliant enough for me.

Now, everything compiles smoothly on Windows, Linux, and even on my Android tablet with #termux.
#Programming #cpp

Управление зависимостями на C++ с помощью vcpkg registry и сервера кеширования

Здравствуйте, дорогие читатели Хабра! Я давно хотел поделиться своими знаниями о работе с реестрами под ключ, так как нигде нет четкой и последовательной информации по этой теме. Сегодня мы разберем, как управлять зависимостями через реестры vcpkg и как кэшировать их на сервере.

https://habr.com/ru/articles/916620/

#c++ #vcpkg #пакетный_менеджер #реестр_пакетов #vcpkg_registry #vcpkg_caching #nuget

Управление зависимостями на C++ с помощью vcpkg registry и сервера кеширования

Здравствуйте, дорогие читатели Хабра! Я давно хотел поделиться своими знаниями о работе с реестрами под ключ, так как нигде нет четкой и последовательной информации по этой теме. Сегодня мы разберем, как управлять зависимостями через реестры vcpkg и как кэшировать их на сервере.

https://habr.com/ru/articles/916620/

#c++ #vcpkg #пакетный_менеджер #реестр_пакетов #vcpkg_registry #vcpkg_caching #nuget

Yeah!

Nicht reviewte #PackageManager wie #npm, #Cargo, #Conan, #vcpkg sind die Zukunft!

https://www.heise.de/news/Remote-Access-Trojaner-in-npm-Paket-mit-40-000-woechentlichen-Downloads-gefunden-10377590.html

Nein und zum wiederholten Mal: Nein! Nicht!

Yeah!

Nicht reviewte #PackageManager wie #npm, #Cargo, #Conan, #vcpkg sind die Zukunft!

https://www.heise.de/news/Remote-Access-Trojaner-in-npm-Paket-mit-40-000-woechentlichen-Downloads-gefunden-10377590.html

Nein und zum wiederholten Mal: Nein! Nicht!

Yeah!

Nicht reviewte #PackageManager wie #npm, #Cargo, #Conan, #vcpkg sind die Zukunft!

https://www.heise.de/news/Remote-Access-Trojaner-in-npm-Paket-mit-40-000-woechentlichen-Downloads-gefunden-10377590.html

Nein und zum wiederholten Mal: Nein! Nicht!

Yeah!

Nicht reviewte #PackageManager wie #npm, #Cargo, #Conan, #vcpkg sind die Zukunft!

https://www.heise.de/news/Remote-Access-Trojaner-in-npm-Paket-mit-40-000-woechentlichen-Downloads-gefunden-10377590.html

Nein und zum wiederholten Mal: Nein! Nicht!

#vcpkg is supposed to be able to provide some level of automatic caching when running in a #github workflow. I had this working in the past, but lately it's been reporting that no packages are pulled from cache, which results in a half hour of wasted time spent rebuilding dependencies.

Opened an issue on the relevant vcpkg documentation page, but now I'm thinking it may be that vcpkg itself is using a recently deprecated GitHub caching API: https://github.com/microsoft/vcpkg/issues/45073

#vcpkg is supposed to be able to provide some level of automatic caching when running in a #github workflow. I had this working in the past, but lately it's been reporting that no packages are pulled from cache, which results in a half hour of wasted time spent rebuilding dependencies.

Opened an issue on the relevant vcpkg documentation page, but now I'm thinking it may be that vcpkg itself is using a recently deprecated GitHub caching API: https://github.com/microsoft/vcpkg/issues/45073

#vcpkg is supposed to be able to provide some level of automatic caching when running in a #github workflow. I had this working in the past, but lately it's been reporting that no packages are pulled from cache, which results in a half hour of wasted time spent rebuilding dependencies.

Opened an issue on the relevant vcpkg documentation page, but now I'm thinking it may be that vcpkg itself is using a recently deprecated GitHub caching API: https://github.com/microsoft/vcpkg/issues/45073

#vcpkg is supposed to be able to provide some level of automatic caching when running in a #github workflow. I had this working in the past, but lately it's been reporting that no packages are pulled from cache, which results in a half hour of wasted time spent rebuilding dependencies.

Opened an issue on the relevant vcpkg documentation page, but now I'm thinking it may be that vcpkg itself is using a recently deprecated GitHub caching API: https://github.com/microsoft/vcpkg/issues/45073

I wish all vcpkg packages had proper pkgconfig outputs.

#vcpkg

I wish all vcpkg packages had proper pkgconfig outputs.

#vcpkg

I wish all vcpkg packages had proper pkgconfig outputs.

#vcpkg

I wish all vcpkg packages had proper pkgconfig outputs.

#vcpkg

HowTo: создание двоичного SDK(набора библиотек) для Windows с использованием vcpkg

В этом HowTo мы рассмотрим подготовку пакетов vcpkg для использования в двоичном виде. В качестве "подопытных кроликов" будут выступать Qt6 , QCustomPlot и я. Spoiler: с QCustomPlot придется немного пострадать, но обычно все проще. TLDR: vcpkg export Далее

https://habr.com/ru/articles/894284/

#vcpkg #cmake #package_manager #qt #visual_studio

HowTo: создание двоичного SDK(набора библиотек) для Windows с использованием vcpkg

В этом HowTo мы рассмотрим подготовку пакетов vcpkg для использования в двоичном виде. В качестве "подопытных кроликов" будут выступать Qt6 , QCustomPlot и я. Spoiler: с QCustomPlot придется немного пострадать, но обычно все проще. TLDR: vcpkg export Далее

https://habr.com/ru/articles/894284/

#vcpkg #cmake #package_manager #qt #visual_studio

I've been using vcpkg a little bit for side projects, and looking into using for work as well.

We're using Skia and I'm getting pretty poor performance. I'm a bit worried that the vcpkg build uses msvc/cl (on Windows). No shade from me on msvc, but Skia has a bunch of clang-specific optimizations and doesn't run well when built with another compiler.

vcpkg ports are a bit opaque to me though and I'm not sure how to verify this. Anyone got ideas?

#vcpkg #cpp #SoftwareEngineering