Missing file in SVN?

SDL Development
1

Dear all,
I have a problem compiling the latest svn version due to a missing
SDL_revision.h file. Have I missed something ?

Thanks

2

Dear all,
I have a problem compiling the latest svn version due to a missing
SDL_revision.h file. Have I missed something ?

Try grabbing the latest svn snapshot, it should include SDL_revision.h.
If you’re using configure/make style build then it should automatically
be generated for you.

See ya,
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC

3

Thanks for your prompt reply.

Actually, I’m compilling under VC8-vista. As far as I can see, the file
SDL_revision.h is not part of the last snapshot. As the include directive seems
to have been added recently, I though that might have been just an omission. Is
there anyway to generate that file ?

Thanks again,

Cl?ment

4

I was having this problem too, but Sam’s reply tipped me off to the
solution (I had to run “./autogen.sh” and “./configure” in UNIX before
using my non-autoconf Makefile (for the Nintendo DS build)).
Since you seem to be using Windows, though, this might not be possible
for you. However, the file it created (include/SDL_revision.h) was
exactly as follows:

#define SDL_REVISION 4362

So to build in Visual Studio for now, you could probably just make that
file yourself and #define SDL_REVISION to be whichever revision you
checked out of SVN.

-DarrenOn Tue, 2009-01-06 at 16:05 +0000, Cl?ment Forest wrote:

Thanks for your prompt reply.

Actually, I’m compilling under VC8-vista. As far as I can see, the file
SDL_revision.h is not part of the last snapshot. As the include directive seems
to have been added recently, I though that might have been just an omission. Is
there anyway to generate that file ?

Thanks again,

Cl?ment

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

5

Thanks for your prompt reply.

Actually, I’m compilling under VC8-vista. As far as I can see, the file
SDL_revision.h is not part of the last snapshot. As the include directive seems
to have been added recently, I though that might have been just an omission. Is
there anyway to generate that file ?

This was supposed to be in the snapshot, I’ll figure out what happened.

Thanks!
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC

6

The file is missing in revision 4396 too.

Greets
Christoph

cforest schrieb:

Dear all,
I have a problem compiling the latest svn version due to a missing
SDL_revision.h file. Have I missed something ?

Thanks

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

-------------- next part --------------
A non-text attachment was scrubbed…
Name: seija.vcf
Type: text/x-vcard
Size: 139 bytes
Desc: not available
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20090113/1fa41eaf/attachment.vcf

7

The file is missing in revision 4396 too.

This file doesn’t get checked into subversion. You need to either run
build-scripts/updaterev.sh or grab a snapshot from the SDL website:
http://www.libsdl.org/tmp/SDL-1.3.zip

See ya!
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC

8

Mh thats bad.
I’m using a Windows Development Environment (MS VC++ Express 2008) and
can’t run these scripts.
It is planed that this file isn’t included in the SVN or don’t you know
why it’s not commiting?

Greets
Christoph

Sam Lantinga schrieb:>> The file is missing in revision 4396 too.

This file doesn’t get checked into subversion. You need to either run
build-scripts/updaterev.sh or grab a snapshot from the SDL website:
http://www.libsdl.org/tmp/SDL-1.3.zip

See ya!
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

9

Hello !

The file is missing in revision 4396 too.

This file doesn’t get checked into subversion. You need to either run
build-scripts/updaterev.sh or grab a snapshot from the SDL website:
http://www.libsdl.org/tmp/SDL-1.3.zip

I think it would make sense to put such a file into the repository
and then add svn:ignore to it.

Maybe a dummy file that has the special
rev. number -1 in it, so that people can ask or print for the revision and
if it is -1 they know, this is a special case.

Official builds will always
of course run the script and print out the right rev. number.

CU

10

I think it would make sense to put such a file into the repository
and then add svn:ignore to it.

Yeah, I tried that, it doesn’t work.

See ya,
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC

11

I’m going to rewrite the generating scripts for Windows Systems and put
the scripts into the Build Tool Chain of the MS VC++ project file so
that it is automatically created when you compile SDL with MS VC++.
The only things you need are the command line version of svn (not only
TortoiseSVN).

Is that OK with you?

Greets
Christoph

Sam Lantinga schrieb:>> I think it would make sense to put such a file into the repository

and then add svn:ignore to it.

Yeah, I tried that, it doesn’t work.

See ya,
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

12

Hello !

I think it would make sense to put such a file into the repository
and then add svn:ignore to it.

Yeah, I tried that, it doesn’t work.

Why are you using a script to generate the SDL_revision.h file.
SVN has the same way, as CVS had a way to rewrite source files
that have special keywords in it :----------------

svn:keywords

Subversion has the ability to substitute keywords?pieces of useful,
dynamic information about a versioned file?into the contents of the
file itself. Keywords generally describe information about the last
time the file was known to be modified. Because this information
changes each time the file changes, and more importantly, just after
the file changes, it is a hassle for any process except the version
control system to keep the data completely up-to-date. Left to human
authors, the information would inevitably grow stale.

For example, say you have a document in which you would like to
display the last date on which it was modified. You could burden every
author of that document to, just before committing their changes, also
tweak the part of the document that describes when it was last
changed. But sooner or later, someone would forget to do that. Instead
simply ask Subversion to perform keyword substitution on the
LastChangedDate keyword. You control where the keyword is inserted
into your document by placing a keyword anchor at the desired location
in the file. This anchor is just a string of text formatted as
$KeywordName$.

All keywords are case-sensitive where they appear as anchors in files:
you must use the correct capitalization in order for the keyword to be
expanded. You should consider the value of the svn:keywords property
to be case-sensitive too?certain keyword names will be recognized
regardless of case, but this behaviour is deprecated.

Subversion defines the list of keywords available for substitution.
That list contains the following five keywords, some of which have
aliases that you can also use:

Date

 This keyword describes the last time the file was known to have

been changed in the repository, and looks something like $Date:
2002-07-22 21:42:37 -0700 (Mon, 22 Jul 2002) $. It may also be
specified as LastChangedDate.
Revision

 This keyword describes the last known revision in which this file

changed in the repository, and looks something like $Revision: 144 $.
It may also be specified as LastChangedRevision or Rev.
Author

 This keyword describes the last known user to change this file in

the repository, and looks something like $Author: harry $. It may also
be specified as LastChangedBy.
HeadURL

 This keyword describes the full URL to the latest version of the

file in the repository, and looks something like $HeadURL:
http://svn.collab.net/repos/trunk/README $. It may be abbreviated as
URL.
Id

 This keyword is a compressed combination of the other keywords.

Its substitution looks something like $Id: calc.c 148 2002-07-28
21:30:43Z sally $, and is interpreted to mean that the file calc.c was
last changed in revision 148 on the evening of July 28, 2002 by the
user sally.

So when you checkout the source with SVN it automatically puts
the Rev. Number into the source file.

CU

13

No, not really.

As you can read in the text you pasted, the special keywords are only
replaced WHEN THE FILE CHANGES and not when you check it out.
And I think the replacement works only if you make an export of the SVN
System. Cause I didn’t see any changes in my own files while using these
Keywords.

Greets
Christoph

Torsten Giebl schrieb:> Hello !

I think it would make sense to put such a file into the repository
and then add svn:ignore to it.

Yeah, I tried that, it doesn’t work.

Why are you using a script to generate the SDL_revision.h file.
SVN has the same way, as CVS had a way to rewrite source files
that have special keywords in it :

svn:keywords

Subversion has the ability to substitute keywords?pieces of useful,
dynamic information about a versioned file?into the contents of the
file itself. Keywords generally describe information about the last
time the file was known to be modified. Because this information
changes each time the file changes, and more importantly, just after
the file changes, it is a hassle for any process except the version
control system to keep the data completely up-to-date. Left to human
authors, the information would inevitably grow stale.

For example, say you have a document in which you would like to
display the last date on which it was modified. You could burden every
author of that document to, just before committing their changes, also
tweak the part of the document that describes when it was last
changed. But sooner or later, someone would forget to do that. Instead
simply ask Subversion to perform keyword substitution on the
LastChangedDate keyword. You control where the keyword is inserted
into your document by placing a keyword anchor at the desired location
in the file. This anchor is just a string of text formatted as
$KeywordName$.

All keywords are case-sensitive where they appear as anchors in files:
you must use the correct capitalization in order for the keyword to be
expanded. You should consider the value of the svn:keywords property
to be case-sensitive too?certain keyword names will be recognized
regardless of case, but this behaviour is deprecated.

Subversion defines the list of keywords available for substitution.
That list contains the following five keywords, some of which have
aliases that you can also use:

Date

This keyword describes the last time the file was known to have

been changed in the repository, and looks something like $Date:
2002-07-22 21:42:37 -0700 (Mon, 22 Jul 2002) $. It may also be
specified as LastChangedDate.
Revision

This keyword describes the last known revision in which this file

changed in the repository, and looks something like $Revision: 144 $.
It may also be specified as LastChangedRevision or Rev.
Author

This keyword describes the last known user to change this file in

the repository, and looks something like $Author: harry $. It may also
be specified as LastChangedBy.
HeadURL

This keyword describes the full URL to the latest version of the

file in the repository, and looks something like $HeadURL:
http://svn.collab.net/repos/trunk/README $. It may be abbreviated as URL.
Id

This keyword is a compressed combination of the other keywords.

Its substitution looks something like $Id: calc.c 148 2002-07-28
21:30:43Z sally $, and is interpreted to mean that the file calc.c was
last changed in revision 148 on the evening of July 28, 2002 by the
user sally.

So when you checkout the source with SVN it automatically puts
the Rev. Number into the source file.

CU

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

14

Hello !

No, not really.

As you can read in the text you pasted, the special keywords are only
replaced WHEN THE FILE CHANGES and not when you check it out.
And I think the replacement works only if you make an export of the SVN
System. Cause I didn’t see any changes in my own files while using these
Keywords.

You are right, damn. I just tested it.

CU

15

I’m going to rewrite the generating scripts for Windows Systems and put
the scripts into the Build Tool Chain of the MS VC++ project file so
that it is automatically created when you compile SDL with MS VC++.
The only things you need are the command line version of svn (not only
TortoiseSVN).

Is that OK with you?

Sure. If svnversion isn’t available, you can write SDL_revision.h with
a revision 0.

Thanks!
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC

16

I’ve seen projects that check svnversion first, then check the
"Revision" line in the “svn info” command, before falling back to some
dummy valueOn Wed, Jan 14, 2009 at 10:18 PM, Sam Lantinga wrote:

Sure. If svnversion isn’t available, you can write SDL_revision.h with
a revision 0.

–
http://codebad.com/

17

Cause my mail server seem to blocked my previous mail:

Hi,

I know have convert the updaterev.sh script to Windows using the Windows
Scripting Host.
The .vbs file has to be saved under ROOT_DIR\build-scripts
The .vcproj files has to be saved under the project directories for
Visual C++
The .sln has to be saved under the VisualC directory.

All Projects/Solutions are converted to Visual C++ 2008 (cause I don’t
have any other Visual C++).

The updaterev.vbs Script is run every time you compile the project.
The build files are now saved under
ROOT_DIR\build(Release|Release_NOSTDIO|Debug)

I hope it works (on my system it does work).

You can download the files at http://www.dragons-server.de/SDL.zip

Greets
Christoph

Sam Lantinga schrieb:

I’m going to rewrite the generating scripts for Windows Systems and put
the scripts into the Build Tool Chain of the MS VC++ project file so
that it is automatically created when you compile SDL with MS VC++.
The only things you need are the command line version of svn (not only
TortoiseSVN).

Is that OK with you?

Sure. If svnversion isn’t available, you can write SDL_revision.h with
a revision 0.

Thanks!
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

-------------- next part --------------
A non-text attachment was scrubbed…
Name: seija.vcf
Type: text/x-vcard
Size: 139 bytes
Desc: not available
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20090124/505633c2/attachment.vcf