Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
AutoVersioning Plugin
JGM:
--- Quote from: kisoft on September 28, 2007, 02:29:13 pm ---C::B crushed on uninstall you plugin. :(
Somebody may confirm it?
--- End quote ---
Actually it only crashes on windows if you don't disable it before uninstalling it. I have tested it on ubuntu and it could be uninstalled without disabling it first. So it's may be a windows thing.
JGM:
Uploaded new binaries to berlios of revision 9, v0.9.1
Now variables are declared const to avoid warnings
Jeisson:
Hi JGM!
I have another question. Programs typically use 3 first values for displaying version: major.minor.buildNumber. Last one is autoincremented each time I press F9, so, my About dialog always shows a big unrealistic third number, something like 0.1.146.
I would like to increment them manually when I am releasing a public version (I can do it setting the "Commit changes" flag); but I want the plugin always updates dates and the Build Count, because they are useful in developing stage.
Would be it possible or am I configurating something wrong?
Thanks a lot in advance.
JGM:
--- Quote from: Jeisson on November 01, 2007, 01:56:18 am ---Hi JGM!
I have another question. Programs typically use 3 first values for displaying version: major.minor.buildNumber. Last one is autoincremented each time I press F9, so, my About dialog always shows a big unrealistic third number, something like 0.1.146.
--- End quote ---
Hi, good to read from you. :)
Well the Build Number is supposed to increment every time you modify a file in the project, on the other hand Build count is the value that always increment before building/running (F9). So MAJOR, MINOR and BUILD are the values to use in your case.
--- Quote from: Jeisson on November 01, 2007, 01:56:18 am ---I would like to increment them manually when I am releasing a public version (I can do it setting the "Commit changes" flag); but I want the plugin always updates dates and the Build Count, because they are useful in developing stage.
Would be it possible or am I configurating something wrong?
Thanks a lot in advance.
--- End quote ---
That should be the default behavior. When updating version.h the dates are always updated to the actual, but the build count is only updated before compiling or running. It's a value supposed to indicate how many times we compile or run our program changed or unchanged, while Build Number increments with commit changes or auto only when changes on source are found.
You could test editing the scheme to set a build number maximum for example 100. Also try reading the documentation that I wrote on the C::B wiki, is on my signature, there is a short description of the values. Also posting your version.ini would be of help :)
Any other questions, feel free to post :D
JGM:
New update of the plugin:
[Changes 1.0]
- Now the plugin uses the project file to store settings instead of the ini file, thanks to killerbot.
- You can choose where to store the version.h header as change the filename.
- You can choose where to store the changeslog as change the filename.
- The settings tab option AutoIncrement has been changed to Do Autoincrement, because of some different behaviour.
- Also the Commit Changes menu was renamed to Increment Version.
- Now the version.h file is parsed to obtain the version values.
- You will have to increment version before closing the project if changes, since it doesn't store the modified flag as a configuration anymore.
- The build history is now part of the header file.
- Many other internal changes thanks to killerbot.
check the first post for downloads or my signature.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version