[QBS] New item ProductFolder
jochen_becher at gmx.de
Tue Jun 4 21:32:15 CEST 2013
I believe your idea of SubProject and my idea of ProjectFolder are not
the exact same thing and we need both: ProjectFolder is just a grouping
of Products and nested ProjectFolders under a folder name. SubProject
sounds like an enhanced concept of Project which allows real sub
projects which can be built stand-alone or as part of a larger Project.
Of course it should be possible to use SubProjects in a way that they
only act as a folder in Projects but I would like to have an extra
keyword and an extra handling in the API and qbsprojectmanager for it
(e.g. Wizards should behave quite different if you just add a
descriptive layering folder in a Project or a complete SubProject for
So I want to continue my ProjectFolder implementation (which is a must
for usage of qbs in our development environment) and someone else may
implement the more complex SubProjects. Possibly once the SubProjects
are implemented one may find a way to eliminate the ProjectFolder
implementation and replace it with some specialization of SubProjects if
still QtCreator can support the difference concepts behind it
Do you agree?
Am Dienstag, den 04.06.2013, 10:10 +0200 schrieb Joerg Bornemann:
> On 03/06/2013 20:32, Jochen Becher wrote:
> > Of course nested projects could also be done. But especially the
> > implementation within qbs source code makes nested projects not the
> > first choice to me (ResolvedProjects contains attributes and methods
> > which are really only used from the top-level project and will not make
> > any sense within a nested project, won't they?)
> Sure, that's how it looks now. But the code can be changed.
> > Furthermore I would like to allow having ProjectFolder as a root element
> > within a referenced qbs file (currently only product is allowed here).
> > Having a Project as a root element in referenced qbs files would
> > introduce some kind of fuzziness of the project/product concept.
> No, it must be possible to reference a subproject that can be built as
> stand-alone project as well. This would be impossible with the
> ProjectFolder approach.
> Also, I don't want to enforce the Project item in qbs files that are
> referenced as subproject. In that case that SubProject thingy basically
> acts as logical grouping for display purposes, very much like a folder.
More information about the Qbs