in the USER_CODE_SECTION of your product’s AppConfig.h. This will effectively disable the code in the following SECTION A:
In accordance with the terms of the JUCE 5 End-Use License Agreement, the
JUCE Code in SECTION A cannot be removed, changed or otherwise rendered
ineffective unless you have a JUCE Indie or Pro license, or are using JUCE
under the GPL v3 license.
End User License Agreement: www.juce.com/juce-5-licence
My only experience with this was with Travis, and I was able to sort it using the instructions I posted above. Sorry, I couldn’t say for other environments.
In case it may be relevant to this discussion, proposals have been done regarding the possibility to remove the dependency upon X even for Linux audio plug-ins that don’t need it:
I am running Jenkins, which had no problem on Mac and Windows virtual machines, but the linux it wouldn’t run.
I installed xvfb after posting and added the xvfb-run call, that @jamiebullock posted, so that works now.
I still feel for a tool I would prefer not to depend on an xserver, but for the moment it’s fine. I just would love to understand, what makes the Projucer with almost 20 command line options relying on a GUI.
Actually it is not really working:
It works once, but I have more than one projects that I want to build, and the identical call fails for the second project. Is there a limitation on xvfb-run?
My problem is not so much about having the XServer installed, but to configure jenkins to use/access it. I had the same problem with pluginval in the mac/windows instances as well…
I’m not sure I understand the problem then.
I’ve never actually run a Ubuntu 18 Jenkins system but I have set up several Ubuntu 16 Jenkins systems and I never had to explicitly start X or run xvfb to get the PJ to resave projects?
And set up a multibranch pipeline just standard, but the command I wrote earlier (Projucer --resave foo.jucer) fails with “Couldn’t connect to display”, and it is able to perform once using the xvfb-run, but fails, if I call it twice.
It could also be, because those two projects are parallel stages… maybe xvfb-run needs to be called sequential… I will try removing the parallel…