Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
AutoVersioning Plugin
riban:
I also suffer from the problem described where the Ubuntu style date of 8.08 gives a compile error of "digit exceeds base". If I recompile immediately afterwards, the error does not occur. This is using gcc 3.4.5 (mingw-vista special) on winxp inside CodeBlocks 8.02. The problem does seem to have started in August. It is as if the compiler sees this as an ocatal value hence a vaule of 8 is too high (0 - 7). It is very odd that this error occurs only the first time after each edit. Second compile is always okay.
Further investigation show it is windres that is throwing up the error. I haven't yet found how to deal with this. It seems that including version.h in resources.rc upsets windres when there is a number defined with a leading 0 which I guess windres is interpreting as an octal number. I am currently trying to remove the Ubuntu style stuff from the plugin as I don't need it anyway.
JGM:
Thanks!
I will change the code to generate the declaration as a string instead of a numeric value.
That should fix it i think.
MaxLondon:
Hi,
AutoVersioning is a really useful plugin for me. So, thanks for having developed it :)
How difficult would it be to include Preprocessor #define's of the values, especially of the version and build numbers and status?
e.g.:
#define DEF_MAJOR "1"
#define DEF_MINOR "2"
#define DEF_BUILD "3"
#define DEF_REVISION "4"
#define DEF_BUILDS_COUNT "5"
#define DEF_STATUS "Beta"
#define DEF_STATUS_SHORT "b"
It would be also nice to have the date as preprocessor defines:
#define DEF_DATE "09"
#define DEF_MONTH "08"
#define DEF_YEAR "2008"
Well that's basically all of the other values, just specified as preprocessor defines :).
For some values it would also be nice, to have them defined as numbers instead of strings.
For me these defines would be really helpful, and it shouldn't really hurt anyone.
So, let me know what you think.
killerbot:
that was really done on purpose.
Remember pp-defines are kind of bad. The circumvent the entire type system of C++.
The const values are really much better ;-)
MaxLondon:
I'm aware of the improved type checking, however there are a number of things I can't do with const values, like conditional compiling and other compile time stuff like string concatenation, etc. Also anything which goes into an .rc file.
For me it would be really helpful to have these defines.
Maybe it's possible to NOT create them by default, unless some config option is enabled,
Any chance?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version