Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Building after svn export

<< < (3/3)

thomas:

--- Quote from: php-coder on January 04, 2006, 12:12:18 pm ---Hmmm.. C::B build successfully but revision 0 (see http://img461.imageshack.us/my.php?image=codeblocks5cr.png) not right IMHO.
--- End quote ---
It is perfectly right. You compile from sources which are not under revision control, so the revision number is zero. There is no way for the tool to determine the revision of these sources.
Even if you sent me a tarball of all the sources, it would not be trivial to find out which revision you use.

If you use checkout instead of export (which you really should) then you will see the revision number of your checked out version.

killerbot:
@thomas : I was not talking about the tool source, but the two files that include the generated header. But as you desrcibe it should be ok, i'll have a closer watch on this when i do my builds.

php-coder:

--- Quote from: Urxae on January 04, 2006, 02:34:08 am ---If you really want to build after exporting, be sure to run that command before exporting and remove it from the makefile so it doesn't give that error.

--- End quote ---

Thnx a lot! It's work and satisfyed my wishes !

Urxae:

--- Quote from: thomas on January 04, 2006, 12:17:35 pm ---
--- Quote ---EDIT: And maybe just quit if the output file already exists to not overwrite revision information already present?
--- End quote ---
In that case, your revision will never change, no matter to what revision you update. This defeats the purpose of autorevision, you could just as well hardcode a revision number into your sources then. The purpose of this tool is to update the revision number that is visible in the application every time the revision of the source files has changed, without any interaction from the user.

--- End quote ---

As I explained in my reply to killerbot, I meant only to do this if revision information wasn't available. I agree it's not perfect though, updating without building before an export will have it report the wrong revision number.


--- Quote ---
--- Quote ---How do you mean the build shoundn't abort?
--- End quote ---
It should. That's my point. As you can see from the source which you posted yourself, the exit code was -1. Therefore, the error "missing file autorevision.h" should be entirely impossible because the build process should immediately break after autorevision exits.

--- End quote ---

Ah, that's the misunderstanding. That wasn't the error message given:

--- Quote from: php-coder on January 04, 2006, 01:42:27 am ---./auto_revision +int +wx +t ../../.. ./../../sdk/autorevision.h
Error: could not open input file

--- End quote ---
It couldn't open the input file, it didn't mention autorevision.h. The input file is .svn/entries IIRC, which would indeed not be present after an export.

Navigation

[0] Message Index

[*] Previous page