No, if we do this the build will break because the
WebBrowserComponent will no longer be declared or defined.
I’m fairly sure that I tried the
--as-needed and it didn’t work. The build fails at the compile stage due to the lack of webkit.
Updating the Projucer to not add the webkit2gtk dependancy won’t help in building the Projucer though. It would need to be in the repo like that so a fresh clone would build.
I may not have explained this very well because all this webkit malarky has caused several problems. I’ve been trying to report them separately to avoid confusion but they do overlap. I’m talking about a specific use-case here:
• I have a Mac whose only job is to host Jenkins, everything is automated and there is no user-interaction
• The first thing Jenkins does is a Git clone
• Then it tries to build the PJ in order to generate the rest of my project files as these are not checked in to source control
• On Ubuntu 14 this is done with something like this
cd $projcuerRoot make Config=Release $projucerExe --resave $projectJucerFile
• The PJ will fail to compile due to the missing webkit
• Now I can’t generate my Makefiles and build my projects
• Jenkins sends me angry emails
What I need is a way to specify on the command line to not build the PJ with a dependancy on webkit.
The problems are:
• As it stands, if I compile the PJ with
JUCE_WEB_BROWSER=0, it won’t build
--as-needed linker flag doesn’t work, the compile fails before it hits the link stage
• How do I add extra pre-processor definitions to
make if we could get the above to work?
• I would really rather not have to write a script that manually removes the
webkit2gtk text from the freshly cloned JUCE repo. This feels very hacky and kind of defeats the point of building exactly what is in Git