How far is HISE 3.0?
-
@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! :)
-
@harris-rosendahl What VS2017 version are you running (Help -> Show Info)?
@Dominik-Mayer had the same problems and updating to VS2017 15.9.3 solved it (no idea why though).
-
@Christoph-Hart said in How far is HISE 3.0?:
@harris-rosendahl What VS2017 version are you running (Help -> Show Info)?
Microsoft Visual Studio Community 2017 Version 15.6.4 VisualStudio.15.Release/15.6.4+27428.2015 Microsoft .NET Framework Version 4.8.03752 Installed Version: Community Visual C++ 2017 00369-60000-00001-AA068 Microsoft Visual C++ 2017 ASP.NET and Web Tools 2017 15.0.40314.0 ASP.NET and Web Tools 2017 C# Tools 2.7.0-beta3-62715-05. Commit Hash: db02128e6e3c4bdfc93e6ec425ac9162b4d4fe80 C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used. Intel® Parallel Studio XE 2018 Update 1 Composer Edition for C++ Windows* Package ID: w_comp_lib_2018.1.166 Intel® Parallel Studio XE 2018 Update 1 Composer Edition for C++ Windows* Integration for Microsoft* Visual Studio* 2017, Version 18.0.27.15, Copyright © 2002-2017 Intel Corporation. All rights reserved. * Other names and brands may be claimed as the property of others. JavaScript Language Service 2.0 JavaScript Language Service Microsoft JVM Debugger 1.0 Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines Microsoft MI-Based Debugger 1.0 Provides support for connecting Visual Studio to MI compatible debuggers Microsoft Visual C++ Wizards 1.0 Microsoft Visual C++ Wizards Microsoft Visual Studio VC Package 1.0 Microsoft Visual Studio VC Package NuGet Package Manager 4.6.0 NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/. ProjectServicesPackage Extension 1.0 ProjectServicesPackage Visual Studio Extension Detailed Info Test Adapter for Boost.Test 1.0 Enables Visual Studio's testing tools with unit tests written for Boost.Test. The use terms and Third Party Notices are available in the extension installation directory. Test Adapter for Google Test 1.0 Enables Visual Studio's testing tools with unit tests written for Google Test. The use terms and Third Party Notices are available in the extension installation directory. Visual Basic Tools 2.7.0-beta3-62715-05. Commit Hash: db02128e6e3c4bdfc93e6ec425ac9162b4d4fe80 Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used. Visual Studio Code Debug Adapter Host Package 1.0 Interop layer for hosting Visual Studio Code debug adapters in Visual Studio Visual Studio Tools for CMake 1.0 Visual Studio Tools for CMake
-
Try updating to > 15.9 (just run the Visual Studio installer, it will automatically install the latest update).
-
@Christoph-Hart said in How far is HISE 3.0?:
Try updating to > 15.9 (just run the Visual Studio installer, it will automatically install the latest update).
That was the cause. I've updated VS to version 15.9, and Compiled Successfully!
Thank you!