Compile errors ((
-
I did nothing concerning copy protection in Hise.
I don't even know with what it's related here... -
This made me think my Hise project was potentially corrupted or something...
I created a new project with a simple interface (one button and knob), and no code.export VST => success! It opens in pro tools via Blue Cat Patchwork!
I'll try to export my code step by step now from the old project to the new one and see...
-
Now with AAX export I got this:
▸ Linking essaiHise2 ❌ ld: library not found for -lAAXLibrary_libcpp ❌ clang: error: linker command failed with exit code 1 (use -v to see invocation) ** BUILD FAILED ** The following build commands failed: Ld /Library/Application\ Support/Avid/Audio/Plug-Ins/essaiHise2.aaxplugin/Contents/MacOS/essaiHise2 normal x86_64 (1 failure) Compiling finished. Cleaning up... logout Saving session... ...copying shared history... ...saving history...truncating history files... ...completed. [Process completed] -
@ustk were you previously able to compile AAX? or is this your first time?
-
No, it is the first time I can go so far…
-
I found something here:
https://forum.juce.com/t/aax-libc-library/15731/16I'll check that tomorrow to see if I can do something…
-
@ustk For AAX plugins, downloading sdk is not enough. Before exporting AAX plugins; you need to change the runtime library link settings to static in the AAX library and recompile them. The header files should be included automatically. It's the .lib files that you need to create on your own using the AAX SDK Solution file.
-
I tried to compile it with Xcode 10, and obviously, I got a "deprecated architecture i386" error
as I am a noob and don't know if I can fix this, I installed vs2015 community on my PC so I can compile the lib at least there, then copy the lib on my mac. (I don't even know if it can work, please excuse my idiocy
)once imported on the mac, here's what I got:
Good? not good?
gosh it is such a pain to make everything working
A complete tuto would be so cool instead of looking for info everywhere and still have something that doesn't work after a week working full time on it...Can't help pressing F5 in the forum...
-
- Yes lib location is right. But you if you will make32 bit plugins, you have to compile it for 32 bit too seperately (But AFAIK XCode10 doesn't let 32 bit )
- I am using XCode8 without any error. (on Sierra)
- For PC, I suggest VS2017. (Windows 10)
- I think you should compile the lib files seperately in mac and pc.
-
@orange said in Compile errors ((:
on
Thanks, orange!
No, I don't intend to release anything in 32bits anyway.
The main format I want to work with is AAX64So if the file looks good (visually), you think it doesn't work because I compiled it on windows?
I thought the name was different...I will try to install Xcode 8, I'm on High Sierra
Is it not a problem to uninstall Xcode 10 for reinstalling 8?Can't help pressing F5 in the forum...
-
Static library files compiled on windows obviously can‘t be used in macOS. Unix based static libraries have the format libX.a
-
Makes sense... I think, much more to you
When discovering Hise for the first time and when you know just a bit of KSP and/or JS, you think it will be an "easy" task to make a plug, at least not much harder than Kontakt...
But the upstream preparation is so hard for the "non-coders" and with so little information, especially the basics in fact, which should, I assume, be known already... Well, it's not my case obviously
I got to codesign after that... Lucky not to have a rope in the studio... Who said I have XLRs?
-
@ustk Minimum requirment of XCode 8 is mac OS Sierra. So mac OS High Sierra wouldn't cause any problem to install XCode8. Also don't forget to use xcpretty. You can search this forum, there are a couple of topics for that. You must use xcpretty and install some Gems before compiling mac plugins.
-
@ustk said in Compile errors ((:
I got a "deprecated architecture i386" error
as I am a noob and don't know if I can fix thisI just posted how to deal with this recently
-
I made it!
I already had xcpretty so it was ok
Xcode went quite smooth, just the files were located under Libs/Debug instead of Release, so I moved them manually and the export worked
Also, I changed in Xcode the "macOS deployment target" to 10.7, but it worked without anywaySo I guess now I have to go through the authorizations from Avid and PACE if I'm not mistaken...
For now, I need a rest... Thanks guys!
