Build Failed No Global Header File Was Included

[Dan Korneff]

@virtuscapeaudio said in Build Failed No Global Header File Was Included:

com.apple.compilers.llvm.clang.1_0.compiler

I think the clang error points to an unsupported architecture.

[DanH]

@Dan-Korneff I recently had to change the supported architecture in the project autogenerated projucer file as well as the standalone hise one - then had to build in Xcode / VS rather than export directly from hise.

[virtuscapeaudio]

@DanH Really having trouble with this...I exported another test project just fine so it seems architecture settings are ok. I deleted the entire build folder and tried again but same issue.

Interesting thing is when I open in Xcode, I no londer see VST and AU targets, only Standalone.

any ideas?

[d.healey]

@virtuscapeaudio What Xcode version are you using?

[virtuscapeaudio]

@d-healey XCode 13.1 on MacOS 12.2.1

[d.healey]

@virtuscapeaudio Try updating it - or have you compiled successfully with that version before?

[virtuscapeaudio]

@d-healey All was working well with Xcode until I updated to latest develop branch of HISE so I wonder if something doesn't match with the actual project or something. Tested other projects and it works fine.

[DanH]

@virtuscapeaudio are you checking the autogenerated projucer file after hise fails to build? I found that I had to also change the architecture settings in there as well before then using Xcode (not hise) to build

[virtuscapeaudio]

@DanH Ive tried to change to x86_64 then build, and arm64 then build, and still no global header is included automatically. Also I don't see the VST and AU targets in Xcode, only Standalone

[DanH]

@virtuscapeaudio are you using faust? Which architecture is your system?

[virtuscapeaudio]

@DanH I'm not using faust...I'm on M1. I just exported a different project successfully from within HISE without any modifications. The build that fails doesn't get past the Global Header issue. What exactly is the Global Header? Perhaps there's something within the Project Settings of this particular .xml that I'm missing? How trivial is it to rebuild this project? I would hate to go down that road if its something as simple as fixing a setting the project_settings.xml or something (I'm really guessing, here)

[DanH]

@virtuscapeaudio it's really hard to tell without seeing what going on in your machine. Missing headers I think normally means it can't find files, which is often caused because it's looking in the wrong place.

Maybe Xcode 14.3 is worth a go if your OS supports that - I think it does.

What's the error you're getting now? Before it mentioned x86_64 which would mean a setting is wrong in the autoGen project I imagine...

You also probably don't see the au/vst3 options in Xcode because you attempted a standalone build and that's what it's created the autoGen project for.

You're definitely looking here, right?

[DanH]

@DanH so this is exactly what I mean in the image below, my computer is now ticking the x86_64 box by default for some reason...

[virtuscapeaudio]

@DanH

Yes def the AutogeneratedPoroject.jucer

Yes that happened to me as well so I made sure only arm64 is selected and I chose Save and open in IDE, Build and get the same error.

[DanH]

@virtuscapeaudio so its nodes/factory.cpp that’s throwing the error? Still with x86_64?

[virtuscapeaudio]

@virtuscapeaudio Is it an Xcode issue if other projects work fine when exporting other projects?

@d-healey This project is built on a Rhapsody template and perhaps updating to the latest develop branch caused something to go awry? idk

[DanH]

@virtuscapeaudio is there a specific reason you updated the develop branch? If it was working fine before then perhaps its better to go back. I try to not update if I don't need to because I find you run into problems like this. Especially when you are close to a release...

Feel free to send me the project if you like, I can have a look, although I've never used a Rhapsody project before...

[virtuscapeaudio]

@DanH Good advice! Yup I'm trying to update Rhodecase88 which is my debut release haha. tbh I just assumed the latest was best..still a noob. I may just try to go back and find the branch I was using before. I will PM you the project to see if maybe you can export it? REALLY appreciate it.

[DanH]

@virtuscapeaudio If there's a branch I released a product with I tend to zip it up before moving on, so I know I have it in case I need to go back.

[virtuscapeaudio]

@DanH SMART!!! thank you!