nextcloud-desktop/shell_integration/windows/CMakeLists.txt

# Use static runtime for all subdirectories
foreach(buildType "" "_DEBUG" "_MINSIZEREL" "_RELEASE" "_RELWITHDEBINFO")
    string(REPLACE "/MD" "/MT" "CMAKE_CXX_FLAGS${buildType}" "${CMAKE_CXX_FLAGS${buildType}}")
endforeach()

include_directories(
    ${CMAKE_CURRENT_BINARY_DIR}
)
configure_file(WinShellExtConstants.h.in ${CMAKE_CURRENT_BINARY_DIR}/WinShellExtConstants.h)
configure_file(WinShellExt.wxs.in ${CMAKE_CURRENT_BINARY_DIR}/WinShellExt.wxs)

add_subdirectory(NCContextMenu)
add_subdirectory(NCOverlays)
add_subdirectory(NCUtil)
Avoid warning because /MT overrides /MD flag Signed-off-by: Michael Schuster <michael@schuster.ms> 2018-10-29 18:29:04 +03:00			`# Use static runtime for all subdirectories`
			`foreach(buildType "" "_DEBUG" "_MINSIZEREL" "_RELEASE" "_RELWITHDEBINFO")`
			`string(REPLACE "/MD" "/MT" "CMAKE_CXX_FLAGS${buildType}" "${CMAKE_CXX_FLAGS${buildType}}")`
			`endforeach()`

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> 2020-08-18 19:12:29 +03:00			`include_directories(`
			`${CMAKE_CURRENT_BINARY_DIR}`
			`)`
			`configure_file(WinShellExtConstants.h.in ${CMAKE_CURRENT_BINARY_DIR}/WinShellExtConstants.h)`
Windows shell extensions: Add WiX (MSI) fragment Use CMake to generate a WXI fragment to handle the DLL registration and file deployment for the shellext components. Signed-off-by: Michael Schuster <michael@schuster.ms> 2020-08-18 22:42:31 +03:00			`configure_file(WinShellExt.wxs.in ${CMAKE_CURRENT_BINARY_DIR}/WinShellExt.wxs)`
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> 2020-08-18 19:12:29 +03:00
Windows shell extensions: Rename all files and classes from OC* to NC*, update version info This also ensures a clear separation in the system registry. SelfReg is not recommended by Microsoft and will be handled by the MSI package to allow proper Repair and Uninstall. However, we keep it for backward compatibility with the NSIS installer. For details see: https://stackoverflow.com/questions/364187/how-do-you-register-a-win32-com-dll-file-in-wix-3#364210 https://docs.microsoft.com/en-us/windows/win32/msi/selfreg-table#remarks Another fix by this commit: The "Version" registry value in the NCOverlays self reg should be a key and not a value. Details: https://wixtoolset.org/documentation/manual/v3/xsd/wix/class.html Example: [HKCR\CLSID\{01234567-89AB-CDEF-0123-456789ABCDEF}\Version] @="1.0.0.0" Signed-off-by: Michael Schuster <michael@schuster.ms> 2020-08-18 20:11:08 +03:00			`add_subdirectory(NCContextMenu)`
			`add_subdirectory(NCOverlays)`
			`add_subdirectory(NCUtil)`
Build Explorer extension if building with MSVC 2018-01-04 22:51:12 +03:00