AutoVersioning Plugin

[JaredR26]

If no one is able to help me, do you think you could provide a pre-compiled windows copy JGM?

[JGM]

If no one is able to help me, do you think you could provide a pre-compiled windows copy JGM?

Hi sorry for the delay, lets try to compile that  !

I advice you to to create a folder structure like the one explained in the wiki for convenience "codeblocks-head/trunk/" and inside that folder the original src folder, not some src/src thats confusing :shock:

I tried both the AutoVersioning and the autoversioning-contrib files, both give the same error.

The AutoVersioning.7z is for generating the autoversioning.cbplugin and the autoversioning-contrib.7z are the files mandatory to the plugins/contrib/autoversioning

my cb global variable points to C:\Installed\CodeBlocks\src

there it will not found the include directory. use the structure recommended in the wiki, the src/src is redundant

, but I tried pointing it to C:\Installed\CodeBlocks\src\src

It should work if you point to that directory :?

and pointing the include variable to C:\Installed\CodeBlocks\src\src\include

that should not be necessary

Well,
first use the autoversioning-contrib.7z and decompress it to the correct plugin/contrib/autoversioning

open the ContribPlugins.workspace and click File->Open and add the plugin/contrib/autoversioning/autoversioning.cbp and hit save workspace

set the $(#CB) variable to codeblocksdirecotry/src/ where the include directory resides.

Hit compile!

You can also open the project file directly from the plugins/contrib/autoversioning and compile it. then run the bat file to produce the correct output.

Thats what I do and I don't have any errors

Hope you can compile it!

[JaredR26]

Got it.

[JGM]

Added the plugin on the Announcement for plugins/patches WIKI I think is stable enough.

[JGM]

New version available with some code changes and now using the cbEVT_COMPILER_STARTED. More details and download on first post.

[MortenMacFly]

More details and download on first post.

Thanks for that - applied that to one of my own projects and it worked quite well so far.
BTW: Don't you wanna put this under SVN version control (e.g. at BerliOS like CBILplugin or cbMakeGen) maybe?! This makes it easier to update...
With regards, Morten.

[JGM]

Thanks for that - applied that to one of my own projects and it worked quite well so far.

Thanks to you and all the developers working to make codeblocks the best tool and programmers friend. Is good to know plugin is working well.

BTW: Don't you wanna put this under SVN version control.

It's true! I just thought that it was a small project without a big need to make that, but well, I will do it. I'm not familiar with berlios, I prefer sourceforge, but I think that like codeblocks is there I can associate the plugin with codeblocks.

Does I'm correct?  :?:

[MortenMacFly]

but I think that like codeblocks is there I can associate the plugin with codeblocks.
Does I'm correct?  :?:

More or less - you can reference the C::B project. My intention was only to have all under one place. Thus is you search through BerliOS for C::B you will get the most important parts. Of course other repros are OK, too (like some plugins are also under google code)... Surely completely up to you - what ever is comfortable enough.
With regards, Morten.

[JGM]

Surely completely up to you - what ever is comfortable enough.

Well, registered an account on berlios, created the new project AutoVersioning, and still waiting for the confirmation email for approve. More than 24 hours has passed. I guess they are really busy with a lot of work.

[JGM]

I'm still waiting for the confirmation email of the project AutoVersioning at berlios without a response. I'm getting frustrated.

Does this means they doesn't accept it?

[dmoore]

from memory I think it took well over a week for my confirmation to come through... berlios are pretty frustrating. if you're located in europe it probably makes sense to use them, but in addition to the long project confirmation delay and generally patchy services you get to enjoy:
* lack of documentation (at least english)
* slow connection from the US
* crappy admin controls (excruciating to add file releases, especially with the clumsy anonymous ftp)
* incorrectly signed security certificates

fortunately the Berlios SVN server has been rock solid every time i've had to commit. if that doesn't change i'll probably to continue to use them...

[JGM]

The autoversioning plugin was approved at berlios

Here is the hyperlink https://developer.berlios.de/projects/autoversioning/

Just uploaded the file and screenshots and edited the project info, now I have to set the svn, but I have to wait 6 hours. 

If any body wants to join the project for development just send me a private message.

[JGM]

Auto Versioning new Feature:

Finally I took the time to implement the changes log generator. 

This is some Output example of the change log generator:

Code Select Expand


03 September 2007
   released version 0.7.34 of AutoVersioning-Linux

     Change log:
        -Fixed: pointer declaration
        -Bug: blah blah

02 September 2007
   released version 0.7.32 of AutoVersioning-Linux

     Change log:
        -Documented some areas of the code
        -Reorganized the code for readability

01 September 2007
   released version 0.7.30 of AutoVersioning-Linux

     Change log:
        -Edited the change log window
        -If the change log windows is leave blank no changes.txt is modified



Check the first post for download and screenshots (I have to update the sources on berlios now :?)

[MortenMacFly]

(I have to update the sources on berlios now :?)

In case you did this: I have no more access to the repository. Neither by any client software nor via the BerliOS (anonymous) interface. The error is 403 - access forbidden. I guess you misconfigured something, maybe...?!

[Kalma]

Hello, It seems to me that this is usefull plugin for that nice IDE,
but I can't find any link to the sources or binaries, so could smeone give
me a link to the soures or binaries?