[Bug]: Linux: overly strict assertion on executable path prevents valid use cases

[jistr]

Detailed steps on how to reproduce the bug

This assertion looks overly strict to me, requiring an absolute or relative path, but not allowing for binaries which reside on $PATH, even though later on execvp is used which should resolve the $PATH use case fine:

JUCE/modules/juce_core/native/juce_SharedCode_posix.h

Lines 1105 to 1106 in 22df0d2

	jassert (File::getCurrentWorkingDirectory().getChildFile (exe).existsAsFile()
	|| ! exe.containsChar (File::getSeparatorChar()));

If the program is not in working dir, it is on $PATH instead, and it has been launched only using its name (e.g. helio) and not via its absolute path (e.g. /usr/bin/helio) then the assertion will fail.

The strict assertion seems to be the root cause of this issue: helio-fm/helio-sequencer#280

What is the expected behaviour?

Program on $PATH should be executable using its command name without any path components (absolute or relative).

Operating systems

Linux

What versions of the operating systems?

Fedora 38 (but i don't think it's relevant)

Architectures

x86_64

Stacktrace

No response

Plug-in formats (if applicable)

No response

Plug-in host applications (DAWs) (if applicable)

No response

Testing on the develop branch

The bug is present on the develop branch

Code of Conduct

• I agree to follow the Code of Conduct