0

This old question covers a tried and tested way to manually copy known dependency files during a build: Copying a DLL's dependencies in Visual Studio

But it's a decade old and I wondered if there is a more modern way in C++ projects. For example, vcpkg not only automatically copies DLLs for you, it figures out which ones you need purely based on the headers you #include. Which makes me wonder if the same approach can be used for DLLs in other SDKs and so on which I need to copy? These can change names between versions etc so it's nasty to have a manual copy SomeDLL3_4_5.dll step which then has to be updated when the new library version comes out.

Is this feasible?

Mr. Boy
  • 57,008
  • 88
  • 294
  • 540

0 Answers0