Home » Developing U++ » U++ Developers corner » build_info.h
Re: Uppiverse [message #55575 is a reply to message #55574] |
Sun, 22 November 2020 19:07  |
Novo
Messages: 1430 Registered: December 2006
|
Ultimate Contributor |
|
|
mirek wrote on Sun, 22 November 2020 12:27Novo wrote on Sun, 22 November 2020 18:12mirek wrote on Sun, 22 November 2020 08:25
Well, what information from git would you want? branch? hash?
Mirek
Everything for each used component.
I usually store this info with app to be able to recall what was used to build this app.
I am afraid "everything" is a bit generic term for me. Would you care to e.g. show me the example?
At least name of a component, URI, and all other attributes presented in supported VCS, like branch (not sure about branches in SVN), hash is also not a generic property, revision ID (specific to SVN and Mercurial, I guess).
The way I'd like to use it is in a form of an X-macro like in an example below.
struct VAR : adt::PropMap<String, String>, Empty {
#define LIST_OF_MEMBERS \
X(UPP) \
X(OUTPUT)
VAR ()
: Empty()
#define X(name) , name(map, #name)
LIST_OF_MEMBERS
#undef X
{}
#define X(name) Prop name;
LIST_OF_MEMBERS
#undef X
#undef LIST_OF_MEMBERS
}; // VAR
Basically, I'd like to get a LIST_OF_COMPONENTS define.
Regards,
Novo
|
|
|
Goto Forum:
Current Time: Wed May 14 23:04:24 CEST 2025
Total time taken to generate the page: 0.01730 seconds
|