This is not a bug, but is just annoying.
Projucer creates the Makefile using relative path to the source code, “…/…/Source/PluginProcessor.cpp”.
When we use “JUCE_LIVE_CONSTANT()” we get this message in the terminal “JUCE Assertion failure in juce_LiveConstantEditor.h:237”. This asset is shown if we compile using relative path, which is the case. Thus, every time I use JUCE_LIVE_CONSTANT I get this message shown with my other debug messages and is really annoying.
If Projucer could create the Makefile using absolute path to get the source files this assertion is not shown. One way would be to get the location of the “.jucer” file and replace it in the Makefile. Another option would be to get the Makefile location from within the Makefile:
MAKEFILE_PATH := $(shell dirname "$(realpath $(firstword $(MAKEFILE_LIST)))") ... ... -I$(MAKEFILE_PATH)/../../JuceLibraryCode ... ... $(JUCE_OBJDIR)/PluginProcessor_a059e380.o: $(MAKEFILE_PATH)/../../Source/PluginProcessor.cpp
I tested this “MAKEFILE_PATH” option and it works…