|
09-18-2017, 10:08 PM
|
#41
|
Human being with feelings
Join Date: Nov 2008
Location: Darmstadt, Germany
Posts: 673
|
Quote:
Originally Posted by olilarkin
was that VST3SDK or my vs2017 branch? think i got confused
|
The VST3_SDKs CMakeLists.txt
|
|
|
09-19-2017, 05:34 AM
|
#42
|
Human being with feelings
Join Date: Apr 2009
Location: Berlin, Germany
Posts: 1,248
|
ah ok. good
|
|
|
09-19-2017, 02:44 PM
|
#43
|
Human being with feelings
Join Date: May 2015
Location: Serbia
Posts: 654
|
I will have to check that cmake projects but if this simplifies cairo compiling I am all in.
|
|
|
10-03-2017, 09:21 AM
|
#44
|
Human being with feelings
Join Date: Apr 2009
Location: Berlin, Germany
Posts: 1,248
|
I'm currently in the process of a major rework of the WDLOL project structure. Separating Iplug from WDL and making lice optional. I don't like to do massive changes like this too often. It means everyone will have to reduplicate iplugeffect
https://github.com/olilarkin/wdl-ol/tree/vs2017
localhost would you mind having a look at what I'm doing and suggest how I can Include cmake so that the template project has a set up ready to use with continuous integration? I am completely clueless about cmake. If there is anything about what I'm doing that is incompatible with cmake, then it will be great to know now so that I don't have to change the project structure again
Thanks!
|
|
|
10-07-2017, 12:44 AM
|
#45
|
Human being with feelings
Join Date: Nov 2008
Location: Darmstadt, Germany
Posts: 673
|
Quote:
Originally Posted by Youlean
I will have to check that cmake projects but if this simplifies cairo compiling I am all in.
|
I doubt it, as cairo doesn't offer a CMake build itself. But you could have a look into https://github.com/CMakePorts/cairo
Quote:
Originally Posted by olilarkin
I'm currently in the process of a major rework of the WDLOL project structure. Separating Iplug from WDL and making lice optional. I don't like to do massive changes like this too often. It means everyone will have to reduplicate iplugeffect
https://github.com/olilarkin/wdl-ol/tree/vs2017
localhost would you mind having a look at what I'm doing and suggest how I can Include cmake so that the template project has a set up ready to use with continuous integration? I am completely clueless about cmake. If there is anything about what I'm doing that is incompatible with cmake, then it will be great to know now so that I don't have to change the project structure again
Thanks!
|
I'll try to look into it this weekend or some time next week. If you have a look at my fork, the CMakeLists.txt for the individual plugins are very simple, so duplication is almost unnecessary: https://github.com/l0calh05t/wdl-ol/...CMakeLists.txt (the custom command is defined in the IPlug CMakeLists.txt: https://github.com/l0calh05t/wdl-ol/...CMakeLists.txt)
Some of the files that are very similar, like the resource files could also be solved using configure_file.
|
|
|
12-07-2017, 02:57 AM
|
#46
|
Human being with feelings
Join Date: Aug 2017
Posts: 50
|
Looking around for CMake and wdl, I've found this https://github.com/fab672000/wdl-fab
Does it sound like a good start ? I don't know very much about CMake for now
|
|
|
12-21-2017, 04:45 AM
|
#47
|
Human being with feelings
Join Date: Jul 2016
Posts: 6
|
status cmake branch
@l0calh05t What's the status of your cmake branch in terms of OSX? From the CMakeLists.txt I'd deduce it's currently ready for VST2. I see some commented lines for VST3, and some boilerplate for CA (AudioUnit).
I'm mainly interested in getting AU to work. But with wdl-fab's 2014 stuff I can already get VST2/VST3 to compile fine, so maybe I can help integrating VST3 into your branch, and start some work on AU.
With wdl-fab I can get a long way with AU -- it compiles fine, and the component's Content folder looks like it has all the magic it needs: PkgInfo, plist and rsrc file. But I can't get auval to notice the plugin, it's like it's not even there.
Are you on IRC? Or do you wanna do all discussion here? I'm available per email on izmael verhage [4t] g33ma1l.c0m one word normal spelling.
|
|
|
12-22-2017, 03:23 AM
|
#48
|
Human being with feelings
Join Date: Mar 2016
Posts: 234
|
Quote:
Originally Posted by izmael
Are you on IRC? Or do you wanna do all discussion here? I'm available per email on izmael verhage [4t] g33ma1l.c0m one word normal spelling.
|
Check it out this https://forum.cockos.com/showthread.php?t=200134 :P
|
|
|
01-10-2018, 06:17 PM
|
#49
|
Human being with feelings
Join Date: Apr 2009
Location: Berlin, Germany
Posts: 1,248
|
Quote:
Originally Posted by l0calh05t
|
things are moving along nicely, and it would be great if you could take a look at getting cmake working with the latest developments: https://github.com/olilarkin/wdl-ol/tree/iplugquake
windows updates coming soon
|
|
|
01-26-2018, 03:42 PM
|
#50
|
Human being with feelings
Join Date: Nov 2008
Location: Darmstadt, Germany
Posts: 673
|
Quote:
Originally Posted by izmael
@l0calh05t What's the status of your cmake branch in terms of OSX? From the CMakeLists.txt I'd deduce it's currently ready for VST2. I see some commented lines for VST3, and some boilerplate for CA (AudioUnit).
I'm mainly interested in getting AU to work. But with wdl-fab's 2014 stuff I can already get VST2/VST3 to compile fine, so maybe I can help integrating VST3 into your branch, and start some work on AU.
With wdl-fab I can get a long way with AU -- it compiles fine, and the component's Content folder looks like it has all the magic it needs: PkgInfo, plist and rsrc file. But I can't get auval to notice the plugin, it's like it's not even there.
Are you on IRC? Or do you wanna do all discussion here? I'm available per email on izmael verhage [4t] g33ma1l.c0m one word normal spelling.
|
Due to lack of a Mac, not well But you are welcome to fork my cmake branch and provide a pull request.
|
|
|
01-26-2018, 03:43 PM
|
#51
|
Human being with feelings
Join Date: Nov 2008
Location: Darmstadt, Germany
Posts: 673
|
Quote:
Originally Posted by olilarkin
|
Have been very busy the past few weeks, but I'll try to look into it.
So I should try to merge the iplugquake branch into my cmake branch and see what happens? Any important features to look out for?
|
|
|
01-26-2018, 04:02 PM
|
#52
|
Human being with feelings
Join Date: Apr 2009
Location: Berlin, Germany
Posts: 1,248
|
no I wouldn't do that. I've changed the project structure, I would fork iplugquake and start afresh. You can just do it for IPlugEffect
if you'd like - join us on the new slack channel: https://join.slack.com/t/iplug-users...TRkZDE3YWEzMWI
|
|
|
01-27-2018, 02:41 AM
|
#53
|
Human being with feelings
Join Date: Nov 2008
Location: Darmstadt, Germany
Posts: 673
|
Quote:
Originally Posted by olilarkin
|
I tried a merge after all. Didn't get VST3 to build yet. Mostly I only had to shift around a few of the CMakeFiles.txt. The current state is at https://github.com/l0calh05t/wdl-ol/...ake-iplugquake.
Oh, and the invite link isn't active anymore according to slack (which I haven't used before, assuming its kinda like Atlassian HipChat?). Maybe you should send me one in a PM.
|
|
|
01-27-2018, 04:23 AM
|
#54
|
Human being with feelings
Join Date: Apr 2009
Location: Berlin, Germany
Posts: 1,248
|
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 03:47 AM.
|