Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
SVN plugin
RJP Computing:
Has there been any developement on this?
I tried the one from the website and it doesn't seem to work. Every time I try to add a project to a repository it closes C::B without any message at all. If I try to go to the "Configure Plugins" it crashes C::B. I use Subversion a lot and this is going to be a great plugin. Please let me know if there is anything I can dso to help.
thomas:
Svn support actually works quite reliably, I work with it all day, cvs support is (still) a bit awkward, that's going to be fixed soon though.
There is a bug in the version that is released on the BerliOS site which indeed causes a crash if you do not have svn properly installed, or if the plugin cannot find it - that bug has been fixed in the repository. The version coming with RC2 will not have that bug any more, and as soon as I can be bothered to clean up a few things, a better version will be released on the Berlios site, too. Few days patience please, have a busy week.
RJP Computing:
--- Quote from: RJP Computing on October 16, 2005, 11:58:17 pm ---If I try to go to the "Configure Plugins" it crashes C::B.
--- End quote ---
Well I found a solution to this was to place the svn.zip file in the '<CodeBlocks Install>\share\CodeBlocks' directory.
I also noticed if I opened a project that was currently under svn and did an update to the "HEAD" revision it deleted the file and then nothing. I don't know if this matters, but I am doing this on a flash drive. Sometimes things like that matter. I am going to try from a local disc later and I will get back to you.
Can you make it so that the svn.exe can be in the CodeBlocks install directory. I would like to make a custom installer and just include the needed files. It would be a great help.
I am excited to see the new version. :lol:
Thanks!
thomas:
--- Quote from: RJP Computing on October 17, 2005, 10:27:48 pm ---Well I found a solution to this was to place the svn.zip file in the '<CodeBlocks Install>\share\CodeBlocks' directory.
--- End quote ---
Ah, that of course would be the case. Not that this is an excuse, but that is the case with any plugin coming with Code::Blocks (the compiler and debugger are smart enough to disable the compiler menu, but you can still fool the compiler by using the project manager). Added a check when the plugin is loaded.
--- Quote from: RJP Computing on October 17, 2005, 10:27:48 pm ---I also noticed if I opened a project that was currently under svn and did an update to the "HEAD" revision it deleted the file and then nothing.
--- End quote ---
There is no reason for that which is obvious to me. The plugin does not touch your project files, neither does it ever delete one.
If you select "Update to HEAD", then it will change directory to the working copy, set a few necessary environment variables (SVN_SSH, for example), and invoke svn update -r head.
--- Quote from: RJP Computing on October 17, 2005, 10:27:48 pm ---Can you make it so that the svn.exe can be in the CodeBlocks install directory. I would like to make a custom installer and just include the needed files. It would be a great help.
--- End quote ---
In the upcoming release, the value of HKEY_CURRENT_USER\Software\Code::Blocks\Code::Blocks v1.0\app_path is one of the search paths for the svn and cvs executables under Windows. Under Linux, executables are searched in /usr/bin, /usr/local/bin, /opt/bin, and /bin.
If all fails, the plugin simply uses the tool's name and relies on the PATH variable on both platforms. So if svn is in your PATH, then it should always work.
Urxae:
--- Quote from: thomas on October 18, 2005, 11:09:03 am ---
--- Quote from: RJP Computing on October 17, 2005, 10:27:48 pm ---I also noticed if I opened a project that was currently under svn and did an update to the "HEAD" revision it deleted the file and then nothing.
--- End quote ---
There is no reason for that which is obvious to me. The plugin does not touch your project files, neither does it ever delete one.
If you select "Update to HEAD", then it will change directory to the working copy, set a few necessary environment variables (SVN_SSH, for example), and invoke svn update -r head.
--- End quote ---
Well, the obvious reason that might happen would be that the file in question was deleted in the repository, so svn update removed it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version