News:

When registered with our forums, feel free to send a "here I am" post here to differ human beings from SPAM bots.

Main Menu

SVN plugin

Started by thomas, June 07, 2005, 07:38:24 PM

Previous topic - Next topic
Print
Go Down Pages 1 2 3 4 5 6 7
User actions

RJP Computing

#75
December 05, 2005, 05:09:01 PM
Yup I am using there build of C::B. Thanks for trying.

Is there any way to explain, posibly a tutorial, about what needs to be compiled and what source is need to help the developement of this plugin along? I have the source for the SVN plugin and the SDK from the C::B website but I get all kinds of errors when compiling the plugin. I think the version of the SDK for C::B is old and that might be the problem. How do I update the SDK so I can work with plugins using the builds that are beyond the current RC?

I know I have half the information. Just enough to be a pain. But I would love to help out once I get up to speed.
- Ryan

Ubuntu/WinXP, AMD Athlon 64 3000+, 1000MB RAM, AC 97 Audio, ATI Radeon 9600XT 256MB

Urxae

#76
December 05, 2005, 05:44:45 PM
Basically, the SDK must match the C::B binaries. It'd probably be best if you could get Ceniza and/or Therion to also provide the SDK corresponding to their binaries (as a separate download).

takeshimiya

#77
December 05, 2005, 06:05:49 PM Last Edit: December 05, 2005, 06:07:36 PM by Takeshi Miya
No, it would be better if the SVN plugin would be in the SVN repository don't you think? lol :lol:

Is there any reason of why it's not on contrib plugins?

thomas

#78
December 05, 2005, 06:07:13 PM
The easiest way to update the SDK is to copy over the headers from the Code::Blocks sources. Note that you need compatible link libraries for wxmsw26.dll and codeblocks.dll, too (matching the exact build that the plugin is to be used with). If you have compiled Code::Blocks yourself, just copy those files too (or set the linker's path). If you still use RC2, then you can download the matching SDK from codeblocks.org. If you use an unofficial build, then... I don't know -- if the build includes the libs, then all is fine, if it does not, then you have a problem.

However, working on the plugin now may not make an awful lot of sense, because your precious work will be worthless after the next release (which is finally being worked on).

I had stopped working on the plugin about 3 weeks before RC2 came out and (despite having planned otherwise) only taken up work again on Saturday.
In the mean time, a lot of significant things in Code::Blocks have changed, and cvs is no longer on the feature list, so an almost complete rewrite reusing some of the existing components seems easier than working on with the existing sources.
Apart from that, significant changes to UI, behaviour, and settings are being made (which are neither compatible with the old versions, nor with Urxae's modifications).
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

thomas

#79
December 05, 2005, 06:08:22 PM
Quote from: Takeshi Miya on December 05, 2005, 06:05:49 PMIs there any reason of why it's not on contrib plugins?

There is a reason: it is rubbish.

As soon as the next release compiles, it will be included via svn:external.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

killerbot

#80
December 05, 2005, 07:06:08 PM
I would not throw away the cvs stuff. CB talking for other projects with cvs servers reamains an inrteresting functionality.
Just like I created a plug-in for ClearCase.

thomas

#81
December 06, 2005, 12:24:56 AM
Quote from: MortenMacFly on November 26, 2005, 07:40:40 PMI have TortoiseSVN installed but the plugin does not detect it. I can setup the path to CVS, SVN - is there a reason why not for TortoiseSVN?
I just found out why - by mere coincidence (reinstalled TortoiseSVN).
TortoiseSVN really does no longer come with a svn executable! Obviously, the plugin cannot find it, if it is not there.
So for the future, users will have to install subversion, and optionally TortoiseSVN, the latter alone is not enough.

Quote from: killerbot on December 05, 2005, 07:06:08 PMI would not throw away the cvs stuff. CB talking for other projects with cvs servers reamains an inrteresting functionality.
Just like I created a plug-in for ClearCase.
That's not what I said. The primary objective is to get svn to work. Incorporating CVS at the same time makes the code complicated and unmanageable, and stalls the development of the primary objective. Therefore, cvs is taken out of that module.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

killerbot

#82
December 06, 2005, 07:45:27 AM Last Edit: December 06, 2005, 07:48:11 AM by killerbot
I totally agree, keep things clean and simple :

- plug-in for svn
- plug-in for cvs
- plug-in clearcase
- plug-in for perforce (I'm gonna start working on it)


Lieven

cborders

#83
January 09, 2006, 11:03:03 PM
I saw the issue regarding this plugin on the download page so I installed svn, but now I can't seem to find a link to download the plugin, where can I get it?

MortenMacFly

#84
January 09, 2006, 11:10:58 PM
Quote from: cborders on January 09, 2006, 11:03:03 PM
[...] where can I get it?
Via SVN from: http://developer.berlios.de/projects/cb-svn/. Look through the forum for a compatibility patch to run this version with the current SVN-HEAD of Code::Blocks.
Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

takeshimiya

#85
January 10, 2006, 12:47:04 AM
Mental note for when the SVN plugin get's back to life: Make it work with both SVN and TortoiseSVN.
As TortoiseSVN doesn't come anymore with svn.exe, but still it let's you do almost all (all?) by the command line.
It will be a pain to tell users that they need to download another 5mb more for making the C::B SVN plugin work.

thomas

#86
January 10, 2006, 12:50:27 AM
They will have to, though, because the plugin will not work with TortoiseSVN.
What it will do in respect to TortoiseSVN is, it will offer some additional functionality. The standard functionality runs through svn.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

jsiebert

#87
June 14, 2006, 01:21:05 PM
Hi there,

are there any news on the svn plugin? Is it currently worked on?

Greetings

Jens

sethjackson

#88
June 14, 2006, 02:02:22 PM
Quote from: jsiebert on June 14, 2006, 01:21:05 PM
Hi there,

are there any news on the svn plugin? Is it currently worked on?

Greetings

Jens

Hi. This will probably answer some of your questions. :)

http://forums.next.codeblocks.org/index.php?topic=3122.0

(Specifically thomas's first post)

jsiebert

#89
June 14, 2006, 02:45:24 PM
Hi,

thanks for the info! Next time I put on my glasses before searching the forum ;-)

Greetings

Jens
Print
Go Up Pages 1 2 3 4 5 6 7
User actions