Exporting a test library
-
@Reylon Looks good. What happens if you open the project's .jucer file in Projucer and from there open it in Visual Studio (just like when you compile HISE)?
-
@d-healey This is what I got from the visual studio output section
Upgrading project 'Xlibrary test_App'...
Configuration 'Debug|x64': changing Platform Toolset to 'v143' (was 'v141').
Configuration 'Release|x64': changing Platform Toolset to 'v143' (was 'v141').
Retargeting End: 1 completed, 0 failed, 0 skipped -
@d-healey also this: The build tools for Visual Studio 2017 (v141) cannot be found. To build using the Visual Studio 2022 (v143) build tools, either click the Project menu or right-click the solution, and then select "Retarget Solution". Install Visual Studio 2017 (v141) to build using the Visual Studio 2017 (v141) build tools.
-
@d-healey you mention in your video to download visual studio 2022 but some say using 2017 is good because other versions fail?
-
So you have 2022 installed, not 2017?
-
@d-healey yeah just deleted it and now installing 2017. 2022 is in the video tho?
-
@d-healey hmm just gave it a test an same thing..Ahh im trying over a week now
-
@Reylon If you want to use 2022 then you need to perform the export manually through Visual Studio as I showed in the video and edit the properties of the Solution before compiling. If you use 2017 then you don't need to do this extra step, it will happen automatically.
-
@d-healey I don't know it still doesn't work.
I downloaded this one vs_TeamExplorer not sure if its the right one -
I downloaded this one vs_TeamExplorer not sure if its the right one
I don't know what that is
-
@Reylon Team Explorer is only used if you're working in a corporation that shares projects across a team on Azure cloud computers. You'll most likely want to install the free, Community Edition of Visual Studio.
-
@Dan-Korneff seems like there is no such version anymore :(
https://my.visualstudio.com/Downloads?q=visual studio 2017&wt.mc_id=o~msft~vscom~older-downloads -
-
@Dan-Korneff Thank you mate! Should I delete all and start over? Or should it work by installing vs only?
-
@Reylon I would remove TeamExplorer. You won't ever need it.
Dan Korneff - Producer / Mixer / Audio Nerd
-
@Dan-Korneff said in Exporting a test library:
@Reylon I would remove TeamExplorer. You won't ever need it.
Remove Windows while you're at it. You don't need it :p
Delete all versions of VS except 2017 (unless you use them for something else). And make sure you only have one version of the HISE source code on your system
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
@d-healey said in Exporting a test library:
Remove Windows while you're at it. You don't need it :p
I wish that were true. I really enjoying PopOS! on my laptop and main PC.
Unfortunately, I'm stuck on other platforms for audio production :(Dan Korneff - Producer / Mixer / Audio Nerd
-
@Dan-Korneff said in Exporting a test library:
@d-healey said in Exporting a test library:
Unfortunately, I'm stuck on other platforms for audio production :(
Come join us :) - https://linuxmusicians.com/
-
@d-healey I did all that just to get a new error while compiling...
c:\users\reylon\documents\hise-develop\hi_streaming\hi_streaming.h(70): fatal error C1083: Cannot open include file: 'ip
p.h': No such file or directory (compiling source file ....\JuceLibraryCode\include_hi_streaming.cpp) [C:\Users\reylon
Desktop\TestLibrary\Binaries\Builds\VisualStudio2017\TestLibrary_App.vcxproj] -
@Reylon Disable IPP
