>It's expected that the generator won't re-run, because the dependency
parsing happens when building a cpp file.
So, I guess, this explanation must be correct.
вт, 27 окт. 2020 г. в 15:22, Dan Pat :
> >As Christian said: The problem is that the cpp scanner is triggered by the
> >generated cpp fil
>As Christian said: The problem is that the cpp scanner is triggered by the
>generated cpp file, but there is no connection to the testinput.h because
>your cpp files is not including it.
Sorry for getting back to this so late. I have missed a very important
detail - the generated cpp files do inc
>> "testinput.h" file contains "#include "a.h" directive. Changing
>> testinput.h results in a generator run followed by a C++ compiler run.
>> Changing a.h results in no action, although in this case the generator
>> is intended to reprocess its input.
>
> It's expected that the generator won'
On Tue, 15 Sep 2020 22:10:13 +0500
Dan Pat wrote:
> "testinput.h" file contains "#include "a.h" directive. Changing
> testinput.h results in a generator run followed by a C++ compiler run.
> Changing a.h results in no action, although in this case the generator
> is intended to reprocess its inpu
Probably, I haven't made myself clear enough. Here's an example setup.
This is a dummy generator's module definition:
import qbs
import qbs.FileInfo
import qbs.TextFile
Module {
id: testgen
Rule {
inputs: ["genxx"]
Artifact {
id: artifact
Yes, the product does depend on the 'cpp' module. The include paths are
fine, since the same header files are later used by the compiler. A little
more detail: I use the Group language item to tag such headers
appropriately.
Assuming that the generator inputs tag is "genxx", the fileTags of the
Gro
But it will only scan for dependent header files if the product using the code
generator depends on the `cpp` module and if the `cpp.includePaths` are set up
correctly, right?
Is this the case?
Best
Jochen
___
Qbs mailing list
Qbs@qt-project.org
http
On Mon, 14 Sep 2020 19:11:41 +0500
Dan Pat wrote:
> Hi, I have a code generator using C++ *.h headers as its input. Everything
> works fine for me except for dependency tracking. Since inputs are ordinary
> include files they often include other include files which include other
> include files e
Hi, I have a code generator using C++ *.h headers as its input. Everything
works fine for me except for dependency tracking. Since inputs are ordinary
include files they often include other include files which include other
include files etc. The problem is that when an include file included by the
