-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CMakeLists.txt
should not reference user-specific homedir paths
#603
Comments
Weird, I didn't have that problem with CMake. You can change the Vst2 paths in the CMakeLists.txt file to C:/your repository path/Source/Misc/vst2sdk then it should find the right Vst2 folder. |
Indeed, I surely can! |
Good point about that changes should be made for "everybody". The problem is that we don't have access to "this" repository to update it. The altered CMakesLists.txt version should be on another fork. Please tell me if it builds if you changed the folder names. Because when I compare my CMakeLists.txt to the one in this repository, I'm missing a lot. Audio plugin settings from this repository: juce_add_plugin(ctrlr My CMakeLists.txt audio_plugin_settings: jucer_audio_plugin_settings( I made my CMakeListst.txt with a project called FRUT. That project was started before Juce came with its CMake API, keep in mind that it's far from an "official" way to make a CMakeLists.txt file. But it builds the build folder, generates .sln files for Visual Studio, and compiles the project like it should, you don't hear me complain. 2nd thought. The CMakeLists.txt file in this repository also precedes Juce's CMake API. I tried to make a CMakeLists.txt file according to that API but it's Juce. Complicated, we give you three sentences, figure out the rest of the three-page manual yourself. |
I started by trying to build from git and got this error message:
Then I noticed the user-specific path
/home/kbar
. And later I found all of these onCMakeLists.txt
as well:The text was updated successfully, but these errors were encountered: