administrators

It should compile on macOS, so chances are good that Linux behaves too - you might need to remove a few std::absf and friends again

Ah, what's the problem there?

You should put your fonts in your projects Images folder.

Yes, definitely put them there, otherwise it won't be embedded in the binary and will use a fallback font on the end users machine, which defaults to Comic Sans MS.

I've added this here:

https://github.com/christophhart/HISE/commit/9e428617ef80f1033bc01902bb3663c513767b8b

Although I have no system at hand to verify that it works. Can you check it?

Yes the buildscript expects it to be at Installer/OSX

A standalone app is in fact a folder with a hidden file indicating that it's executable. The actual binary resides in a subfolder called Content/macOS (or something like that).

Not that it makes any difference to anything...

This file is a bit too complicated to autogenerate, but here's the one I used for Hexeract:

PackageTemplate.zip

Just do a search and replace for your company with %COMPANY% (use all underscores since it's a bundle identifier) and your project with %PROJECT% - I hope I am not leaking any internal passwords that I forgot to remove

You might have to delete the AAX target in Packages,

No actually this is the develop branch (it‘s just poor branch policy) so if you find something let me know and I‘ll take care of it at the next round of bug fixing.

The plan is to release HISE 3.0 in about two months so everything that needs to be polished should be done by then.

Try running auval on it - it‘s a built in command line tool that validates AU plugins.

Which flags are you talking about?