Solved Problem building qtbase from source
-
@Tom-asso Since you're you're installing into /usr/local you should call make install with sudo.
-
@jsulm - ah, you are right of course!
-
Note that if you want to hack on Qt itself, you can use the developer-build and it will do an in place build. However it should not be used to build software releases as it toggles some flags for development.
-
@SGaist - could you please explain? What is the "developer build", and what is the "development.3" flag?
I would like to modify qtdatavisualization3d for my app, then freely distribute to users on a non-commercial basis - which source file should I be using in that case?
Thanks! -
The 3 was a typo.
As I wrote, it will trigger an in-place build, meaning that you won't have to call make install each time you want to test your modifications.In that case, you should only build that module rather than the whole of Qt.
-
@SGaist - thanks. Earlier you mentioned a "Ce" option to specify a particular sub-folder to build. Can you please refer me to a page describing how to use that?
Thanks! -
@SGaist - after building in-place with 'make', the libraries are scattered among many different subdirectories. What is the best way to link against those, when there are in so many different places?
Thanks! -
Did you do a build from scratch after adding that option to your configure line ?
With a developer build you should have all binaries in qtbase/bin and the libraries in qtbase/lib.
-
@SGaist - yes I see them there, thanks.
Earlier you mentioned a "Ce" option to specify a particular sub-folder to build. Can you please refer me to a page describing how to use that?
Thanks! -
I do not see a qtcreator executable after building qt-everywhere-src-5.14.2. Is that expected?
I built with these configure options: -qt-xcb -recheck-all -debug -developer-build -
Yes it is to be expected, Qt Creator is a independent project.