Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Autoversioning scheme

<< < (2/3) > >>

scarphin:

--- Quote from: eanon on September 11, 2012, 08:46:46 pm ---And I see autoversioning generates version number like this : MAJOR.MINOR.BUILD.REVISION

--- End quote ---

It doesn't work like this on my machine. You must be doing something wrong.

Btw what happens if the maintainer of the some plugin doesn't maintain it anymore? I'm asking this because once I've submitted a patch to add extra functionality to autoversioning plugin and think it's been long lost in the patch tracker.

oBFusCATed:
Your patch is not lost but, there is no person to commit it.
I don't know the code, neither do use the plugin, so I can't review the patch.

p.s. probably you can try to contact the maintainer JGM or try with killerbot, both are listed as people who have worked on the code.

eranon:

--- Quote from: scarphin on September 12, 2012, 10:27:05 pm ---
--- Quote from: eanon on September 11, 2012, 08:46:46 pm ---And I see autoversioning generates version number like this : MAJOR.MINOR.BUILD.REVISION

--- End quote ---

It doesn't work like this on my machine. You must be doing something wrong.
--- End quote ---

I've just used the autoversioning plugin delivered in C::B package w/o any change in code and testing with the default options. Here is the useful part of the version.h generated by the plugin :


--- Code: --- //Standard Version Type
static const long VERSION__MAJOR = 1;
static const long VERSION__MINOR = 0;
static const long VERSION__BUILD = 2;
static const long VERSION__REVISION = 7;

//Miscellaneous Version Types
static const long VERSION__BUILDS_COUNT = 1;
#define VERSION__RC_FILEVERSION 1,0,2,7
#define VERSION__RC_FILEVERSION_STRING "1, 0, 2, 7\0"
static const char VERSION__FULLVERSION_STRING[] = "1.0.2.7";
--- End code ---

As you can see in VERSION__FULLVERSION_STRING, the parts are sorted with VERSION__REVISION at the end. Well, however, don't worry, I've decided to not use-it.

JGM:

--- Quote from: eanon on September 14, 2012, 01:53:46 am ---
--- Quote from: scarphin on September 12, 2012, 10:27:05 pm ---
--- Quote from: eanon on September 11, 2012, 08:46:46 pm ---And I see autoversioning generates version number like this : MAJOR.MINOR.BUILD.REVISION

--- End quote ---

It doesn't work like this on my machine. You must be doing something wrong.
--- End quote ---

I've just used the autoversioning plugin delivered in C::B package w/o any change in code and testing with the default options. Here is the useful part of the version.h generated by the plugin :


--- Code: --- //Standard Version Type
static const long VERSION__MAJOR = 1;
static const long VERSION__MINOR = 0;
static const long VERSION__BUILD = 2;
static const long VERSION__REVISION = 7;

//Miscellaneous Version Types
static const long VERSION__BUILDS_COUNT = 1;
#define VERSION__RC_FILEVERSION 1,0,2,7
#define VERSION__RC_FILEVERSION_STRING "1, 0, 2, 7\0"
static const char VERSION__FULLVERSION_STRING[] = "1.0.2.7";
--- End code ---

As you can see in VERSION__FULLVERSION_STRING, the parts are sorted with VERSION__REVISION at the end. Well, however, don't worry, I've decided to not use-it.

--- End quote ---

Hi,

I haven't been much active using c++, but maybe creating your own string could work

(if on c++)

std::string mystring;
mystring << VERSION__MAJOR << "." << etc...;

scarphin:
JGM: Any chance for you to review the patch below?

Patch ID: 003210
http://developer.berlios.de/patch/index.php?func=detailpatch&patch_id=3210&group_id=5358

Basically it disables auto incrementing the version number if the build num is given zero.

Navigation

[0] Message Index

[#] Next page

[*] Previous page