Thanks for the input, Matthias. It's been some time since I built it from scratch, so I wouldn't be able to provide specifics. But it was on Ubuntu 16, and Mark's comments about Qt5, QScintylla and libpng did ring a bell for me, since the email. I'll try again on the next couple of days and if there's interest I can report on how it went.
André 2017-03-17 13:29 GMT-03:00 Matthias Kuhn <matth...@opengis.ch>: > Hi André and Mark, > > Can you clarify on which systems you are working and which dependencies > cause headaches? > > In many situations, a build of Qt is not required and doing this > requires deep understanding of all the involved libraries. I would > strongly advice anyone to first explore other alternatives before > starting the walk on this tricky road. > > For reference, here is a set of script that is able to build many of the > dependencies (into a custom root path) for those who still want to do it: > https://github.com/opengisch/osgeo4travis/tree/master/docker/qt5/scripts > > Best regards > Matthias > > On 03/17/2017 05:17 PM, André William wrote: > > Hi all, my name is André, this is my first email on this list. > > > > I've also struggled with building QGIS before, and besides the problems > > mentioned by Mark, the default installed libraries are often > > incompatible with QGIS or some of its dependencies. > > I'd be willing to help with documenting my steps or possibly > > contributing code to the scripts as I attempt to build on a clean OS. > > > > André > > > > 2017-03-17 12:26 GMT-03:00 Matthias Kuhn <matth...@opengis.ch > > <mailto:matth...@opengis.ch>>: > > > > Hi Mark, > > > > Are the dependencies not available for your distribution? > > > > Except for some very special systems (Android, very old ubuntu > versions > > on travis...) I never ever build these dependencies manually and just > > install them. > > > > Matthias > > > > On 03/17/2017 04:21 PM, Mark Johnson wrote: > > > For the last 10 days I have been attempting to build QGIS 3.0 > master > > > from scratch. > > > For this QT 5 also had to be build, which is not an easy task. > > > > > > In the past I had used the 'run' scripts, which installed the > source > > > - qt-opensource-linux-x64-5.7.1.run > > > but after the first installment I noticed that QGIS needed a modal > that > > > had not been included: QtWebKit > > > > > > The there is QScintilla,PyQt5 (with sip) and Qwt > > > - Qwt: did not install the libs where PyQt5 could not find it > > > - QScintilla did not accept the –-pyqt=PyQt5 parameter, so > > > the configure.py had to be adapted > > > > > > And then there is the cmake of QGIS3 itself, which in itself is a > horror > > > dream come true > > > - instead of asking *once* for the 'Qt5 cmake' directory > > > -- it asks it about 12 times for the 17 modals needed > > > --> I assume ccmake determines for each module the dependencies, > > but for > > > the user this is a horrible - time consuming experience > > > > > > --- > > > For this reason I think it would be a good idea to add an area in > the > > > QGIS wiki with tip how this should be done, > > > > > > Based on a specific QGIS version > > > - which other versions (QT5, python3 [python 3.5.3rc1 does not > work, > > > python 3.4.6 does] etc.) should be used > > > - basic howto's to > > > -- build QT5 from scratch (like using git that contains QtWebKit, > as > > > apposed to the 'run' that does not) > > > -- known irregularities > > > ---> copy the Qwt/libs to the Qt5/libs so that PyQt5 can find them > > > ---> QScintilla how to adapt the configure.py script to create the > > > needed PyQt5 version > > > > > > The goal would be to offer a guideline for those doing this for the > > > first time > > > - avoiding known traps > > > > > > --- > > > Something in the form of (based on the present wiki): > > > > > > Organize an event > > > ... > > > Collaborative documents > > > ... > > > Building QGIS 3.0 from scratch > > > Building QT 5 from scratch > > > Building and correctly installing Qwt > > > Building QScintilla for PyQt5 > > > Building PyQt5 > > > QGIS3 ccmake > > > > > > I would be willing to start this with my experiences. > > > > > > Mark Johnson, Berlin Germany > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Qgis-developer mailing list > > > Qgis-developer@lists.osgeo.org <mailto:Qgis-developer@lists. > osgeo.org> > > > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> > > > Unsubscribe: > > https://lists.osgeo.org/mailman/listinfo/qgis-developer > > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> > > > > > _______________________________________________ > > Qgis-developer mailing list > > Qgis-developer@lists.osgeo.org <mailto:Qgis-developer@lists. > osgeo.org> > > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> > > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> > > > > > > > > > > _______________________________________________ > > Qgis-developer mailing list > > Qgis-developer@lists.osgeo.org > > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > > > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer