-
Notifications
You must be signed in to change notification settings - Fork 404
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
Surge-VST2: build-osx.sh: VST2.4SDK not correctly referenced, so Surge.dylib not correctly built #113
Comments
this seems to be caused by
and
and
i'm wondering.. these used to work, i mean, i have the
set alright, but yet it feels like |
could this be related to
|
You don't have a valid |
@kzantow the thing with this is.. that it is a valid vst2.4sdk so what i'm really missing is, if
is the premake5.lua looking for them in the wrong place? I'm hesitant to start copying vst2.4sdk content into |
like, is it this?
otoh, in premake5.lua, under linux, it is not even referencing
|
Perhaps whoever set up the Linux target did not have VST2SDK available? I'm going to make a clean clone on my laptop to see the outcome. btw, this and #110 are explicitly linked, and are almost in effect duplicates, since the reason you miss a Surge.dylib is due to the build failing because it can't find the vst2 files. |
@asimilon yep, this is why i closed #110 and copied the text from there to #113 so that this is highlighted as the same issue. i'm getting stuff like this, and i'm not entirely sure why the builder doesn't find public.sdk/source
|
What is your exact output from I'm wondering if maybe you miss a trailing |
@asimilon hi
|
(VST24SDK is there just because i'm trying to stab in the dark and figure out wth is going on) |
about the trailing |
Permissions perhaps then? It unfortunately is something that's confined to your system :( |
Hey @esaruoho did this get sorted for you? It really does seem to be local-to-you. If not, could you try a clean checkout at master maybe? Or let us know latest error message? And if so, could you close the ticket? Thanks! |
I actually do trash the surge local repo on my drive pretty much daily just to make sure i don't have anything getting wrecked. |
i will do a clean checkout on master and paste what i get. just a sec |
ok.. here's the freshest errors: error1
error2
error3:
error4:
and last error
basically, looks like my "why yes, the folder is in now, what i COULD do, is try and use an implicit url (explicit url?)
let's see what happens this time. ... well, what do you know - it works: pro-tip: don't use also, how was i supposed to know this? :'( |
thanks for the handholding, @baconpaul , i guess i learned quite a bit on this one :) |
Well I'm not sure how anyone is supposed to know anything. But the problem you are having is the use of "" in shell which stops expansion. Compare:
~ is shell expanded and so if you don't know the expansion rules it can burn you. But a short version of the expansion rules is "in quotes it doesn't expand". And then the tools downstream look for absolute paths. Hope that helps. |
awesome! thanks! ...i really really should've thought of this one for sure. thanks for the expanded explanation, too. all I can say is |
type fix: change nsvg__parseLineJoin() default value to NSVG_JOIN_MITER
i'm wondering if i'm supposed to be able to build a macOS VST even with vst2.4sdk (working) there. this is what build-osx.sh says:
(from #110 )
Hi, I've got the export set ( export VST2SDK_DIR="~/work/VST2.4SDK" ) yet when I go to build surge-vst2 with xcode, I get these:
should these be found? they are most certainly "in there" ( see https://github.com/kurasu/surge/issues/113#issuecomment-448598752 ).. but somehow
premake5.lua
does not seem to find them. what am i missing?The text was updated successfully, but these errors were encountered: