Build failure when exporting plugin on OSX, xcbeautify: Bad CPU type in executable

[thrice801]

After finally getting the HISE release version to build, I can't seem to be able to export either VST or AU plugins. Trying to export a midifx plugin. - The weird thing, is I actually only had x86_64 selected in valid architechtures in the projucer file, and still got this after building the hise release and trying to export. So I'm not sure what's going on, anyone have any idea? Did a forum search and found some similar stuff but nothing that looked like this specifically. - But also there isn't any arm references or anything in the error, just x86_64

Re-saving file: /Users/jasonayre/code/hise_projects/alientoric_midi_player/Binaries/AutogeneratedProject.jucer
Finished saving: Visual Studio 2017
Finished saving: Xcode (macOS)
Finished saving: Xcode (iOS)
Finished saving: Linux Makefile
Compiling MIDI FX plugin alientoric_midi_player ...
/Users/jasonayre/code/hise_projects/alientoric_midi_player/Binaries/batchCompileOSX: line 7: /Users/jasonayre/code/hise_develop/tools/Projucer/xcbeautify: Bad CPU type in executable
** BUILD FAILED **


The following build commands failed:
	CompileC /Users/jasonayre/code/hise_projects/alientoric_midi_player/Binaries/Builds/MacOSX/build/alientoric_midi_player.build/Release/alientoric_midi_player\ -\ Shared\ Code.build/Objects-normal/x86_64/include_hi_streaming.o /Users/jasonayre/code/hise_projects/alientoric_midi_player/Binaries/JuceLibraryCode/include_hi_streaming.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'alientoric_midi_player - Shared Code' from project 'alientoric_midi_player')
(1 failure)```

[d.healey]

@thrice801 said in Build failure when exporting plugin on OSX, xcbeautify: Bad CPU type in executable:

I actually only had x86_64 selected in valid architechtures in the projucer file

The project's juicer file or HISE's?

[thrice801]

@d-healey HISE's, the HISE Standalone projucer, before compiling HISE. I've tried it with and without arm selected as valid architectures and recompiling

[d.healey]

@thrice801 What happens if you change it in your project's juicer file? When you click export from HISE it creates a JUCE project, you will find a juicer file in your project's binaries folder. Open that in Projucer, edit it, and then open it in Xcode, just like when compiling HISE.

[thrice801]

@thrice801 yep that's exactly what I just was figuring out. then after compiling manually in xcode thought it still wasn't working but turns out it was, just issues with abelton and midi fx plugins I think so it wouldn't load. Got a different snippet to compile; I think I had to disable IPP also to get it to compile. -- actually export seems to be working from within hise now after ipp thing (I believe), it still throws the error on export but looks like the xcbeautify step doesn't need to succeed in order to compile. Thanks for the help!

[Lindon]

@thrice801 IPP isnt required on MacOS

[Dan Korneff]

I'm seeing this in the latest version of HISE as well on multiple MacOS:

batchCompileOSX: line 7: /HISE/tools/Projucer/xcbeautify: Bad CPU type in executable

macOS 15.4.1 + Xcode 16.3
macOS 13.7.5 + Xcode 15.4

building from the autogenerated projucer file works as expected.