Integration of Tortoise within Code::Blocks

[mariocup]

Hi,

I think it would be nice if Code::Blocks has another tab for browsing within the filesystem like explore. Perhaps this view could be used to integrate support for TortoiseSVN/CVS.
Some time ago I have seen that there is eclipse plugin using tortoise.
http://www.tabaquismo.freehosting.net/ignacio/eclipse/tortoise-svn/subversion.html

As tortoise is a wxWidget application perhaps the integration is less work than adding a svn or cvs plugin to Code::Blocks.

What do you think about that.

Bye,

Mario

[mandrav]

As tortoise is a wxWidget application perhaps the integration is less work than adding a svn or cvs plugin to Code::Blocks.

What do you think about that.

I think that you 're a windows user...

[mariocup]

Hi mandrav,

I develop under windows and linux. I like Tortoise under windows because it is easy to use, but it is not available for linux :cry: I don't know if it possible to port tortoise to linux.
As far as I now, there are different SVN clients for windows and linux:
esvn (qt), rapidsvn (wxwidget) but there will be no way to integrate them in a browser or Code::Blocks.
Under linux there are some kio_svn integration (like kdevelop) but that will not work under windows.

I think the integration of tortoise would be easier, so perhaps a lot of windows user could work with that great plugin together with Code::Blocks.

You are right mandrav that Code::Blocks is a cross platform IDE, so the features should be available for windows and linux.

Bye,

Mario

[mandrav]

You are right mandrav that Code::Blocks is a cross platform IDE, so the features should be available for windows and linux.

That was exactly my point.
You (or anyone else) are very welcome to write and provide a tortoisesvn-based Code::Blocks plugin for other windows users to enjoy. But we cannot do that because it will not be a cross-platform solution.
When we start work on such a plugin rest assured it will be cross-platform (without using tortoisesvn of course). But it's not at the top of our priorities for now.

[MortenMacFly]

IMHO there is a TortoiseSVN plugin for windows already. At least for some obscure reason I have a TortoiseSVN menu originating from a plugin I grabbed out of the depth of the forum ages back. Try a search in the forum, but I have no idea wheter:
- it's still working (I'm not using it)
- it's still supported / developed / maintained...
With regards, Morten.

[mariocup]

Thanks,

I have downloaded the file and will try to the plugin work for TortoiseSVN and TortoiseCVS.
But if I built the plugin I have the same problem as build Codeblocks from sources under windows.
Codeblocks (nightly builds) is linked against wxmsw26u_gcc_cb.dll.
If I build codeblocks from sources it is linked (WX_SUFFIX=u) against wxmsw26u_gcc_custom.dll and the plugins are not loaded correctly. If I modify WX_SUFFIX=u_gcc_cb then I get
C:/Programme/wxWidgets-2.6.3/include/wx/platform.h:190:22: wx/setup.h: No such file or directory
What I am doing wrong. Thanks.

Bye,

Mario

[Jan van den Borst]

Some time back I wrote a CBTortoiseSVN plugin! I'll attach it.

Jan

[attachment deleted by admin]

[MortenMacFly]

Some time back I wrote a CBTortoiseSVN plugin! I'll attach it.

That was the one I meant. Thanks, Jan. BTW: If I recall correctly there were also some modifications done by pecan in addition... but I'm not sure about that....
With regards, Morten.

[Biplab]

If I build codeblocks from sources it is linked (WX_SUFFIX=u) against wxmsw26u_gcc_custom.dll and the plugins are not loaded correctly. If

Open config.gcc file in <wx>/build/msw folder. Change the following line

Code

VENDOR = custom

To

Code

VENDOR = cb

And recompile the wx. Now you'll get wxmsw26u_gcc_cb.dll file.

[mandrav]

Open config.gcc file in <wx>/build/msw folder. Change the following line

Code

VENDOR = custom

To

Code

VENDOR = cb

And recompile the wx. Now you'll get wxmsw26u_gcc_cb.dll file.

@all:

!!! NEVER EVER DO THAT !!!

The vendor suffix is there for a reason. Specifically, the "cb" suffix tells us that this dll was built by us and we can safely assume it is built the way we want it.
If you do that and something doesn't work, don't come here for help. You 've been warned.

[Biplab]

@all:

!!! NEVER EVER DO THAT !!!

The vendor suffix is there for a reason.

Yiannis is correct. The method I've shown is just to fix your problem.

But as he has mentioned, we'll not provide any support.

Otherwise, download the official wx Runtime provided by C::B team and then create an import library. In this case also No support is guaranteed.

Or just use the wxmsw26u_gcc_custom.dll file, it will be same.

[mariocup]

Mi mandrav, Hi Biplab,

the main reason for this question is the following problem. If I build codeblocks and all plugins from sources and run update.bat then codeblocks is linked against custom.dll. Starting codeblocks and loading plugins works fine.
But if I compile e.g. ThreadSearch Plugin or CBTortoiseSVN and link agains custom.dll and then load it in Code::Blocks then I get an error, that these plugins could not be loaded correctly. If I compile e.g. the ThreadSearch Plugin and link it against *u_gcc_cb.dll and copy the plugin to the binaries which I get from the nightly build the plugin works. I do not know what is the reason?
Any idea.

Thx,

Mario

[Pecan]

   //-- Full Compile Logging --
   "Settings" -> "Compiler and Debugger"
   "Global Compiler Setting"
   "Other Settings"
   "compiler logging:" set to "Full Command Line"

Post the results of the compile/link from the messages notebook.

[dje]

But if I compile e.g. ThreadSearch Plugin or CBTortoiseSVN and link agains custom.dll and then load it in Code::Blocks then I get an error, that these plugins could not be loaded correctly.

To bypass the problem with ThreadSearch plugin, I link with .a libs to work with my development environment and directly with dlls to work with a nightly build.

Dje

[mariocup]

Hi codeblocks team,

yesterday I rebuilt wx with VENDOR=custom. Then I made a clean and rebuilt of codeblocks and all plugins, and now everything works fine.
All is linked against custom.dll and I get no error if I start codeblocks. I do not know what was exactly the inconsistency on my system?
Thanks for your help.

Bye,

Mario