Re: [Cppqed-support] git commits in version information

[Raimar S. <rai...@ui...>]

Hi András,

in principle this is a good Idea, I have also thought about how to get this to 
work without additional user action.

On Wednesday, January 08, 2014 15:17:55 Andras Vukics wrote:
> I suggest that we put the inclusion of "Version.h" and
> "component_versions.h" into a header which is included by all scripts. A
> straightforward choice is Evolution.h, which we then move from core to
> scripts.

Version.h is unproblematic, but component_versions.h is automatically 
generated and only available in the build directory of script projects. Only 
there all the components can be known. This can also include custom elements 
projects, about which C++QED knows nothing.

Therefore the header including component_versions.h must only be used by 
scripts.

> Also, this call:
> updateVersionstring(cppqed_component_versions());
> should perhaps be wrapped in the constructor of some class, of which we
> then initialize a dummy instant in the scope of the global namespace. Scott
> Meyers writes about how to do this correctly in issue 4 of Effective C++
> (3rd edition), I will have to check.

For the reason stated above, this call cannot be in any of the C++QED 
libraries. Maybe we can work with a template that gets instantiated by the 
script? But I'm not sure how to do this automatically, and I don't have the 
book at hand.

> Then, script writers will not be additionaly burdened by the
> version-display issue.
> What do you think?

That would indeed be very nice!

Best regards
Raimar