Cmake copy file after build12/2/2023 ![]() I haven’t played too much with CPack, but it seems like it would be quite difficult to set up for plugin installers, for the reasons you’ve mentioned: CPack tries to run the install on the build system before packaging, which may require elevated permissions. Would you say that what I’m trying here is a bad idea in general or is it a good idea in general, simply done in a wrong way? would you say that what I’m trying here is a bad idea in general or is it a good idea in general, simply done in a wrong way? I get the feeling that although installer creation with CPack seems super easy at first, it is deeply tied into the CMake install logic and therefore dependent on how the JUCE CMake implementation uses that under the hood. Not sure why, probably I understand something wrong here due to the lack of CMake experience. Second problem: Both, Mac and Windows installers created this way try to install JUCE with all its sources and as Unspecified component along with the plugin components, although I specify SET (CPACK_COMPONENTS_ALL VST3 AU). On stackoverflow someone suggested to use relative paths and set CMAKE_INSTALL_PREFIX to point to the base directory, however that leads to an installation relative to the application directory Of course my goal is to create a Cross-Platform capable installer in the end with minimal effort.įirst problem I encountered: Replicating the solution from above for windows with the windows specific paths lead to an error that absolute paths are not allowed as destinations. Update: Seems like all this is not as simple for a non CMake-Pro like me as I thought Can CPack run without installing everything to the location where the generated installer would install the binaries to so that running cpack is possible without root permissions?. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |