Re: [Development] Best practices for hacking Qt in QtCreator?
Hi, Am 21.09.2018 um 09:16 hat Sean Harmer geschrieben: > Works fine here as long as you open the project using a kit set up from that > particular build of Qt. I tend to just build qtbase etc on the command line, > setup a kit in creator for it, then open qt3d/qt3d.pro and it just works. Ok, I've used a kit based on a pre-built Qt versions. Probably not a good idea. So this is what I'm going to try: * do a developer build for the Qt version worked on * setup a kit for this build * see how to setup a build configuration that reuses the developer build the kit is based on I'd appreciate any advice on the latter! I'll share my experiences so this could become wiki content as Eddy suggested. Nils ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Best practices for hacking Qt in QtCreator?
On 21/09/2018 08:41, Nils Jeisecke via Development wrote: Hi there, although I'm usually using vim as my primary environment when hacking Qt itself it can be tempting to use QtCreator instead for better code navigation etc. Simply opening the .pro file of some Qt submodule does not really work out of the box. Lots of complaints about Qt includes not found etc. (with clang code model). Maybe someone is willing to share the secrets on how to configure QtCreator for a nice Qt developing experience? Works fine here as long as you open the project using a kit set up from that particular build of Qt. I tend to just build qtbase etc on the command line, setup a kit in creator for it, then open qt3d/qt3d.pro and it just works. Cheers, Sean ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
