Skip to content
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-VST3: (macOS) linker command failed with exit code 1 (use -v to see invocation) clang #80

Closed
esaruoho opened this issue Dec 14, 2018 · 15 comments

Comments

@esaruoho
Copy link
Collaborator

esaruoho commented Dec 14, 2018

After proceeding from making a tiny fix ( #79 ) - the next error while trying to get surge-vst3 built with macOS is:

linker command failed with exit code 1 (use -v to see invocation) clang

Now, I can't even click it so that xcode would suggest a fix. any ideas?

@baconpaul
Copy link
Collaborator

Linker errors usually mean you have an undefined symbol. Xcode makes it annoying to find them as far as I can see.

I simulated one in my local area just now

screen shot 2018-12-14 at 6 18 14 pm

the trick I find to find the symbol is to go to the set of logs and find your failing build

screen shot 2018-12-14 at 6 18 57 pm

then when you click on the little expanding hamburger glyph thing you see the symbols you are missing

screen shot 2018-12-14 at 6 19 57 pm

Usually this occurs because you are including a .h file for a subset of a library but not building or linking the associated .cpp. Especially if you see something like Steinberg::VST::MyBlimBlom it probably means your include path allows you to #include "myblimblom" but you're premake5.lua doesn't include myblimblom.cpp

Hope this helps! Good luck.

@esaruoho esaruoho changed the title macOS:VST2: linker command failed with exit code 1 (use -v to see invocation) clang macOS:VST3: linker command failed with exit code 1 (use -v to see invocation) clang Dec 15, 2018
@esaruoho
Copy link
Collaborator Author

Thanks for the assist! the error i'm seeing is..
surge_xcworkspace

@esaruoho esaruoho changed the title macOS:VST3: linker command failed with exit code 1 (use -v to see invocation) clang Surge-VST3: (macOS) linker command failed with exit code 1 (use -v to see invocation) clang Dec 15, 2018
@baconpaul
Copy link
Collaborator

baconpaul commented Dec 15, 2018 via email

@asimilon
Copy link
Contributor

I also see these link errors. Not entirely sure from looking at git blame history, so wondering who wrote in the README

You can also build a VST which links but honestly we aren't sure if it works. Help from someone who uses VST would be appreciated here!

I'm wondering how this is possible that it built and linked?

@baconpaul
Copy link
Collaborator

I had written that when it linked! I then got the au working and stopped looking at vst. And apparently now it is back to not linking :)

If it is the surgeditor symbol errors I fixed that by ifdefing out the class which wasn’t used. Later tonight I will take a peek and see what’s in head.

These sorts of problems will pop up more and more the longer our merge backlog is! I really hope we can get master back close to the codebase which runs the au soon.

@baconpaul
Copy link
Collaborator

Right this diff

https://github.com/kzantow/surge/commit/f20830627f7b0e6546b771ab2f087a537c9673ea

Which made it work. That if 0 went to if !target audio unit, though, which is why au works and vst no longer does

So to make vst work also exclude that class if it is truly not needed or finish those methods. With it excluded I could compile and link but not run a vst

@baconpaul
Copy link
Collaborator

Oh and that is my diff. Just I’m looking st it on kzantows big merge branch which is why his name shows up.

@asimilon
Copy link
Contributor

Slightly unrelated, but on the VST2 project, with some excluding of AU specific files from premake5.lua I've got it successfully building and linking, however, it's not being recognised. Perhaps it's going to be similar issue for the VST3, will investigate.

@esaruoho
Copy link
Collaborator Author

@asimilon query -- what is not recognizing Surge.vst? Have you checked https://github.com/tracktion/pluginval to see what it says on the VST?

@baconpaul
Copy link
Collaborator

great! Happy to answer any questions about the au or look at any diffs if that helps

@baconpaul
Copy link
Collaborator

OK I figured out the premake thing that was breaking vat and how to change it so that AU still worked and have a diff coming which will allow VST3 and AU to link. Stay tuned. I'll push it to the big PR.

@baconpaul
Copy link
Collaborator

kurasu@ce3b57d

OK there's the diff. @asimilon if you want to use this you need to fetch and merge @kzantow branch "cumulative-fixes-and-zoomable-ui"

I have not included your build.osx changes in that. Honestly it was too tricky to pull the commit from a fourth remote!

But with those changes, VST3 and AU both link if you start from a clean area and rerun premake

@baconpaul
Copy link
Collaborator

Oh and by being in cumulative-fixes-and-zoomable-ui it participates in the big PR which gets the AU running also.

I don't want to add a million things to that PR. If you actually can get the VST validating from there maybe a separate one makes sense but to do that one you will probably want to start from the cumulative-fixes branch.

@baconpaul
Copy link
Collaborator

Can we close this issue @esaruoho - It's now resolved after the #92 merge.

@esaruoho
Copy link
Collaborator Author

Closing ticket :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants