User forums > Help
error when compiling from svn sources (25-10/2006)
afb:
I don't think requiring Subversion for compiling the nightly build
is any harder of a requirement than requiring wxWidgets installed...
The language/locale issue was a curveball, but seems sorted out.
Maybe you could also take a look at the proposed autorevision changes ?
I would like to have access to the raw rev. number, without the trunk-
--- Code: ---m4_define([SVN_REVISION], trunk-r3163)
m4_define([SVN_REV], 3163)
--- End code ---
--- Code: ------ configure.in (revision 3163)
+++ configure.in (arbetskopia)
@@ -49,6 +49,8 @@
AC_CHECK_FUNC(snprintf, AC_DEFINE(HAVE_SNPRINTF,,snprintf))
AC_CHECK_FUNC(vsnprintf, AC_DEFINE(HAVE_VSNPRINTF,,vsnprintf))
+AC_SUBST(REVISION, SVN_REV)
+
dnl versioning info for libtool
dnl Note this is the ABI version which is not the same as our actual library version
CODEBLOCKS_CURRENT=0
--- End code ---
The RPM spec is using a sed hack, but that doesn't work too good for XML...
(I want it to be able to autogenerate a codeblocks.plist, for Mac OS X)
--- Code: ------ codeblocks.spec.in (revision 3163)
+++ codeblocks.spec.in (arbetskopia)
@@ -1,4 +1,4 @@
-%define _svnrev %(echo @VERSION@ | cut -c 8-)
+%define _svnrev @REVISION@
%define req_wxgtk 2.6.0
%define _fedora %(if [ -f /etc/fedora-release ]; then echo 1; else echo 0; fi)
%define _suse %(if [ -f /etc/SuSE-release ]; then echo 1; else echo 0; fi)
--- End code ---
edit: on second thought, changing SVN_REVISION is probably a little confusing.
Not to mention that the variable and define having the same name doesn't work.
afb:
--- Quote from: tiwag on October 31, 2006, 01:13:48 pm ---linux and mac should always have svn commandline client installed, isn't it?
--- End quote ---
True for the latest versions, not so for older versions (it is installable...)
thomas:
--- Quote from: tiwag on October 31, 2006, 01:13:48 pm ---linux and mac should always have svn commandline client installed, isn't it?
--- End quote ---
This is why we are having these troubles... those are all localised.
--- Quote from: tiwag on October 31, 2006, 01:13:48 pm ---Although it doesn't interest me what gives you the creeps, i would simply use svn, and everyone who wants to build his own C::B from svn has to install it - basta
--- End quote ---
When I first incepted autorevision, it only worked with Subversion, had no fallback, and did not do any serious error checking.
The same day (because he promptly encountered a problem), Yiannis came up with the following requirements:
1. it must not break the build
2. it must work with an exported tarball, i.e. when there is no revision information at all
3. it should work without svn or any other dependencies, having a fallback
4. it can have revision=0 as fallback if nothing else helps
--- Quote from: afb on October 31, 2006, 01:19:47 pm ---Maybe you could also take a look at the proposed autorevision changes ?
I would like to have access to the raw rev. number, without the trunk-
--- End quote ---
But... that's exacly what autorevision provides? The trunk- comes from somewhere else...?
--- Quote from: afb on October 31, 2006, 01:19:47 pm ---<everything else>
--- End quote ---
(pretends to understand anything you said)
Yes... that looks nice, dear. :lol:
Game_Ender:
I am going to have to give this a try because last time on checked, C libraries were complier independent thanks to the standard C abi. I will see how the subversion developers managed to subvert this.
afb:
--- Quote from: thomas on October 31, 2006, 02:40:35 pm ---When I first incepted autorevision, it only worked with Subversion, had no fallback, and did not do any serious error checking.
The same day (because he promptly encountered a problem), Yiannis came up with the following requirements:
1. it must not break the build
2. it must work with an exported tarball, i.e. when there is no revision information at all
3. it should work without svn or any other dependencies, having a fallback
4. it can have revision=0 as fallback if nothing else helps
--- End quote ---
Yeah, I guess we do need some kind of such workaround for Windows...
(I saw that someone was working on a replacement for wx-config too)
--- Quote ---But... that's exacly what autorevision provides? The trunk- comes from somewhere else...?
--- Quote from: afb on October 31, 2006, 01:19:47 pm ---<everything else>
--- End quote ---
(pretends to understand anything you said)
Yes... that looks nice, dear. :lol:
--- End quote ---
Sorry, I was mixing up autorevision with update_revision.sh -
I meant "revision" handling in general, sorry for the confusion...
Autorevision only writes the src/sdk/autorevision.h header, right ?
Will do up a proper patch for the other change, to the autoconf.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version