diff options
author | Jocelyn Turcotte <jturcotte@woboq.com> | 2015-02-04 15:15:06 +0300 |
---|---|---|
committer | Jocelyn Turcotte <turcotte.j@gmail.com> | 2015-02-04 17:00:22 +0300 |
commit | 1ac523ec01be0b68063564769e07f4db3b92f1e7 (patch) | |
tree | d1fe9be54dada83f58dcbbd04a94a2069ae4205c /cmake | |
parent | 43a51c1befed05bcf546ca9ea826c8dc2d0e3818 (diff) |
Output libocsync and libowncloudsync in the bin directory
Windows finds DLLs using PATH or the directory of the process'
executable. By outputing those dependend DLLs together with
owncloud.exe, the developer only need to have OpenSSL's bin
and the qtkeychain build directory in his PATH to let the
dynamic linker find them.
As the documentation of RUNTIME_OUTPUT_DIRECTORY points out,
this only affects windows as other platforms don't consider
libraries as runtime targets.
Diffstat (limited to 'cmake')
-rw-r--r-- | cmake/modules/NSIS.template.in | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/cmake/modules/NSIS.template.in b/cmake/modules/NSIS.template.in index 7aab82333..3d56479e3 100644 --- a/cmake/modules/NSIS.template.in +++ b/cmake/modules/NSIS.template.in @@ -385,8 +385,8 @@ Section "${APPLICATION_NAME}" SEC_APPLICATION ;Main executable & csync File "${BUILD_PATH}\bin\${APPLICATION_EXECUTABLE}" File "${BUILD_PATH}\bin\${APPLICATION_CMD_EXECUTABLE}" - File "${BUILD_PATH}\src\libsync\lib${APPLICATION_SHORTNAME}sync.dll" - File "${BUILD_PATH}\csync\src\libocsync.dll" + File "${BUILD_PATH}\bin\lib${APPLICATION_SHORTNAME}sync.dll" + File "${BUILD_PATH}\bin\libocsync.dll" File "${BUILD_PATH}\src\gui\mirall_*.qm" ; Make sure only to copy qt, not qt_help, etc |