Build on Debian 9.9 fails





  • Christoph posted a few hours ago that the master branch was temporarily broken and to compile you have to delete everything.
    https://forum.hise.audio/topic/1420/audio-glitches-on-irs-hise-2-0/15



  • Make clean destroyed ~/.vst again



  • I noticed version 2.1.0 and the standalone built clean and successfully

    although ended with these notes...

    Linking HISE Standalone - App
    ../../../../JUCE/modules/juce_core/zip/zlib/deflate.h:96:16: warning: type ‘struct internal_state’ violates the C++ One Definition Rule [-Wodr]
     typedef struct internal_state {
                    ^
    ../../../../JUCE/modules/juce_graphics/image_formats/../../juce_core/zip/zlib/zlib.h:1347:12: note: a different type is defined in another translation unit
         struct internal_state {int dummy;}; /* hack for buggy compilers */
                ^
    ../../../../JUCE/modules/juce_core/zip/zlib/deflate.h:97:15: note: the first difference of corresponding definitions is field ‘strm’
         z_streamp strm;      /* pointer back to this zlib stream */
                   ^
    ../../../../JUCE/modules/juce_graphics/image_formats/../../juce_core/zip/zlib/zlib.h:1347:32: note: a field with different name is defined in another translation unit
         struct internal_state {int dummy;}; /* hack for buggy compilers */
    


  • HISE 2.1.0 VST also built successfully however HISE.jucer needs a slight modification

    hi_streaming
    hi_tools
    hi_ztsd

    had the wrong paths



  • @oddyotrax said in Build on Debian 9.9 fails:

    Make clean destroyed ~/.vst again

    Are you sure you didn't use an older file? There is nothing in the Projucer file indicating that it will use the plugin folder as build directory.

    Also you might need to recompile the Projucer since the binary in the repo is still using the 5.2.0 version.



  • Is version 2.1 alpha, beta or stable?



  • To be honest I messed up the git merge - I intended to merge the feature branch I was working on back into develop, but GitHub's merge function decided to use the master branch as target.

    Therefore I wouldn't call it a stable release (this is why I didn't put up a binary release on the GitHub release page), but I keep on polishing the edges for the next days so by the end of the week I plan to do a proper release (probably 2.1.1) which is as stable as it gets.



  • I managed to build the Standalone v2.1.0 from the latest git pull but the VST failed again


Log in to reply
 

8
Online

503
Users

1.8k
Topics

13.7k
Posts