Author Topic: CodeBlocks IDE shows "svn 0" for svn builds  (Read 4118 times)

Offline Mephistopheles

  • Multiple posting newcomer
  • *
  • Posts: 16
CodeBlocks IDE shows "svn 0" for svn builds
« on: June 05, 2008, 06:43:42 pm »
Hello,

I'm currently building RPMs for openSUSE 10.3 from SVN which works quite fine with one minor problem:

The GUI shows "svn 0" instead of the correct revision number - e.g. "svn 5087" - in the splash screen and in the Help -> About dialog.

.last_revision contains the correct revision number and the source archive from which I build my rpms contains the .svn directories as well.

So, please enlighten me what I am missing and where to configure / fill in the current revision number so it is correctly shown in the gui as well.

Thanks a lot in advance :)

Offline dje

  • Lives here!
  • ****
  • Posts: 682
Re: CodeBlocks IDE shows "svn 0" for svn builds
« Reply #1 on: June 05, 2008, 08:00:50 pm »
Hi !

It looks like SVN is not installed or installed but not referenced in the PATH environment variable

Dje

Offline olipfei

  • Multiple posting newcomer
  • *
  • Posts: 26
Re: CodeBlocks IDE shows "svn 0" for svn builds
« Reply #2 on: June 05, 2008, 08:36:36 pm »
Didn't dare to complain about this, but same is happening to me (on SuSE Linux 9.1!). It worked some time ago, but I can't remember when the cut between working and non-working was.

svn IS in installed and in my path as I regularly update the CB trunk from command line, BUT (idea/hint): my version is quite old, 1.0. Perhaps some command line parameters that are necessary for auto-versioning CB (splash, about, etc.) are simply not yet supported by my old version of svn.

Though openSuSE 10.3 should contain a sufficiently recent version of svn to establish auto-versioning. I will fetch the source and try to build a newer version of svn and see what happens.

Regards,
Oliver

Offline Mephistopheles

  • Multiple posting newcomer
  • *
  • Posts: 16
Re: CodeBlocks IDE shows "svn 0" for svn builds
« Reply #3 on: June 05, 2008, 08:47:14 pm »
@dje:
Good call, simply adding subversion to the build environment fixed it. Thank you very much!

@olipfei:
fwiw 10.3 has Subversion 1.4.4 and all I had to do was to install the client package in the build environment.