HISE Logo Forum
    • Categories
    • Register
    • Login

    Compiling HISE 2.1.0 "No such file or directory"

    Scheduled Pinned Locked Moved
    Bug Reports
    3
    17
    751
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • d.healeyD
      d.healey
      last edited by

      Don't use 2.1 it's ancient, use the scriptnode branch.

      Libre Wave - Freedom respecting instruments and effects
      My Patreon - HISE tutorials
      YouTube Channel - Public HISE tutorials

      1 Reply Last reply Reply Quote 0
      • I
        Inveracity
        last edited by

        Thank you for the suggestion!

        I switched to the scriptnode branch, unfortunately I get the same problem

        cl.exe does not like having spaces in its path for some reason, so I tried changing the folder name Visual C++ for Python to Visual_C++_for_Python which causes these failures in Visual Studio 2017 when trying to build HISE

        (about 100+ lines of them)

        Error   C3872   '0x90': this character is not allowed in an identifier  HISE Standalone_App c:\users\username\appdata\local\programs\common\microsoft\visual_c++_for_python\9.0\vc\bin\amd64\cl.exe   1   
Error   C2018   unknown character '0x3' HISE Standalone_App c:\users\username\appdata\local\programs\common\microsoft\visual_c++_for_python\9.0\vc\bin\amd64\cl.exe   1   
Error   C2018   unknown character '0x4' HISE Standalone_App c:\users\username\appdata\local\programs\common\microsoft\visual_c++_for_python\9.0\vc\bin\amd64\cl.exe   1   
Error   C2018   unknown character '0x40'    HISE Standalone_App c:\users\username\appdata\local\programs\common\microsoft\visual_c++_for_python\9.0\vc\bin\amd64\cl.exe   1   
Error   C4430   missing type specifier - int assumed. Note: C++ does not support default-int    HISE Standalone_App c:\users\username\appdata\local\programs\common\microsoft\visual_c++_for_python\9.0\vc\bin\amd64\cl.exe   1   
Error   C2146   syntax error: missing ';' before identifier 'ÿÿ¸'   HISE Standalone_App c:\users\username\appdata\local\programs\common\microsoft\visual_c++_for_python\9.0\vc\bin\amd64\cl.exe   1   
Error   C2018   unknown character '0xe' HISE Standalone_App c:\users\username\appdata\local\programs\common\microsoft\visual_c++_for_python\9.0\vc\bin\amd64\cl.exe   1   
Error   C2018   unknown character '0x1f'    HISE Standalone_App c:\users\username\appdata\local\programs\common\microsoft\visual_c++_for_python\9.0\vc\bin\amd64\cl.exe   1   
Error   C2018   unknown character '0x1' HISE Standalone_App c:\users\username\appdata\local\programs\common\microsoft\visual_c++_for_python\9.0\vc\bin\amd64\cl.exe   1   
Error   C2021   expected exponent value, not '*'    HISE Standalone_App c:\users\username\appdata\local\programs\common\microsoft\visual_c++_for_python\9.0\vc\bin\amd64\cl.exe   2   
Error   C2018   unknown character '0xf' HISE Standalone_App c:\users\username\appdata\local\programs\common\microsoft\visual_c++_for_python\9.0\vc\bin\amd64\cl.exe   2   
Error   C2021   expected exponent value, not '='    HISE Standalone_App c:\users\username\appdata\local\programs\common\microsoft\visual_c++_for_python\9.0\vc\bin\amd64\cl.exe   2   
Error   C3873   '0xa4': this character is not allowed as a first character of an identifier HISE Standalone_App c:\users\username\appdata\local\programs\common\microsoft\visual_c++_for_python\9.0\vc\bin\amd64\cl.exe   2   
... snipped for brevity

        And when trying to create a VST in the succesfully built 2.1.0 version I get this:

        c:\users\username\appdata\local\programs\common\microsoft\visual_c++_for_python\9.0\vc\bin\amd64\cl.exe : warning C4335: Mac file format detected: please convert the source file to either DOS or UNIX format [H:\HISE_Projects\Kit_One\Binaries\Builds\VisualStudio2017\Kit_One_SharedCode.vcxproj]

        Any thoughts on this?

        1 Reply Last reply Reply Quote 0
        • I
          Inveracity
          last edited by

          Alright I completely deleted everything, did a repair install of Visual Studio 2017 and the build tools. I went to GitHub, switched the branch to scriptnode and downloaded it as a zip file (instead of git clone)

          I set the CL environment variable to point to

          CL=c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe

          Now these are my build errors:

          c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe : warning C4335: Mac file format detected: please convert the source file to either DOS or UNIX format
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(1): error C3872: '0x90': this character is not allowed in an identifier
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(1): error C2018: unknown character '0x3'
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(1): error C2018: unknown character '0x4'
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(1): error C2018: unknown character '0x40'
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(1): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(1): error C2146: syntax error: missing ';' before identifier 'ÿÿ¸'
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(1): error C2018: unknown character '0xe'
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(1): error C2018: unknown character '0x1f'
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(1): error C2018: unknown character '0x1'
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C3872: '0x24': this character is not allowed in an identifier
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C3873: '0x2030': this character is not allowed as a first character of an identifier
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C3872: '0x2039': this character is not allowed in an identifier
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C3872: '0x2030': this character is not allowed in an identifier
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C2018: unknown character '0x18'
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C3872: '0x201c': this character is not allowed in an identifier
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C3872: '0x8d': this character is not allowed in an identifier
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C3872: '0x8f': this character is not allowed in an identifier
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C3872: '0xab': this character is not allowed in an identifier
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C3872: '0xa1': this character is not allowed in an identifier
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C3872: '0x2026': this character is not allowed in an identifier
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C3872: '0x2021': this character is not allowed in an identifier
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C3872: '0x2020': this character is not allowed in an identifier
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C2018: unknown character '0x6'
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(2): error C2001: newline in constant
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(3): error C2018: unknown character '0x6'
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(3): error C2018: unknown character '0x4'
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(3): warning C4129: '': unrecognized character escape sequence
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(3): warning C4129: '': unrecognized character escape sequence
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(3): warning C4129: 'g': unrecognized character escape sequence
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(3): warning C4129: '$': unrecognized character escape sequence
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(3): warning C4129: '_': unrecognized character escape sequence
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(3): fatal error C1004: unexpected end-of-file found

          followed by a ton of warnings and then finally

          Done building project "HISE Standalone_App.vcxproj" -- FAILED.

          I'm not sure what to do from here :crying_face:

          1 Reply Last reply Reply Quote 0
          • d.healeyD
            d.healey
            last edited by

            Could you describe your build process step by step?

            Libre Wave - Freedom respecting instruments and effects
            My Patreon - HISE tutorials
            YouTube Channel - Public HISE tutorials

            1 Reply Last reply Reply Quote 0
            • I
              Inveracity
              last edited by

              Definitely

              1. Download and extract HISE-scriptnode https://github.com/christophhart/HISE/archive/refs/heads/scriptnode.zip
              2. Insert the ASIOSDK2.3 and VST3 SDK into the SDK folder as per instructions
              3. Open Juce from HISE-scriptnode\tools\projucer\Projucer.exe
              4. In Projucer open HISE-scriptnode\projects\standalone\HISE Standalone.jucer
              5. Ensure Selected Exporter is set to `Visual Studio 2017" and then click the Visual Studio button to open up Visual Studio 2017.
              6. In VS2017 set the build to Release and x64 and go to the Build dropdown menu and select Build HISE Standalone_App
              7. Watch it attempt to build

              Does that seem somewhat correct?

              1 Reply Last reply Reply Quote 0
              • I
                Inveracity
                last edited by

                Quick update, I tried just clicking the Build Solution from the Build dropdown menu in VS2017 and that actually made it build the application.

                Moving on to building the VST 64bit with the newly built HISE.exe and I'm back to the same error messages as when I was building HISE itself.

                I'm so incredibly confused 😅

                1 Reply Last reply Reply Quote 0
                • LindonL
                  Lindon
                  last edited by

                  @Inveracity said in Compiling HISE 2.1.0 "No such file or directory":

                  c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe : warning C4335: Mac file format detected: please convert the source file to either DOS or UNIX format

                  maybe this (your first warning):

                  c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe : warning C4335: Mac file format detected: please convert the source file to either DOS or UNIX format

                  HISE Development for hire.
                  www.channelrobot.com

                  1 Reply Last reply Reply Quote 0
                  • I
                    Inveracity
                    last edited by

                    Thanks Lindon, unfortunately it doesn't say which files need to be converted and when I open random files with Sublime or VSCode they all say that the files have Windows line endings and utf-8 encoding - so I have no idea what it is I'm supposed to convert

                    1 Reply Last reply Reply Quote 0
                    • I
                      Inveracity
                      last edited by Inveracity

                      Been digging a little more (and also learning a lot more)
                      I found the batchCompile.bat script and changed

                      -set vs_args=/p:Configuration="Release" /verbosity:minimal
+set vs_args=/p:Configuration="Release" /verbosity:normal

                      and saw this in the output

                      "H:\HISE_Projects\Drum_Kit_One\Binaries\Builds\VisualStudio2017\Drum_Kit_One.sln" (default target) (1) ->
"H:\HISE_Projects\Drum_Kit_One\Binaries\Builds\VisualStudio2017\Drum_Kit_One_VST3.vcxproj.metaproj" (default target) (2) ->
"H:\HISE_Projects\Drum_Kit_One\Binaries\Builds\VisualStudio2017\Drum_Kit_One_SharedCode.vcxproj" (default target) (3) ->
(ClCompile target) -> 
  c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(1): error C3872: '0x90': this character is not allowed in an identifier [H:\HISE_Projects\Drum_Kit_One\Binaries\Builds\VisualStudio2017\Drum_Kit_One_SharedCode.vcxproj]
  c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(1): error C2018: unknown character '0x3' [H:\HISE_Projects\Drum_Kit_One\Binaries\Builds\VisualStudio2017\Drum_Kit_One_SharedCode.vcxproj]
  c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe(1): error C2018: unknown character '0x4' [H:\HISE_Projects\Drum_Kit_One\Binaries\Builds\VisualStudio2017\Drum_Kit_One_SharedCode.vcxproj]
... and so on ...

                      So are these generated files causing the issue?
                      because when I open them up they seem to be fine, windows line-endings and no strange characters as far as I can tell

                      1 Reply Last reply Reply Quote 0
                      • d.healeyD
                        d.healey
                        last edited by

                        Are you using a 32bit version of Visual Studio?

                        Libre Wave - Freedom respecting instruments and effects
                        My Patreon - HISE tutorials
                        YouTube Channel - Public HISE tutorials

                        1 Reply Last reply Reply Quote 0
                        • I
                          Inveracity
                          last edited by

                          Thanks for the help so far, I really appreciate it

                          It looks like Visual Studio is 32bit and when I search for a 64bit version all I find is Microsoft forum posts of people asking for a 64bit versions - so it looks like there are no 64bit versions of Visual Studio

                          I also tried a few different cl.exe's from different paths, but all of them give the same errors. I can only speculate that the ones in the x64 folders are 64bit version of cl.exe

                          C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\cl.exe
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\cl.exe
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\cl.exe
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\Hostx86\x86\cl.exe
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\Hostx86\x86\cl.exe
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx86\x86\cl.exe

                          I'm searching google, but I can't seem to find anything that relates to this, or I'm not using the right terms.

                          Got any other thoughts or ideas?

                          1 Reply Last reply Reply Quote 0
                          • d.healeyD
                            d.healey
                            last edited by

                            I'm really not sure what's causing the issue. I'm also not sure what cl.exe has to do with it.

                            Libre Wave - Freedom respecting instruments and effects
                            My Patreon - HISE tutorials
                            YouTube Channel - Public HISE tutorials

                            1 Reply Last reply Reply Quote 0
                            • I
                              Inveracity
                              last edited by

                              I have no idea either.

                              I guess that's it then

                              Thanks for helping either way :thumbs_up:

                              1 Reply Last reply Reply Quote 0
                              • d.healeyD
                                d.healey
                                last edited by d.healey

                                If you want to get in a call with screenshare and try and figure out the problem together I have an hour free tomorrow afternoon (UK time).

                                Libre Wave - Freedom respecting instruments and effects
                                My Patreon - HISE tutorials
                                YouTube Channel - Public HISE tutorials

                                1 Reply Last reply Reply Quote 0
                                • I
                                  Inveracity
                                  last edited by

                                  That's extremely kind of you to offer! :folded_hands:

                                  I think before I take your time from you I'll try completely resetting.

                                  I'll uninstall everything and redownload everything from scratch and try and document my steps as I go

                                  I must have done something wrong along the way the first time around

                                  1 Reply Last reply Reply Quote 1
                                  • I
                                    Inveracity
                                    last edited by

                                    I solved the problem! 🎊

                                    Essentially I had an old installation of the Build Tools present on my system, so when I installed Visual Studio 2017 I then had a duplicate build environment that was lacking the correct windows SDK (because I had been a dummy and installed the windows sdk into the build tools instead of vs2017).

                                    So I uninstalled the Build Tools via the Visual Studio Installer leaving only VS2017 installed.

                                    After that I removed the CL= environment variable entirely from my system and added

                                    C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64

                                    to the PATH environment variable so that cl.exe could be executed from anywhere.

                                    From here on it was following the video guide basically.

                                    I added the Windows 10 SDK (10.0.16299.0) by modifying the VS2017 installation in the Visual Studio Installer.

                                    Then I opened the HISE standalone project in projucer and built the HISE.exe as per the video instructions - this time no warnings of mac files detected!

                                    And finally I ran HISE, added a sampler and an empty UI, exported it as VST3 64bit and success! :party_popper:

                                    Now I can go back to actually making my instrument :face_with_tears_of_joy:

                                    1 Reply Last reply Reply Quote 2
                                    • First post
                                      Last post

                                    24

                                    Online

                                    1.8k

                                    Users

                                    10.4k

                                    Topics

                                    90.6k

                                    Posts