i386 deprecated!?!?!

[Lindon]

@Lindon .oh hang on....

...yep. I forgot to set it to 64-bit in the debug section... ignore me, back on your heads...

[Ohnias]

@ustk does this work for Xcode 9 too?

[ustk]

@Ohnias I have no idea, it worked with v10 so I don't touch anything

[Ohnias]

Hey Guys i´m getting a Error Message very close to this one...

The following build commands failed:
Ld build/PianoSAMmini.build/Release/PianoSAMmini\ -\ VST.build/Objects-normal/i386/PianoSAMmini normal i386
(1 failure)

Does anyone know how to fix this?

Ps. If i export without IPP i dont get this Message and the export works mostly fine..

Intel IPP is already installed... @d-healey told me i may have to setup the "setting file paths so projucer knows where IPP is installed."
Does anyone knows how to set these up on a Mac? ... (I´m on MacOs(highSierra) )

Greets Toby

[ustk]

Sorry about what I said, it's not xcode 10 but 8 that I am using…

[ustk]

I don't konw what happened (except that I have a recent version of Hise), but I can't export VSTi anymore... not even with the previous version I was using, and without changing anything in my config…
Will work on that today I think

[Dan Korneff]

@ustk probably your preferences within HISE. Make sure your hise directly is properly selected

[Lindon]

OK so I can get HISE to compile - but it keeps building the debug version for some reason.... however when I try and compile my plugin I get fatal errots

"the i386 architecture is depreciated. You should update your ARCHS build setting to remove the i386 architecture. (in target 'Vintage Organ - VST')"

-- Im a complete Mac novice so I have no idea where I would do that... anyone?

[Dan Korneff]

@Lindon I'll send some pics in a few

[Lindon]

@dustbro great thanks a lot.

[Lindon]

bump, anybody?

[Christoph Hart]

Open the Autogenerated projucer file in the build directory and change the architecture setting to 64bit only.

[Lindon]

@Christoph-Hart yes already done that - otherwise HISE wont compile...its erroring on VST export...

[Christoph Hart]

Yes and you need to do the same thing with the projects Projucer file.

HISE creates a temporary projucer file which is then used to create the actual IDE projects for each platform. If you click export, everything is handled through a batch script behind the scenes.

In your case, you must click export, then wait until the compilation starts, abort the compilation, open the projucer file called "AutogeneratedProject.jucer" in your projects' Binary subfolder, then proceed like you would compile HISE.

If you don't want the Debug version, choose "Build for profiling", that is XCode speak for the release version.

[Lindon]

@Christoph-Hart OK thanks I will give all that a go...

[Lindon]

@Christoph-Hart OK this is SOOO frustrating...

I open HISE on the Mac,
load my project,
start the compile,
abort the compile,
go open the AutogeneratedProject.jucer file,
set to 64-bit Intel,
save and open xcode,
Start the compile
Everything seems to work fine.

Now where in heavens name is the compiled vst plugin?

projucer tells me its in $HOME/Library/Audio/Plug-Ins/VST

but that is empty.

Ok some random attempts by me:

I turned OFF Support32 Bit Mac OS
I ran the Export command again for VST
it seemed to work all the way thru...

There is still nothing in the VST folder, but now the
{PROJECT}/Binaries/Builds/MacOSX/build/Release folder has these files in it:

ChromaticPanFlute.vst (an alias)
libChromaticPanFlute.a

are these it?

Why anyone would say the Mac is intuitive I have no idea....

[ustk]

@Lindon I can't help much I'm afraid, but you said you got an alias. Where is it pointing to?

[hisefilo]

@Lindon try right click over the alias and.. Show original. Hise compiler places my plugins into my user vst folder

[hisefilo]

@Christoph-Hart maybe a more intuitive way is to set hise to place compiled plugins into binaries/compiled on Mac? Like it does on win

[Christoph Hart]

Yes, the default location is the user's plugin directory:

~/Libraries/Application Support/Audio/Plug-Ins/VST

There is no way on Mac to point to a VST directory (on Windows it can be any path), so on macOS you're pretty much limited to this path and it's almost identical twin without write permissions /Libraries/Application Support/Audio/Plug-Ins/VST. That's why there is a plugin-copy step.