Is there any reason for ‘make cintdlls’ to be executed also when there are
no changes at all in the build directory?
Why it has to be called separately in the building process (this is what
I see in the spec file)?
Cheers, Germano
The cintdlls need to be rebuilt only when some things change in CINT and in some the dictionary helper files. Generating the cintdlls takes a long time. So it was decided to make it as separate steps (and generating the proper dependency from them is not trivial). We hope to improve this (so they are automatically generated when needed) but this is not trivial.
Philippe
[quote=“pcanal”]The cintdlls need to be rebuilt only when some things change in CINT and in some the dictionary helper files.
[/quote]
So, you do agree that is strange a rebuilding while nothing is
changed…
[quote=“pcanal”]
Generating the cintdlls takes a long time. So it was decided to make it as separate steps (and generating the proper dependency from them is not trivial). We hope to improve this (so they are automatically generated when needed) but this is not trivial.
Philippe[/quote]
Let me know if I’ve understood: if only one source file is changed, I have
no way at all to know if cint dlls have to be rebuilt?
I have seen it; rebuilding takes “a few” (…)
I’m waiting for your developments.
Tnx, Germano
[quote]Let me know if I’ve understood: if only one source file is changed, I have no way at all to know if cint dlls have to be rebuilt? [/quote]Well, in general you only need to rebuild them if the CINT header files and the cont/inc/Proxy.h have changed.
Philippe.