Author Topic: SVNInside : development of another SVN plugin for CodeBlocks  (Read 141332 times)

Offline orel

  • Multiple posting newcomer
  • *
  • Posts: 96
Re: SVNInside : development of another SVN plugin for CodeBlocks
« Reply #105 on: January 20, 2008, 03:23:58 am »
Patch needed under Windows XP when not using Pre-Compiled Headers (PCH)

Tim S

Just applied !!
Thank you very much for that new pch patch, i have to be more careful with that in next commits.

Best regards

Orl
windows XP SP2
mingw gcc 3.4.5
svn Code::Blocks and M$ Visual Studio 2005 and .NET to eat!! SVNInside plugin :http://forums.codeblocks.org/index.php/topic,7063.0.html

Offline branleb

  • Multiple posting newcomer
  • *
  • Posts: 16
Re: SVNInside : development of another SVN plugin for CodeBlocks
« Reply #106 on: February 29, 2008, 12:51:23 pm »
I tried to compile the Plugin SVN Rev. 69, but first I had problems with some missing librearies:
wxScintilla and wxPropGrid.
After I installed them (wxCode[wxScintilla] CVS Rev.  723 & wxPropGrid SVN Rev. 615)
I got other compile errors.

I am using CB SVN Rev. 4898

Here is the build log. Can someone help me?
Code: [Select]
-------------- Build: release in SVNInside - Linux ---------------

Compiling: src/commands/svniAdd.cpp
Compiling: src/commands/svniCommand.cpp
Compiling: src/commands/svniCommit.cpp
Compiling: src/commands/svniDiff.cpp
Compiling: src/commands/svniInfo.cpp
Compiling: src/commands/svniLock.cpp
Compiling: src/commands/svniStatus.cpp
Compiling: src/commands/svniUpdate.cpp
WARNING: Can't read file's timestamp: /home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniConfigDlg.cpp
Compiling: src/dialogs/svniFileSelectDlg.cpp
Compiling: src/dialogs/svniLogger.cpp
Compiling: src/dialogs/svniTabPnl.cpp
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp: In constructor »svniTabPnl::svniTabPnl(wxWindow*)«:
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:56: Warnung: »AppendCategory« ist veraltet (deklariert bei /usr/local/include/wx/propgrid/propgrid.h:3864)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:57: Fehler: keine passende Funktion für Aufruf von »wxPropertyGrid::Append(wxStringProperty)«
/usr/local/include/wx/propgrid/propgrid.h:3861: Anmerkung: Kandidaten sind: wxPGProperty* wxPropertyContainerMethods::Append(wxPGProperty*)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:58: Fehler: keine passende Funktion für Aufruf von »wxPropertyGrid::Append(wxStringProperty)«
/usr/local/include/wx/propgrid/propgrid.h:3861: Anmerkung: Kandidaten sind: wxPGProperty* wxPropertyContainerMethods::Append(wxPGProperty*)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:59: Fehler: keine passende Funktion für Aufruf von »wxPropertyGrid::Append(wxStringProperty)«
/usr/local/include/wx/propgrid/propgrid.h:3861: Anmerkung: Kandidaten sind: wxPGProperty* wxPropertyContainerMethods::Append(wxPGProperty*)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:60: Fehler: keine passende Funktion für Aufruf von »wxPropertyGrid::Append(wxStringProperty)«
/usr/local/include/wx/propgrid/propgrid.h:3861: Anmerkung: Kandidaten sind: wxPGProperty* wxPropertyContainerMethods::Append(wxPGProperty*)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:61: Fehler: Aufruf des überladenen »wxIntProperty(const wxChar*)« ist mehrdeutig
/usr/local/include/wx/propgrid/props.h:360: Anmerkung: Kandidaten sind: wxIntProperty::wxIntProperty(const wxString&, const wxString&, const wxLongLong&)
/usr/local/include/wx/propgrid/props.h:357: Anmerkung:                  wxIntProperty::wxIntProperty(const wxString&, const wxString&, long int)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:63: Warnung: »AppendCategory« ist veraltet (deklariert bei /usr/local/include/wx/propgrid/propgrid.h:3864)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:64: Fehler: keine passende Funktion für Aufruf von »wxPropertyGrid::Append(wxStringProperty)«
/usr/local/include/wx/propgrid/propgrid.h:3861: Anmerkung: Kandidaten sind: wxPGProperty* wxPropertyContainerMethods::Append(wxPGProperty*)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:65: Fehler: Aufruf des überladenen »wxIntProperty(const wxChar*)« ist mehrdeutig
/usr/local/include/wx/propgrid/props.h:360: Anmerkung: Kandidaten sind: wxIntProperty::wxIntProperty(const wxString&, const wxString&, const wxLongLong&)
/usr/local/include/wx/propgrid/props.h:357: Anmerkung:                  wxIntProperty::wxIntProperty(const wxString&, const wxString&, long int)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:66: Fehler: keine passende Funktion für Aufruf von »wxPropertyGrid::Append(wxStringProperty)«
/usr/local/include/wx/propgrid/propgrid.h:3861: Anmerkung: Kandidaten sind: wxPGProperty* wxPropertyContainerMethods::Append(wxPGProperty*)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:68: Warnung: »AppendCategory« ist veraltet (deklariert bei /usr/local/include/wx/propgrid/propgrid.h:3864)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:69: Fehler: keine passende Funktion für Aufruf von »wxPropertyGrid::Append(wxStringProperty)«
/usr/local/include/wx/propgrid/propgrid.h:3861: Anmerkung: Kandidaten sind: wxPGProperty* wxPropertyContainerMethods::Append(wxPGProperty*)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:70: Fehler: keine passende Funktion für Aufruf von »wxPropertyGrid::Append(wxStringProperty)«
/usr/local/include/wx/propgrid/propgrid.h:3861: Anmerkung: Kandidaten sind: wxPGProperty* wxPropertyContainerMethods::Append(wxPGProperty*)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:72: Warnung: »AppendCategory« ist veraltet (deklariert bei /usr/local/include/wx/propgrid/propgrid.h:3864)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:73: Fehler: keine passende Funktion für Aufruf von »wxPropertyGrid::Append(wxStringProperty)«
/usr/local/include/wx/propgrid/propgrid.h:3861: Anmerkung: Kandidaten sind: wxPGProperty* wxPropertyContainerMethods::Append(wxPGProperty*)
/home/shade/code/sources/svninside-svn/trunk/src/dialogs/svniTabPnl.cpp:74: Fehler: keine passende Funktion für Aufruf von »wxPropertyGrid::Append(wxStringProperty)«
/usr/local/include/wx/propgrid/propgrid.h:3861: Anmerkung: Kandidaten sind: wxPGProperty* wxPropertyContainerMethods::Append(wxPGProperty*)
Process terminated with status 1 (0 minutes, 18 seconds)
30 errors, 0 warnings
Don't hate the Hacker. Hate the Code!

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9496
Re: SVNInside : development of another SVN plugin for CodeBlocks
« Reply #107 on: February 29, 2008, 01:11:18 pm »
After I installed them (wxCode[wxScintilla] CVS Rev.  723 & wxPropGrid SVN Rev. 615)
[...]
Here is the build log. Can someone help me?
Please don't use any (wx) components other than the C::B SDK. Within the C::B sources you will find the propgrid version we are using as well as the wxscintilla version we are using. Your's are most likely not compatible.

If you want to develop for C::B / compile for C::B you should always use the C::B sources/SDK and wxWidgets (that's the only exception).

With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline Fasser

  • Single posting newcomer
  • *
  • Posts: 6
Re: SVNInside : development of another SVN plugin for CodeBlocks
« Reply #108 on: March 06, 2008, 01:33:20 pm »
Hi, I think this plugin is very interesting. Have you considered releasing a try-at-your-own-risk version, compiled against the new 8.02 C::B release? I'm sure many people will have a look at it then.

Also, as you took the command line approach to SVN, I think it shouldn't be too difficult to add suport to CVS as well (maybe others too!), so this plugin could evolve to be a general interface to version systems for C::B, at least covering the very basic functions. What do you think?

Thanks for your work!

Offline branleb

  • Multiple posting newcomer
  • *
  • Posts: 16
Re: SVNInside : development of another SVN plugin for CodeBlocks
« Reply #109 on: March 13, 2008, 10:02:33 pm »
thanks MortenMacFly.
I got the SVNInside Plugin compiled.
But now, I habe another Problem:
Codeblocks doesn't load the plugin with teh error message "missing symbols?"
So i looked with ld at the compiled .so
Code: [Select]
{-shade@bumbleblee-} => [~/code/sources/svninside-svn/trunk]
(21:53:50) ld libsvninside.so
ld: warning: cannot find entry symbol _start; not setting start address
libsvninside.so: undefined reference to `svniPrjConfigDlg::svniPrjConfigDlg(wxWindow*, svniProjectConfig*, bool, bool)'
libsvninside.so: undefined reference to `svniSettingsDlg::svniSettingsDlg(wxWindow*, svniPlugin*, svniConfig*)'
libsvninside.so: undefined reference to `vtable for svniPrjConfigDlg'
libsvninside.so: undefined reference to `svniSettingsDlg::SvnPathCorrect(wxString const&)'

Can anyone help me?
(ah, before i forget that: i had to "touch" src/dialogs/svniConfigDlg.cpp because g++ claimed about not beeing able to read its timestamp an so the linking process was canceled.)

Branleb
Don't hate the Hacker. Hate the Code!

Offline orel

  • Multiple posting newcomer
  • *
  • Posts: 96
Re: SVNInside : development of another SVN plugin for CodeBlocks
« Reply #110 on: March 14, 2008, 01:05:53 am »
Can anyone help me?
(ah, before i forget that: i had to "touch" src/dialogs/svniConfigDlg.cpp because g++ claimed about not beeing able to read its timestamp an so the linking process was canceled.)

Branleb

Your problem can be solved and has been solved, have you read the page 7 of this thread, here is the link ...!
http://forums.codeblocks.org/index.php/topic,7063.90.html

And for all the persons who are interested inmy plugin, sorry for this long time of silence without updates. I am very busy at work for he moment but this plugin is not at all over, i have a quite good version to commit. But i am waiting a bit in order to test more and provide you a working-version, not one for beta-testers only ;-)
windows XP SP2
mingw gcc 3.4.5
svn Code::Blocks and M$ Visual Studio 2005 and .NET to eat!! SVNInside plugin :http://forums.codeblocks.org/index.php/topic,7063.0.html

Offline branleb

  • Multiple posting newcomer
  • *
  • Posts: 16
Re: SVNInside : development of another SVN plugin for CodeBlocks
« Reply #111 on: March 14, 2008, 04:38:45 pm »
sorry, but i see no solution on page 7 of this thread.
or at least, noen worked for me.

But may you explain the part with "copy the source to C::B src dir/plugins/svninside" and "linux users have to modify post_build_step" ?

I am using linux, butthis didn't worked for me( the post build script worked only if I c&p'ed each line to the cmdline end executed it

Can you explain, what you meant?

regards,
Branleb
Don't hate the Hacker. Hate the Code!

Offline JGM

  • Lives here!
  • ****
  • Posts: 518
  • Got to practice :)
Re: SVNInside : development of another SVN plugin for CodeBlocks
« Reply #112 on: April 23, 2008, 06:12:27 pm »
Hey! any news about the plugin, does it's ready to be added to the codeblocks contrib repo?

Offline Alexis

  • Multiple posting newcomer
  • *
  • Posts: 62
Getting output from a console
« Reply #113 on: April 23, 2008, 06:38:14 pm »
Quote
the only part of it which is non portable for the moment is the class i implement to read console output (under Win32 that's not an easy task). I think reading svn console output under linux (or any other platform) should be easier.

Maybe the code snippet linked below can help :
http://www.wxdev.fr/snipp24-wxExecute-Recuperer_resultat_ligne_commande.html

It's in french, but as you are from France, it shouldn't be that difficult to understand  :)

Offline orel

  • Multiple posting newcomer
  • *
  • Posts: 96
Re: Getting output from a console
« Reply #114 on: April 23, 2008, 09:49:19 pm »
Quote
the only part of it which is non portable for the moment is the class i implement to read console output (under Win32 that's not an easy task). I think reading svn console output under linux (or any other platform) should be easier.

Maybe the code snippet linked below can help :
http://www.wxdev.fr/snipp24-wxExecute-Recuperer_resultat_ligne_commande.html

It's in french, but as you are from France, it shouldn't be that difficult to understand  :)
Thank you man (merci beaucoup!!) but this has been already solved some time ago.

Hey! any news about the plugin, does it's ready to be added to the codeblocks contrib repo?
I am not sure it is possible for the moment, i didn't update the repository those times because i can't work on the plugin as often as i would like to.

But i think what i am doing will save time later for those who want to develop other source control plugins.
I have designed a Code::Blocks souce control plugin interface and i am currently redesigning SVNInside, implementing this interface .
So with that work done, it should be easier for someone to develop a CVS (or whatever source control system) plugin for Code::Blocks. The advantage of this solution is to have homogenous source control on CB, whatever system you use.
windows XP SP2
mingw gcc 3.4.5
svn Code::Blocks and M$ Visual Studio 2005 and .NET to eat!! SVNInside plugin :http://forums.codeblocks.org/index.php/topic,7063.0.html

Offline JGM

  • Lives here!
  • ****
  • Posts: 518
  • Got to practice :)
Re: SVNInside : development of another SVN plugin for CodeBlocks
« Reply #115 on: April 24, 2008, 04:14:27 am »
Thats great, you're making a great job  :D
Keep up the good work!

Offline Alexis

  • Multiple posting newcomer
  • *
  • Posts: 62
Re: Getting output from a console
« Reply #116 on: April 24, 2008, 10:17:32 am »
Thank you man (merci beaucoup!!) but this has been already solved some time ago.

Just after posting, I saw that this issue was on top of a very long thread and so might have been already solved... Sorry :oops:

Offline denk_mal

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: SVNInside : development of another SVN plugin for CodeBlocks
« Reply #117 on: May 09, 2008, 10:48:53 am »
Hello,

I've been using this plugin and it works quite well for me (good work) but a friend has checked out the svn repository for my project and got my svn username on the next start of c::b.
I found out that my svn username has been saved in the c::b project file that is also checked into the svn repository.

IMHO it should not be saved into the project file but anyway;
Is there a way to type in the username and password on c::b start or when an svn action is triggered so that there is no need for the username to be saved into the project file?

thanks
denk_mal

Offline orel

  • Multiple posting newcomer
  • *
  • Posts: 96
Re: SVNInside : development of another SVN plugin for CodeBlocks
« Reply #118 on: May 09, 2008, 10:59:21 pm »
Hello,

I've been using this plugin and it works quite well for me (good work) but a friend has checked out the svn repository for my project and got my svn username on the next start of c::b.
I found out that my svn username has been saved in the c::b project file that is also checked into the svn repository.

IMHO it should not be saved into the project file but anyway;
Is there a way to type in the username and password on c::b start or when an svn action is triggered so that there is no need for the username to be saved into the project file?

thanks
denk_mal

Thank you very much man, gld to hear from users some time...
You are totally right with this issue, SVNInside should ask for the login and the password as soon as a command needs authentification in current Code:Blocks session, then it would be saved until the next CB session or until the user changes by himself the login and/or password. The only thing saved inside the Code::Blocks project file would be the fact that the repository need (or not) some authentification.
windows XP SP2
mingw gcc 3.4.5
svn Code::Blocks and M$ Visual Studio 2005 and .NET to eat!! SVNInside plugin :http://forums.codeblocks.org/index.php/topic,7063.0.html

Offline dmoore

  • Developer
  • Lives here!
  • *****
  • Posts: 1576
Re: SVNInside : development of another SVN plugin for CodeBlocks
« Reply #119 on: May 10, 2008, 05:58:50 pm »
Why do you keep any svn info in the project files? There isn't a 1:1 correspondence between projects and repositories. why not just save the svn info you need in a separate config file (or, my preference, in the global user config)?