User forums > Help
error when compiling from svn sources (25-10/2006)
afb:
--- Quote from: Game_Ender on October 31, 2006, 12:52:51 am ---The subversion developers don't recommend parsing the output of the subversion command lines tools.
--- End quote ---
Subversion has been affected by the same disease as Yum then...
It even changes the output on purpose, to defeat screenscraping.
My sympathies to you, Thomas. Seems like an awful amount of
work just to get a single revision number in the about box... :-)
tiwag:
why not providing a svn executable in the svn repository ?
then you always could use "svn info" and parse the revision number from there ?
thomas:
--- Quote from: afb on October 31, 2006, 10:29:21 am ---Subversion has been affected by the same disease as Yum then...
It even changes the output on purpose, to defeat screenscraping.
My sympathies to you, Thomas. Seems like an awful amount of
work just to get a single revision number in the about box... :-)
--- End quote ---
The funny thing is that the "official correct way" to do that is to run svn in backticks from the makefile and pipe the output through sed. We'd probably do that if we were building Code::Blocks with makefiles everywhere. But even then it would be a pain, as it would have the very same issues.
So we're rather using one tool everywhere instead of two solutions for two build systems, both of which don't work reliably :lol:
thomas:
--- Quote from: tiwag on October 31, 2006, 10:35:45 am ---why not providing a svn executable in the svn repository ?
then you always could use "svn info" and parse the revision number from there ?
--- End quote ---
Distributing executables for being able to build from source is giving me the creeps... :)
Apart from that, we would need at least 3 executables (Windows, Linux/BSD, Mac) to cover the four most used platforms. Actually twice as many, if you account for 32/64 bits and Intel/PPC...
Also, we would still have potential issues then. If we distribute Subversion 1.3, but someone used 1.4 to check out, it won't work. On the other hand, if we distribute 1.4 and the working copy is 1.3, it might possibly break the working copy for the user by updating the repo. I don't think that will actually happen on svn info, but I haven't tried!
Regardless of whether it works now, it could be the same issue again with version 1.5, 1.8, or 2.0 any time in the future.
tiwag:
linux and mac should always have svn commandline client installed, isn't it?
this should be true for every serious developer on windoze too :P
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
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version