Now This: fatal error: sorry, this include generates a translation unit too large for Clang to process.

[CyberGen]

Hi,

Getting this error during export:

fatal error: sorry, this include generates a translation unit too large for Clang to process.

Anyone knows what this means and how to solve it?

Sorry, exporting errors just sound like a foreign language to me.

[Lindon]

@CyberGen said in Now This: fatal error: sorry, this include generates a translation unit too large for Clang to process.:

Hi,

Getting this error during export:

fatal error: sorry, this include generates a translation unit too large for Clang to process.

Anyone knows what this means and how to solve it?

Sorry, exporting errors just sound like a foreign language to me.

what platform what compiler version what version of HISE

[d.healey]

@Lindon Clang is Mac, also he mentioned aif in his other thread which is also Mac, so I'm guessing he's on Mac.

[CyberGen]

@d-healey @Lindon Mac. I'm using the developer branch. Compiling directly out of HISE. But with Xcode (14.2) I get the same error.

[CyberGen]

@Lindon @d-healey Sorry posted this on the wrong thread a moment ago.

This is the screenshot of the terminal when it fails.

Any guesses as to what could be hapening?

[d.healey]

Are you exporting a plugin or standalone? Have you tried cleaning the build folder? Are you able to build HISE?

[CyberGen]

@d-healey I'm trying for a standalone first but I have tried plugin just to see if it works. same result. Yes I've cleaned the build directory and yes I can build HISE just fine. Built HISE as recently as yesterday.

What is it referring to with "translation unit"?

last part looks like this:

[CyberGen]

@d-healey also, I just exported one of my older projects without issue, to make sure is related to this particular project.

[d.healey]

@CyberGen said in Now This: fatal error: sorry, this include generates a translation unit too large for Clang to process.:

What is it referring to with "translation unit"?

No idea but usually when something is too large it means you've ran out of RAM. Does this project contain a lot of embedded images or audio files (not samples)?

[CyberGen]

@d-healey so no, the project is wavetable based and it's performing at basically 0% RAM and under 10%CPU. All knobs and graphics are created with vector graphics and shaders with the exception of one background image, which is large but nothing to cry about, I don't think. 21MB

[d.healey]

@CyberGen said in Now This: fatal error: sorry, this include generates a translation unit too large for Clang to process.:

21MB

Is that the raw bitmap size?
How big are the wavetables? Are they embedded?

[CyberGen]

@d-healey so, I deleted a bunch of old unused files that were still in the audio files project. This made the build succeed!... the only problem is the that the app does not run. But hey, one fight at a time. Thank you for helping me troubleshoot this.

It does bring up one question. Is there a size limit to audio files? or the size of the audio file folder?

thanks again.

[d.healey]

@CyberGen
https://docs.hise.audio/working-with-hise/project-management/projects-folders/audio-files.html
https://docs.hise.audio/working-with-hise/settings/project.html#embed-audio-files