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

AutoVersioning Plugin

<< < (38/41) > >>

stahta01:

--- Quote from: Freem on October 28, 2009, 08:10:05 pm ---
--- Quote from: ajaywazir on September 03, 2009, 06:19:21 pm ---Hi
Need some help
I have SVN 1.5.5 and TortoiseSVN 1.6.5
I have checked out some code using TortoiseSVN 1.6.5;
SVN.exe is in path
I cannot use svn revision in the version file.
The config dialog always gives me error, svn configuration files not found.
whereas all .svn files and folders are there.

Ajay

--- End quote ---

Hi

I'm sorry to have to ask for help with this useful plug-in, but I have the same problem.
I searched in the C::B documentation, search on google, but I didn't find any information.
I think I really don't understand what I have to put in the field "current SVN directory".
I have tried to use the bin directory of subversion, the global directory of subversion, the directory of the project for which I want to try this feature, and the .svn directory in the project's directory, but this is all the time the same error... "Svn configuration files not found. Verify the Autoversioning svn directory."



--- End quote ---

This is just a guess.

svn command must be in the system path or in the compiler additional exe path

The "current SVN directory" should be the top SVN directory your SVN project is checked out to. This folder/directory must contain the .svn folder.

Note: This is a problem "I have SVN 1.5.5 and TortoiseSVN 1.6.5" the svn command must be the same major/minor version as the svn project folder. Note, a higher version might work. An SVN 1.6.0 should work with TortoiseSVN 1.6.5; but not SVN 1.5.5. Format of version number major.minor.?? What the ?? is called varies from project to project.

Tim S.
 

Freem:
Thanks a lot, it work great, now.

I'm didn't think to upload brain to the last version, it seem :)

And thanks for this useful plugin, that improve a great IDE.

JGM:

--- Quote from: MortenMacFly on October 27, 2009, 03:49:34 pm ---
--- Quote from: JGM on October 09, 2009, 11:22:53 am ---AutoVersioning 1.3

--- End quote ---
Applied in trunk after testing... Thanks! :-)

--- End quote ---

yay! thanks for the commit and thanks to everyone that pointed the plugin errors (bugs)!  :D Keep the codeblocks growing!

polygon7:
Hi,
I have one suggestion, this variables:

--- Code: --- //Standard Version Type
static const long AV_MAJOR = 1;
static const long AV_MINOR = 0;
static const long AV_BUILD = 2;
static const long AV_REVISION = 11;

--- End code ---

could be size_t / unsigned int type because usually you don't need negative version number,
and usually you don't need version number grater than max value of unsigned int (I know it doesn't
matter on 32bit, where unsigned long == unsigned int == 4 294 967 295, but on other architectures,
ex. 16bit, it makes a difference).

AndyJ:
Hello,

I have a request. Where strings are currently generated as:

   static const char DATE[] = "24";

would it be possible to (optionally?) generate them as:

   #define DATE_DEFINE "24"
   static const char DATE[] = DATE_DEFINE;

or something similar as this would be more flexible for some applications (creating a custom string in yet another #define for instance). Obviously the appropriate prefix should be applied to both names.

Thanks for a great plugin,

Andy

Navigation

[0] Message Index

[#] Next page

[*] Previous page