Windows shell extensions: Use custom GUIDs via CMake and prepare MSI reg
authorMichael Schuster <michael@schuster.ms>
Tue, 18 Aug 2020 16:12:29 +0000 (18:12 +0200)
committerMichael Schuster <michael@schuster.ms>
Thu, 20 Aug 2020 16:50:05 +0000 (18:50 +0200)
commit8ce13b7bdb0d14e8335ab33ff7a223ed02157114
treeca02928f26d44ad304e758c89776c6b38b820658
parent4675869fb3961cec78241cb961d4e6c0bc3fa8b5
Windows shell extensions: Use custom GUIDs via CMake and prepare MSI reg

Previously side by side installation with ownCloud or other NC custom builds would break the shell integration because the same GUIDs and registry keys were used.

Now we specify our custom GUIDs in NEXTCLOUD.cmake and use CMake to generate a header file and WiX (MSI) include file with these constants.

Note: Using generators like "guidgen" or "uuidgen" ensures that GUIDs are unique, as manual changes are not guaranteed to be.

Signed-off-by: Michael Schuster <michael@schuster.ms>
NEXTCLOUD.cmake
shell_integration/windows/CMakeLists.txt
shell_integration/windows/OCContextMenu/dllmain.cpp
shell_integration/windows/OCOverlays/DllMain.cpp
shell_integration/windows/OCOverlays/OverlayConstants.h [deleted file]
shell_integration/windows/WinShellExtConstants.h.in [new file with mode: 0644]
shell_integration/windows/WinShellExtConstants.wxi.in [new file with mode: 0644]