How far is HISE 3.0?
-
Last stable version that should be used in production => Github -> scriptnode branch
bleeding edge with fancy new stuff: Github -> scriptnode codegen rewrite branchEverything else is completely outdated. And yes, I already feel ashamed about the branch policy, so don't rub it in...
-
@Christoph-Hart said in How far is HISE 3.0?:
Last stable version that should be used in production => Github -> scriptnode branch
bleeding edge with fancy new stuff: Github -> scriptnode codegen rewrite branchEverything else is completely outdated. And yes, I already feel ashamed about the branch policy, so don't rub it in...
Ok ;-)
-
@Christoph-Hart have you looked at the Error Log (Windows) that I post above?
-
I'm hitting some errors I've not seen before when compiling the codegen branch
/JUCE/modules/juce_graphics/colour/juce_PixelFormats.h:119:77: error: cannot bind packed field ‘((juce::PixelARGB*)this)->juce::PixelARGB::<anonymous>.juce::PixelARGB::<unnamed union>::comps[0]’ to ‘juce::uint8&’ {aka ‘unsigned char&’} 119 | forcedinline uint8& getBlue() noexcept { return comps [indexB]; }
-
Well it does compile on OSX, but Xcode looks like a Christmas tree when doing so...
-
@UrsBollhalder said in How far is HISE 3.0?:
Well it does compile on OSX, but Xcode looks like a Christmas tree when doing so...
When does Xcode not do that :beaming_face_with_smiling_eyes:
-
@MikeB Well... I love Christmas!
-
Fails to compile here... I'm probably doing something wrong in the Projucer... I need to have another look at Dave's video on compiling HISE...
So bad not being an IT expert...:( -
@UrsBollhalder Strange, I can't compile here on osx
-
@ustk Well... It compiles with around 385 orange flags, so... it's crashing quite a bit a.o.... I also think @Christoph-Hart pushed a new version yesterday... maybe??! I haven't checked what it was all about...
-
@harris-rosendahl said in How far is HISE 3.0?:
have you looked at the Error Log (Windows) that I post above?
Yes, I remember getting this error too, but not sure what I did to fix it.
Have you resaved the projucer project after switching the branches? The VS solution file needs to be updated to a new C++ standard (these error message point to the wrong C++ standard being used).
-
@ustk Make sure that the C++ version is set to C++17 in the project settings and resave the projucer file so it creates a new XCode project.
Are you using the projucer build that came with HISE? And can you build the snex_workbench?
-
@Christoph-Hart said in How far is HISE 3.0?:
@harris-rosendahl said in How far is HISE 3.0?:
have you looked at the Error Log (Windows) that I post above?
Yes, I remember getting this error too, but not sure what I did to fix it.
Have you resaved the projucer project after switching the branches? The VS solution file needs to be updated to a new C++ standard (these error message point to the wrong C++ standard being used).
Yes I did. I also renamed HISE folder and deleted Projucer file in the Roaming folder to reset the caches. I can see approx. 6000 files loading while C++ loads the solution file, this is the proof of the update.
but still no ucj, both Rellease and Debug versions can't be compiled in Windows 10 :(
-
@Christoph-Hart It fails here too, MacOS 10.15.7, Xcode 10.1
the project already had set to C++17.This is where it fails
-
- Yes, C++ is 17 (as always)
- Yes, Projucer from Hise repo
- Yes, I always launch Xcode from the Projucer so it's automatically resaving
- No, I'm not able to compile the Workbench either...
- I deleted the Builds folder
I use XCode 8 (High Sierra so I could use xcode 10), could it be the source of the problems in my life?
-
Yes, please try Xcode 10 - XCode 8 might not support the C++17 standard
-
@ulrik I just pushed a fix for this line - not sure why my XCode doesn't complain, but it isn't standard compliant C++ anyways.
Check the latest commit
fixed missing array template....
-
@Christoph-Hart Just tried and it still doesn't work, Installing XCode 10 then...
-
@d-healey said in How far is HISE 3.0?:
I'm hitting some errors I've not seen before when compiling the codegen branch
So you know when I tell everyone not to have more than one copy of the HISE source on their system, well I didn't do that. Mystery solved!
-
@Christoph-Hart succés! :)