Build Carbon Resources build phases are no longer supported

[benzenewings]

I also just tried it on a different older mac running Ventura and Xcode Version 15.2 (15C500b)
Same error with a little extra red text on this one.. attached is screen capture. I luved playing with Hise couple years ago, I really hope to see it working again for me.

[Christoph Hart]

@benzenewings Did you use the latest HISE build from develop? That error message should be fixed by deactivating the plugin copy step.

[benzenewings]

@Christoph-Hart Let me do a run down here of my setup to ensure I am doing it correctly. I download the Hise mac installer binary from Hise.dev website link, install the application, then download the matching 4.1 source code and extract the folder. I launch the app, click new project empty, file-settings and change Hise Path in development tab to the folder i extracted source code Hise 4.1 (which is in my downloads folder, so probably fine permissions, etc), save settings. Then I add one knob component in the editor (just for a blank test), go Export-setupExport Wizard, I get green checks everywhere, then I go Export as Instrument, AUi format, OK, build starts (see screen shot), then i get error: Cycle in dependencies detected, but could not be parsed. Please file a bug report with the build transcript and how to reproduce the cycle if possible.
Build Carbon Resources build phases are no longer supported. Rez source files should be moved to the Copy Bundle Resources build phase. (in target 'volumeknobtest - AU' from project 'volumeknobtest')
** BUILD FAILED **
... As I've said I had it working on my old machine in 2020-2021, made one instrument successfully for myself, used it, (still works on my Logic Pro actually as au), this week I thought of an instrument idea i wanted to try and I have all new computers now since 2021, so I went to Hise and got started and so far this as far as I got, so maybe I'm doing something wrong. I dont't recall it being complex or hardships setting up last time I got in to it, maybe got lucky, lol, or of corse as we know apple luvs to make everything more difficult as we progress, so thats where I'm at. Any help getting this going again would be great. I have the following macs for testing, mac pillbox pro runs Monterey, mac pro tower (2019) running Sequioa, mac pro 2019 running Ventura, and macbook pro m2 2022 running ventura (but i have learned to avoid dev on arm units -but willing to try), and I have an HP laptop runing Ubuntu 24 (that I'm on another thread here) trying to see if I can get it running on there. So far, I have not successfully been able to build an AU with Hise on any machine, so maybe there is something i am totally missing or going about the wrong way.

[benzenewings]

quick update: i did a build of Hise instead of binary package installer.. followed all instructions, went fine, opened it up, put one knob fader in a project, saved, exported a Standalone plugin just fine. Tried AU and VST, same error. .
"error: Cycle in dependencies detected, but could not be parsed. Please file a bug report with the build transcript and how to reproduce the cycle if possible."

[benzenewings]

@Christoph-Hart sorry, how do i go about deactivating the Plugin Copy step? I do not see that in Settings. -- Yes, using the latest Hise -build from develop.

[d.healey]

@benzenewings

[benzenewings]

@d-healey .. I don't seem to have that.

[d.healey]

@benzenewings It's in your project's juicer file, not in HISE's

[benzenewings]

@d-healey Ya, same experience here for me, after changing that. I'll talk through what I do to modify that setting. So there is no Projucer file for the project until I try a build and let it fail, so I export an AU until it fails, then go to that folder and change the Projcer setting for Enable Plugin Copy - Disabled, save, then Go to Hise and export again, and same error happens. I'd assume this is wrong way going about it.
I also tried just Compile Project, which gives xpretty errors, so there may be some issues with that install even tho i ran the command for installing it and all went fine.. here is screen of Compile error.

Perform sanity checks
Create C++ autogenerated files
Create binary data files
Exporting the pooled resources
Export audio files
Export image files
Export samplemap files
Export MIDI files
DONE
Create embedded data files
Launch system compiler...
Re-saving file: /Users/nathan/Documents/HISE Projects/TestFader2/Binaries/AutogeneratedProject.jucer
Finished saving: Visual Studio 2017
Finished saving: Xcode (macOS)
Finished saving: Xcode (iOS)
Finished saving: Linux Makefile
Compiling Instrument plugin TestFader2 ...
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
/Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/lib/xcpretty/parser.rb:434:in ===': invalid byte sequence in US-ASCII (ArgumentError) from /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/lib/xcpretty/parser.rb:434:in update_test_state'
from /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/lib/xcpretty/parser.rb:307:in parse' from /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/lib/xcpretty/formatters/formatter.rb:88:in pretty_format'
from /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/lib/xcpretty/printer.rb:19:in pretty_print' from /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/bin/xcpretty:84:in block in <top (required)>'
from /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/bin/xcpretty:83:in each_line' from /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/bin/xcpretty:83:in <top (required)>'
from /usr/local/bin/xcpretty:23:in load' from /usr/local/bin/xcpretty:23:in

'
** BUILD FAILED **

[Christoph Hart]

@benzenewings Try the latest commits from this weekend, I just updated macOS to reproduce this and ran into the same error (seems like they've updated the Ruby runtime which broke xcpretty).

I've completely replaced xcpretty with another console formatting app (which is a binary that is now directly included in the HISE source code and not dependent on Ruby) so you shouldn't run into this issue. Still not sure if that was your original problem, but I can now export through the compile project window on the latest macOS stuff without issues.