Exporting a test library

[d.healey]

@Reylon /Binaries/Compiled

[Reylon]

@d-healey So in my main drive there is the Binaries folder.
Inside the builds folder there are some files with my library name but no Compiled folder.

I attached some images to give a better view.

[d.healey]

@Reylon said in Exporting a test library:

Inside the builds folder there are some files with my library name but no Compiled folder.

Why are you looking inside the builds folder? Binaries/Compiled/

And why is it all on your C drive? That's weird, it should be in your project folder.

[Reylon]

@d-healey Im looking in the Builds because the other options are "JuceLibreCode"
"Source" "AutogeneratedProject.Jucer" and "BatchCompile.bat"

I have the Hise-develop folder on my documents folder so I think that's why?
Hise only accepts that particular path.

[d.healey]

@Reylon Where is your project folder?

[Reylon]

@d-healey Desktop
there is a Binaries folder but same thing, no compiled folder

[d.healey]

@Reylon said in Exporting a test library:

@d-healey Desktop
there is a Binaries folder but same thing, no compiled folder

I think you have an organizational issue to deal with first. If your HISE install is in your documents folder and your project folder is on your desktop, there shouldn't be a random Binaries folder floating around in the root of your C drive.

[Reylon]

@d-healey sorry, the folder was in my c drive because I had the path not to my project but to the Hise develop so thats why. I deleted it now.

The problem is that I don't get a compiled folder. When I open the autogenerated jucer project it shows to a compile folder that is simply not there. This is my third installation and same thing.

[d.healey]

@Reylon Which version of Visual Studio are you using?

[Reylon]

@d-healey 2017

[d.healey]

@Reylon Can you make a video showing the export from start to finish?

[Reylon]

@d-healey Sure! :)

2022-08-21 15-32-46.mp4

Google Docs (drive.google.com)

[d.healey]

@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?

[Reylon]

@d-healey im actually on 64 but when exporting 64 it says ”the file path not found”

[d.healey]

@Reylon Have you set the path to the HISE source code in your project preferences?

[Reylon]

@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️

[d.healey]

@Reylon Can you show me the path you are using there?

[Reylon]

@d-healey C:\Users\Reylon\Documents\HISE-develop

[d.healey]

@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)?

[Reylon]

@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