Build failed CompileC

[treynterrio]

Hi there, I've asked a similar question already and the fix was to clean the build directory but this time this doesn't work. I've reinstalled HISE on my Intel Macbook and I tried to export a plugins but every time it says ** BUILD FAILED **

 Build Carbon Resources build phases are no longer supported.  Rez source files should be moved to the Copy Bundle Resources build phase. (in target 'Plugintest - AU' from project 'Plugintest')

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

Could anyone tell me how I could fix this? Thanks

[treynterrio]

@Christoph-Hart could you help me with this?

[Noahdeetz]

@treynterrio

Hey. Just to double check have you compiled HISE on your computer or did you just download the binary? I assumed you did since you have already gotten the plugin to work on your machine but just in case...
https://www.youtube.com/watch?v=zeLeCSNh0XM

If so, what version of HISE are you using?

[treynterrio]

@Noahdeetz I've build HISE 4.1 from the source code.

[treynterrio]

@treynterrio I have already 3 macbooks with HISE so I don't think I did an mistake while I build it. This problem happens when I try to export a plugin I already made

[d.healey]

@treynterrio Is there any more output about why the build failed?

[treynterrio]

@d-healey no, that's all about the error that is in the terminal. I can check again at which step it stops exactly, but it stops almost immediately.

[treynterrio]

@d-healey

that's what comes before the Build Carbon resources and ** BUILD FAILED**

Compiling FX plugin Plugintest ...
    Building targets in manual order is deprecated - check "Parallelize build for command-line builds" in the project editor, or set DISABLE_MANUAL_TARGET_ORDER_BUILD_WARNING in any of the targets in the current build to suppress this warning
▸ Compiling include_juce_gui_extra.mm
▸ Compiling include_melatonin_blur.cpp
▸ Compiling include_juce_product_unlocking.mm
▸ Compiling include_juce_osc.cpp
▸ Compiling include_juce_opengl.mm
▸ Compiling include_juce_gui_basics.mm
▸ Compiling include_juce_graphics.mm
▸ Compiling include_juce_events.mm
▸ Compiling include_juce_dsp.mm
▸ Compiling include_juce_data_structures.mm
▸ Compiling include_juce_cryptography.mm
▸ Compiling include_juce_core.mm
▸ Compiling include_juce_audio_utils.mm
▸ Compiling include_juce_audio_processors.mm
▸ Compiling include_juce_audio_plugin_client_utils.cpp
▸ Compiling include_juce_audio_plugin_client_VST_utils.mm
▸ Compiling include_juce_audio_formats.mm
▸ Compiling include_juce_audio_devices.mm
▸ Compiling include_juce_audio_basics.mm
▸ Compiling include_hi_zstd_3.mm
▸ Compiling include_hi_zstd_2.mm
▸ Compiling include_hi_zstd_1.mm
▸ Compiling include_hi_tools_02.cpp
▸ Compiling include_hi_tools_01.cpp
▸ Compiling include_hi_streaming.cpp
▸ Compiling include_hi_snex_62.cpp
▸ Compiling include_hi_snex_61.c

[d.healey]

@treynterrio Are you building vst3?

[Morphoice]

This post is deleted!

[Morphoice]

@treynterrio this sounds very much like the problems I had a few weeks ago with a develop branch build of HISE. Christoph changed a few things and it worked smoothly with the new OSX versions.... how current is your build?

[treynterrio]

@d-healey AU and VST3 both doesn't work building VST3 doesn't say this Build Carbon Recources but this CompileC error

[treynterrio]

@Morphoice the newest 4.1.0

[d.healey]

@treynterrio said in Build failed CompileC:

the newest 4.1.0

Which commit?

[treynterrio]

@d-healey said in Build failed CompileC:

the newest 4.1.0
Which commit?

the newest I've downloaded it yesterday

[d.healey]

@treynterrio Are you able to compile your project as a standalone?

[treynterrio]

@d-healey yes I'm always use it as standalone

[d.healey]

@treynterrio No I mean export your project as standalone rather than as a plugin.

[treynterrio]

@d-healey that doesn't work either

[d.healey]

@treynterrio Have you cleaned the build folder? Are you able to compile a new empty test project?