Develop branch build status

[frametek]

Error Group
Undefined symbol: typeinfo for juce::Timer
Undefined symbol: juce::Component::mouseMove(juce::MouseEvent const&)
Undefined symbol: juce::Component::mouseDown(juce::MouseEvent const&)
Undefined symbol: juce::Component::mouseDoubleClick(juce::MouseEvent const&)
Undefined symbol: juce::Component::setName(juce::String const&)
Undefined symbol: juce::Component::setVisible(bool)
Undefined symbol: juce::Component::addToDesktop(int, void*)

this is just a snippet- there are a total of 100 errors. This seems to be related to the lto.o compiler errors?

[d.healey]

@frametek Did you clean the build directory after building the standalone?

[frametek]

Yes. Same problem. I'm using Xcode 12.01 on a M1 Mini (Big Sur) so the build is Intel only.

[d.healey]

@frametek said in Develop branch build status:

Xcode 12.01 on a M1 Mini

That's the info that should have been in your first post :p In which case I'm not sure how to direct you as I don't have such a system. BTW why are you wanting to build HISE as an AU?

[frametek]

I'm new to HISE and since the plugin it was part of the project, wanted to see if it worked. My guess is people are using HISE in standalone as a development system to create custom instruments and exporting them to AU, etc.

[d.healey]

@frametek Yeah that's pretty much correct. There is almost no need to work with HISE as a plugin, except if you're making an FX plugin or want to test certain aspects of your project inside a DAW within HISE.

[Natan]

@Lindon said in Develop branch build status:

he EQ display still "laggy" in the development branch?
Any other "known problems"?

I Think So, And Another Issue Is That On Windows, Pop Up Menus won't Resize and Get Adapted To The Windows Scale Size.

Still Waiting For Those 2 To Get Fixed And Switch To Develop.
And Yeah The Last Release Fails On Windows, And No Built :/

[d.healey]

@Natan said in Develop branch build status:

The Last Release Fails On Windows, And No Built

Tell us more. What errors are you getting?

[Dan Korneff]

@d-healey Would you be able to give some build advice for Linux?
Here's where I'm at so far:

• Starting from the ground up with a new system.
• Installed recommended dependencies.
• working with the latest Master branch (also tried develop)
• ran make CONFIG=Release
• got ipp error

../../../../../HISE/hi_backend/../hi_modules/../hi_scripting/../hi_sampler/../hi_components/../hi_dsp/../hi_core/../hi_tools/../hi_streaming/hi_streaming.h:69:10: fatal error: ipp.h: No such file or directory
   69 | #include "ipp.h"
      |          ^~~~~~~
compilation terminated.

• installed latest IPP (oneaip)
• re-targeted Extra Linker Flags in Projucer
  
  
  That fixes the IPP issue.
  Now when I run make CONFIG=Release, I get stuck at the next error:

make: *** No rule to make target '../../../../hi_scripting/scripting/scriptnode/ScriptNodeTestSuite.cpp', needed by 'build/intermediate/Release/ScriptNodeTestSuite_6b3f695a.o'.  Stop.

A quick google search says the message means the file is missing. When I check the HISE folder, it's definitely not there.
Does any of this seem familiar to you?

[d.healey]

@dustbro said in Develop branch build status:

working with the latest Master branch (also tried develop)

I haven't built with IPP for years so I'm not familiar with any issues you might encounter with that.

I'm using the develop branch.

You need to add -fpermissive to the compile flags.

[Dan Korneff]

@d-healey said in Develop branch build status:

I'm using the develop branch.
You need to add -fpermissive to the compile flags.

Thanks for this! I added the flag and ditched IPP. Got way closer with Develop branch.

I'm getting an error with the -Wno-inconsistent-missing-override flag

At global scope:
cc1plus: note: unrecognized command-line option ‘-Wno-inconsistent-missing-override’ may have been intended to silence earlier diagnostics
make: *** [Makefile:248: build/intermediate/Release/include_hi_dsp_library_01_6050d6b.o] Error 1

Is this flag needed?

[d.healey]

That's not an error, that's a warning/note. The error will be further up in the terminal and will probably have the word error in red text (depending on the terminal you're using). I don't know if the flag is needed but I always leave it in.

[Dan Korneff]

@d-healey said in Develop branch build status:

That's not an error, that's a warning/note.

You are correct.

In file included from ../../../../../HISE/hi_dsp_library/hi_dsp_library_01.cpp:54,
                 from ../../JuceLibraryCode/include_hi_dsp_library_01.cpp:9:
../../../../../HISE/hi_dsp_library/snex_basics/snex_DynamicType.cpp: In constructor ‘snex::VariableStorage::VariableStorage(snex::Types::ID, const juce::var&)’:
../../../../../HISE/hi_dsp_library/snex_basics/snex_DynamicType.cpp:21:50: error: conversion from ‘const juce::var’ to ‘int64_t’ {aka ‘long int’} is ambiguous
   21 |   data.p.data = reinterpret_cast<void*>((int64_t)value);
      |                                                  ^~~~~

[d.healey]

@dustbro Oh it's that error again! I thought I'd fixed all those.

Use my development branch for now - https://github.com/davidhealey/HISE/tree/development - it's up to date with Christoph's develop branch plus a few extras from the new_layout branch.

[Dan Korneff]

@d-healey Thanks so much!
I don't see a jucer file in the standalone folder. Do I use the Makefile in the TravisCI folder?

[d.healey]

@dustbro Oh yeah I screwed up a commit and lost my jucer file :p just use the one from the develop branch and set it up as you had before with the -fpermissve flag etc.

[Dan Korneff]

@d-healey You rock!
Success on this end. Thanks again for the help.

I also took a chance and installed with the latest IPP. that worked as well. You just have to change the file paths like the pics above.

Now I have some novice Linux desktop questions for ya. Once HISE is compiled, where is the recommended folder to drop it in? I notice other apps use /opt

[d.healey]

@dustbro The opt folder is for apps for all users, I only have one user on my system but I still prefer to keep my apps in the home folder, it also means I only have one location to backup. Some apps though seem to prefer the opt folder so I let those install where they want.

I added a hidden folder in my home folder called apps which is where I put executables. But in the case of HISE I leave it where it compiles it in the source code folder and add a shortcut to my menu, so when I recompile I don't have to go moving binaries or updating shortcuts again.

[Dan Korneff]

@d-healey Excellent idea. Also, how do you change the app icon? The default "gear" icon is unnerving

[d.healey]

@dustbro Which desktop environment are you using? I just realised you meant the binary icon. No idea, I just leave it as is. I change the icon in my menu shortcut though.