[QBS] Qbs Roadmap
Jochen Becher
jochen_becher at gmx.de
Sat Jun 1 12:36:05 CEST 2013
Am Samstag, den 01.06.2013, 12:01 +0200 schrieb Pau Garcia i Quiles:
> Hello,
>
>
> If you are into qbs already, you are probably not interested but
> anyway: CMake does everything you want. E. g. you can use the
> source_group command to group into folders in Visual Studio, it does
> run CMake automatically when any project file (CMakeLists.txt) has
> been changed and reloads the projects if there are changes, etc
>
I know CMake and we are looking into that build system also. But the
support for CMake in QtCreator is also missing a lot of features and we
want to switch to QtCreator because it is the only IDE that has support
for QtQuick and it has already more refactoring features than Visual
Studio (even if VisualAssist or something similar is installed).
Also the C++ code model of QtCreator is much better than the Visual
Studio's one (which in fact is not a code model but crap) and we use
that for some extensions.
Regards, Jochen
>
> On Sat, Jun 1, 2013 at 11:46 AM, Jochen Becher <jochen_becher at gmx.de>
> wrote:
> Am Freitag, den 31.05.2013, 17:39 +0200 schrieb Joerg
> Bornemann:
> > On 31/05/2013 14:29, Jochen Becher wrote:
> >
> > > in my company we are currently trying to switch from
> Visual Studio with
> > > Qt plugin to QtCreator. We were running into some
> conceptional problems
> > > with qmake so we are currently looking into Qbs as an
> alternative.
> >
> > Just out of curiosity, could you tell us what these
> conceptional
> > problems are in detail?
>
>
> 1. qmake / jom is much slower than Visual Studio build
> 2. Integration of Incredibuild with qmake is much slower than
> Visual
> Studio (each (library) linkage serializes the build process
> and we have
> about 90 libraries/executables in our largest solution so it
> gets
> unacceptable slow)
> 3. jom (and nmake) do not reload the make files after it has
> been
> changed by an embedded qmake run. One has to start qmake
> manually after
> each change in any .pro file.
> 4. No virtual folder for projects or source files are possible
> with
> qmake (we fixed that partly with a patch to QtCreator and some
> extra .pro files we introduced which do something similar to
> virtual
> solution folders in Visual Studio)
>
> >
> > > We understand that Qbs' integration into QtCreator is
> still not ready
> > > for daily use (e.g. because of issue QBS-19 and others) so
> I would like
> > > to know if there is any detailed roadmap of Qbs for the
> next months.
> >
> > QBS-19 (add possibility to add files to qbs projects in Qt
> Creator) is
> > just about adding files via right-mouse click and a context
> menu. You
> > can add files by directly editing the project file of
> course.
> >
>
>
> Of course. But we cannot expect our developers to prefer
> QtCreator over
> Visual Studio if wizards do not work as usual. We have built
> our own
> QtCreator wizards adopted to our developer environment (the
> new wizards
> do a lot more than the standard ones). We need the possibility
> to add
> projects, products, groups and files in a flexible way before
> we can
> switch to qbs.
>
> > The roadmap can be viewed in JIRA. It is reachable via the
> main project
> > page https://bugreports.qt-project.org/browse/QBS
> > There are the planned future versions visible. Every
> accepted issue got
> > a version assigned to it that indicates when they are
> supposed to be fixed.
> >
>
>
> Thank you, I will look into this.
>
> Best Regards, Jochen
>
> >
> > BR,
> >
> > Joerg
>
>
> _______________________________________________
> QBS mailing list
> QBS at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qbs
>
>
>
>
>
> --
> Pau Garcia i Quiles
> http://www.elpauer.org
> (Due to my workload, I may need 10 days to answer)
More information about the Qbs
mailing list