Build failed CompileC

[bfaudio]

@d-healey they do.

[d.healey]

@bfaudio Can you send me one of these projects that won't compile?

[Lindon]

@bfaudio said in Build failed CompileC:

@d-healey Yep. Doesn't make a difference.
Even on a brand new project, new script fx, tried to export to dll just that one new network and same error.
Can export a new project that uses pre-exported dll's, just can't export any existing project started before sequoia or compile any networks of any kind regardless of when they were created.

did you try cleaning out the additional code Folder..

[bfaudio]

@Lindon yep

[bfaudio]

@d-healey I’ll pack one up tomorrow and see if I can get it over to you, what’s the best way?

[d.healey]

@bfaudio DM. Don't include the binaries, samples, or pooled resources folders.

[d.healey]

I'm wondering if there is information we're missing. Can you provide the full build log from xcode? I'm not sure how you get it, so ask Google or ChatGPT.

[Straticah]

@d-healey has this been solved? I have the same issue on my new m4 mac.
HISE 4.1 develop branch (a new test project works without the error)

PS: fixed by getting latest HISE + deleting expression & snex nodes from my scriptnode.

[aralbar]

@bfaudio @d-healey @Straticah @treynterrio

Hello friends, have any solutions to this issue been found?

I am having the same issues exporting my plugin after an update. On Mac M2.

Tried re-installing etc. to no avail.

Would appreciate any help. Many thanks.

[d.healey]

@aralbar said in Build failed CompileC:

Tried re-installing etc. to no avail.

Have you compiled HISE from source?

[aralbar]

@d-healey Indeed, I have tried to using the guide on "Compile the Latest Hise" on documentation.

Build is failing with the below error on Xcode:

Desktop/Hise Path/hi_core/hi_modules/effects/fx/FilterHelpers.h:234:18 No member named 'r' in 'InternalPolyBank'

[d.healey]

@aralbar If you can't compile HISE you won't be able to compile your project, so solving this is the first step

What version of Xcode are you using?
Are you building the develop branch (you should be)?

[aralbar]

@d-healey So, I think the issue had to with the most recent Xcode Update.

I was on 16.3 and reverted back to 16.2, seems to be all good now.

Thanks for the help folks.