Christoph Schulz <firstname.lastname@example.org> wrote:
> I wanted to ask, why the x64 port is not being merged into HEAD? From
> what I have looked at, the changes are mostly trivial (except VC71 ->
> VC8). Since I got an amd64 I'm interessted in having a "stable" x64
> Port. While I was reading the FAQ I just tought "man, that may take a
> while until there is something stable". Am I right or is there already
> some development for merging the patches x64 into HEAD?
I am pleased that people find the results of my porting efforts useful.
For all of you who are interested in this port, I would like make some
statements. Beware!, that's gonna be a lengthy post ;)
0. My motivations
* Learn things about VC8 and 64 bit porting issues.
* Prepare TSVN for the time I will need it on x64 at the office (Q2/06?).
* Help people that so profoundly help me doing my work every day.
* Keep the acceptance of TSVN on a high level
(TCVS is said to be available on x64).
* Get a positive feedback from the community.
1. Current status.
* I have committed to provide 64 bit binaries for TSVN releases.
This has been started with v1.2.2 and will eventually end when
x64 binaries become an integral part of the TSVN installables.
* A lot of patches have already been applied to the TSVN trunk
to make it less platform dependent and to prepare it for VC8.
* There are 3 possible configurations to make TSVN usable on x64:
- "standard" installation plus 32 bit explorer as default
- "native" 64 bit binaries
- "mixed": 64 bit explorer plug-in only. Use 32 bit binaries for
everything else (TortoiseProc, Merge, ..)
All of them are possible as of now. It is not known whether one can
install 32 and 64 bit versions and use them simultaneously.
* BDB (via file://) and spellchecker are known not to work.
2. Development - general aspects
* My efforts to improve the port will be rather sporadic - mainly
depending on the weather: A few rainy weekends may work
* If someone would like to speed things up, just grab the patchball
and go ahead.
* Since the port seems to work for some people, it is about
time for me to send the patches to the respective .lib projects
(Yes, I could have done that earlier but ..)
3. Development - strategy
* Make the subversion build script generator work for VC8.
Ideally, it will work for both, win32 and win64.
* Prepare the TSVN code for VC8: Use secure C-lib functions.
* Move TSVN to VS2005 (should be released in Q4/05).
This will require some coordination among committers, I guess.
Because of subtile changes in the project file format, this step
(+ the same for SVN) is the main showstopper.
* Add the target platform to the inputs of the build scripts
(shouldn't be too hard).
* Decide upon the installer options. A fat package supporting both
targets may be 30 .. 40 MB (mainly due to the VC8 runtime libs).
Make installer(s) compile for both platforms.
Oh my! We are not running out of work :/
Stefan "had-to-vote" Fuhrmann.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Sep 19 00:22:09 2005