Unable to Compile AU for Mac



  • Unable to compile Mac AU,component file .
    Screenshot 2021-02-22 at 2.44.27 PM.png



  • Screenshot 2021-02-22 at 8.04.28 PM.png



  • @Tania-Ghosh It's not codesigned. I think you need to have an Apple developer ID. It happened to me in December.



  • @nesta99 I created apple Developer ID.. but how can I codesigned? What step did you follow? Can you guide me? i need to compile AU plugins.



  • Please somebody tell me how to compile AU plugins. I have no Idea on Au plugins development and all the requirements to build it.



  • @Tania-Ghosh Have you purchased the 99$ Developer plan ? If yes then I don’t know how to codesign trhough Hise because I got the David Healey Hise exporter by subscribing to his patreon. So please you better ask him and be a patreon!



  • @nesta99 OK. Thanks



  • You don't need to code sign anything to compile a plugin



  • @d-healey Omd!! true. It was just a warning, sorry. my bad...



  • @d-healey Then sir , what step do I need to follow to compile AU plugins?



  • According to google that error code is because Xcode is trying to copy a file that doesn't exist.

    Reinstalling Xcode fixed it for some people, I'm not on mac though so ¯_(ツ)_/¯



  • @iamlamprey Windows is way easier than Mac. First I had spent 2 days to build HISE. When HISE is ready I am unable to compile AU plugins. Not even from JUCE (with out HISE only writing simple code in JUCE). @nesta99 What the * u** developer plan? VST3 /VST is free to compile where as AU for MAC is $99? Then what is the meaning of making and spending hours to develop Audio plugins for Mac AU?
    At the end Team R2R or AudioUtopia will pirate it.



  • It doesn't cost anything to compile AU or VST, there is some problem with your build setup. Try reinstalling Xcode.



  • @Tania-Ghosh Make sure you have xcode installed and its command line is important. if you are using ipp check that everything is correctly installed. to export directly from hise you don't need to sign. remember to save your ID certificates and applications and especially their keys in the keychain glass. I made the mistake of creating 5 certificates of each I am blocked, I lost my keys I can no longer sign or notarize my work. and the apple support service is a real shit ^^



  • @d-healey Reinstalled Xcode 10. Tried 11 No luck. VST3 is being compiled but Logic Pro doesn't show it. Ableton Live Lite or Bitwig 8track shows it......... But AU......? Every time it ends up with error. Which I can't figure out. Tried google/youtube but it's Out of Sundar Pichai's knowledge ...☹

    @yall now coming back to your guide line... As you all know I am new in MAC. I am telling briefly what have I done for AU...
    My steps are------

    1. Installed Xcode
      2)Xcode preference >Accounts I have put Apple ID and created Team (Personal)
      3)Installed IPP that helped by @orange and @Rudra-Ghosh
      4)Creating a project in HISE exporting AU-VST
      5)Opening JUCE and the Autogenerated.jucer
      6)Save and Open in IDE
    2. Build for profile or Debug/Run (Tried everything)
    3. **Boom......**error listed on top of the Images

    Now guide me what am I doing wrong? For keychain stuff i don't know how to do it... Apple support is really shit.. i agree.



  • @Tania-Ghosh

    Reinstalled Xcode 10. Tried 11 No luck.

    Has to be Xcode 10.x.

    Logic Pro doesn't show it.

    This is a different issue. We'll tackle that later once we fix AU compiling.

    2)Xcode preference >Accounts I have put Apple ID and created Team (Personal)
    ...
    Now guide me what am I doing wrong? For keychain stuff i don't know how to do it... Apple support is really shit.. i agree.

    This has nothing to do with compiling plugins.

    Can you send me the project and I'll try to compile it and see if I get the error?



  • @d-healey Sure.. here it is .Zantophil2.zip



  • Thanks. I just want to confirm, when you export, you are exporting as an FX plugin, not an instrument plugin, correct?

    Also, why do you open the project in xcode? HISE should automatically start the export via the commandline, you shouldn't need to open Projucer or xcode. Does the command line terminal window not open for you when you export from HISE?



  • @d-healey

    Thanks. I just want to confirm, when you export, you are exporting as an FX plugin, not an instrument plugin, correct?

    Yes

    Also, why do you open the project in xcode? HISE should automatically start the export via the commandline, you shouldn't need to open Projucer or xcode. Does the command line terminal window not open for you when you export from HISE?

    Exactly...commandline window opens but stops with some errors. I will post you the snapshot tomorrow. So I had to open .jucer file and generating xcode project from there.



  • @Tania-Ghosh

    Exactly...commandline window opens but stops with some errors. I will post you the snapshot tomorrow. So I had to open .jucer file and generating xcode project from there.

    Ok, I'll wait for your image.


Log in to reply
 

13
Online

1.1k
Users

3.6k
Topics

30.9k
Posts