[Qbs] (no subject)

[Dan Pat]

>
> You can provide your own cpp implementation by overriding the search
> path, but I don't see how you would be able to refer to the contents of
> the original directory. Note that the files there are implementation
> details and their presence and names cannot be relied upon. It's not a
> supported use case to derive from these items. So to achieve what you
> want, you'd have to copy the qbs module files you want to extend


My fears confirmed.

Out of curiosity: Which special features does it implement and why are
> they not suitable for upstreaming?


The goal is to get qbs projects compiled to WebAssembly using the
emscripten toolchain (and Qt WebAssembly). As for upstreaming: I have
managed to come up with a working but hacky solution (a small test project)
which I believe has room for improvement.

вт, 27 окт. 2020 г. в 15:58, Christian Kandeler <christian.kandeler at qt.io>:

> On 10/27/20 11:47 AM, Dan Pat wrote:
> > Hi, I have created a Module that inherits GenericGcc
>
>
> Out of curiosity: Which special features does it implement and why are
> they not suitable for upstreaming?
>
>
> > and hence is loaded as a "cpp" module when certain conditions are met.
> > During development the module file was located in the module directory
> > of the QtCreator installation. But I would like to move it to the qbs
> > module directory inside our project (using qbsSearchPaths). It is
> > desirable that the module be addressable by "cpp" name to avoid
> > changing the project files. To try to achieve that I created a
> > directory called "cpp" in the project module directory hoping that the
> > contents of this directory and the contents of the QtCreator qbs
> > module directory will somehow merge together. But it didn't work as
> > you might guess). Any ideas how to pull that off without having to
> > keep a copy of the file in the QtCreator qbs module directory?
>
>
> You can provide your own cpp implementation by overriding the search
> path, but I don't see how you would be able to refer to the contents of
> the original directory. Note that the files there are implementation
> details and their presence and names cannot be relied upon. It's not a
> supported use case to derive from these items. So to achieve what you
> want, you'd have to copy the qbs module files you want to extend.
>
>
>
> Christian
>
> _______________________________________________
> Qbs mailing list
> Qbs at qt-project.org
> https://lists.qt-project.org/listinfo/qbs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qbs/attachments/20201027/290a97fe/attachment.html>