Exporting a test library
-
-
@Reylon The quality is too low so I couldn't see exactly what was happening but I can tell you that your project didn't compile so that's why you are not seeing any output. It takes several minutes for a project to compile.
It looked like you were exporting a 32bit version, are you using a 32bit system?
-
@d-healey im actually on 64 but when exporting 64 it says ”the file path not found”
-
@Reylon Have you set the path to the HISE source code in your project preferences?
-
@d-healey Yes the one folder you left in downloads in your tutorial. Hise develope folder.
Btw thank you soo much for all the great tutorials
️ -
@Reylon Can you show me the path you are using there?
-
@d-healey C:\Users\Reylon\Documents\HISE-develop
-
@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 -
