Hise will not export
-
Ah I think I might know what the problem is. Please paste the contents of the batch file from your project's binaries folder.
I've got to go out shortly but so it might be a while until I respond.
-
@d-healey what do I save it as? XML or archive?
-
@gryphonsegg Open it in a text editor, it's just plain text.
-
@d-healey sorry, because I have had no ability to use it yet I am confused as to what you want me to send you
-
In your project's binaries folder there will be a file called something like build.bat (I can't remember the name on Windows). Open that file in a text editor and paste the contents here.
I'm 99% sure the path it's telling us it can't find is the path to Visual Studio. So I want to see the content of this file to check where it's looking.
-
@d-healey ok sorry for the confusion.
@echo off
set project=hise project 1
set build_path=F:\hise project 1\Binaries
set msbuild="C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\MsBuild.exe"
set vs_args=/p:Configuration="Release" /verbosity:minimal
set PreferredToolArchitecture=x64
set VisualStudioVersion=17.0"F:\HISE\tools\Projucer\Projucer.exe" --resave "%build_path%\AutogeneratedProject.jucer"
echo Compiling 64bit Instrument plugin %project% ...
set Platform=X64
%msbuild% "%build_path%\Builds\VisualStudio2022%project%.sln" %vs_args%pause
-
@gryphonsegg No problem, it's hard to explain this thing via text, especially when you're not familiar with it.
So this is the path it's looking for
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\MsBuild.exe"I'm guessing you have something like a pro version of VS rather than the community version?
-
@d-healey this says its looking for visual studio on C but I have it on E. how is that? can I change where it is looking?
-
@gryphonsegg Aha that solves the mystery. HISE is using the default install path which is C: drive. You'll need to modify your copy of the HISE source code, or create a symlink on the C drive, or move VS to the C drive. Or wait for someone else to offer a solution I haven't though of
-
@gryphonsegg Im using the community version as far as I know. how would I do any of those things to fix it?
-
@gryphonsegg i am uninstalling VS and moving it to the C drive
-
@gryphonsegg I will report back as soon as I know more. I really appreciate you guys helping so much. It means a lot and I really just want to get this going.
-
@gryphonsegg yes that's definitely the issue, I didn't know you could install MSVC anywhere else than the default path.
-
@Christoph-Hart if I did want to change the Hise source code how would I do that?
-
@gryphonsegg You change it and recompile HISE but I would rather add a link file on the C: to your E: installation (and if you want to keep your sanity for the next steps, install MSVC on the system drive, there will be lots of edge case issues like this).
-
@Christoph-Hart i just reinstalled it to the c drive but, now I am getting all kids of ipp.h fatal errors. What now?
-
-
@d-healey what about these errors though?
-
@gryphonsegg I decided to go back and recompile the entire program again and now it fails every time, saying no IPP directory from within VS studio. I have no ide what is happening. I didnt change anything
-
@gryphonsegg You need to reinstall IPP probably so that it can add the integration into VS.
