Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » U++ Developers corner » build_info.h
build_info.h [message #55543] Fri, 20 November 2020 19:07 Go to next message
Novo is currently offline  Novo
Messages: 1098
Registered: December 2006
Senior Contributor
It would be interesting to learn a little bit more about what Uppverse is supposed to be. Embarassed
I'd love to see info from Uppverse added to build_info.h.
At this time it stores only revision info from SVN.
I'm personally not using SVN. Rolling Eyes


Regards,
Novo
Re: Uppiverse [message #55570 is a reply to message #55543] Sun, 22 November 2020 14:25 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 12954
Registered: November 2005
Ultimate Member
Novo wrote on Fri, 20 November 2020 19:07
It would be interesting to learn a little bit more about what Uppverse is supposed to be. Embarassed
I'd love to see info from Uppverse added to build_info.h.
At this time it stores only revision info from SVN.
I'm personally not using SVN. Rolling Eyes


Well, what information from git would you want? branch? hash?

Mirek
Re: Uppiverse [message #55573 is a reply to message #55570] Sun, 22 November 2020 18:12 Go to previous messageGo to next message
Novo is currently offline  Novo
Messages: 1098
Registered: December 2006
Senior Contributor
mirek 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.


Regards,
Novo
Re: Uppiverse [message #55574 is a reply to message #55573] Sun, 22 November 2020 18:27 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 12954
Registered: November 2005
Ultimate Member
Novo wrote on Sun, 22 November 2020 18:12
mirek 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?
Re: Uppiverse [message #55575 is a reply to message #55574] Sun, 22 November 2020 19:07 Go to previous message
Novo is currently offline  Novo
Messages: 1098
Registered: December 2006
Senior Contributor
mirek wrote on Sun, 22 November 2020 12:27
Novo wrote on Sun, 22 November 2020 18:12
mirek 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
Previous Topic: Uppiverse2
Next Topic: Uppiverse
Goto Forum:
  


Current Time: Sun Nov 29 00:23:42 CET 2020

Total time taken to generate the page: 0.00998 seconds