Well I found a solution to this was to place the svn.zip file in the '<CodeBlocks Install>\share\CodeBlocks' directory.
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.
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.
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.
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.
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.