Hi Jules and ROLI team, there's an issue with the "juce_getExecutableFile()" posix implementation when running a juce-based tool.
Everything works fine if you run "./JuceDemo" or "./full/path/to/JuceDemo" but it fails when JuceDemo is in $PATH and we run "JuceDemo".
You can try this yourselves on Linux or OSX, the steps are:
1 - build JuceDemo
2 - run this:
export PATH=/path/to/JuceDemoDir:$PATH JuceDemo
3 - Try the "Child Process Comms" and see it fail with an assertion on "ChildProcess::ActiveProcess".
The assertion happens because the Juce code is trying to find the current "JuceDemo" path based on the working directly (usually /home/user), which will obviously fail.
If the path is not relative or absolute (doesn't start with "/" or ".") we need to look up for the binary in $PATH.
Here's a patch to fix this: https://gist.githubusercontent.com/falkTX/0af036871c13389d64e3/raw
PS: This will fix a known Linux issue in a specific juce-based host ;)