Exporting a test library

[Reylon]

@Matt_SF Im using the latest one. Followed step by step David's video on how to install Hise.
@d-healey I tried as standalone but anyways checked the folders and there seems to be nothing.

Thank you guys for your replys :)

[d.healey]

@Reylon Open your project's .jucer file in Projucer. Go to the releases section for your exporter, and it will show you the binary location.

[Reylon]

@d-healey Mine says HISE, I also checked the Binary Location
../../../../tools/SDK/ASIOSDK2.3/common but couldn't find my exported test library.

[d.healey]

@Reylon said in Exporting a test library:

@d-healey Mine says HISE,

Did you open your project's .jucer file? This is the file that is in your project's binaries folder.

[Reylon]

@d-healey Did just now and it says the location is Compiled/? Any ideas where to look?

[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! :)

https://drive.google.com/file/d/1JqD7NtrAs1De-OGF72tSaxyxR0baB4xx/view?usp=sharing

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