RE: Linker issues building subversion on Windows
From: Johan Corveleyn <johan.corveleyn_at_uz.kuleuven.ac.be>
Date: Wed, 9 Sep 2009 12:22:16 +0200
> Van: Daniel Shahaf [mailto:d.s_at_daniel.shahaf.name]
Oops, sorry. I meant to type that there was build output, but then I double-checked and couldn't find it anymore (and forgot about what I was typing :)). Maybe I was just confused and didn't build them correctly. Anyway, I got it working with the httpd build.
Version 2.2.13 (Win32 source distribution downloaded from httpd.apache.org)
> (I should commit the makefile when I have a few minutes)
Yes, that would be great. The svn build process on Windows should really be made easier and better documented. Committing your makefile, and document it (so people can find/use it) would be a good first step. Then maybe someone will find time to make it more robust/flexible, and to improve/document other parts of the windows build procedure.
Now, onto the next stage of my svn-windows build experiments: it doesn't run on another pc than the one on which I built it :(. Can you (or anyone else) help me troubleshoot?
- On the original build pc it all works fine (Win XP SP2).
I'm at a loss here. How can I troubleshoot this further? Maybe I made a stupid mistake during the build process, or maybe it's caused by SP3 vs. SP2? Or could this be caused by my fiddling with the masm versions?
Obviously I would like to have executables that are a little bit more portable (ideally between all 32bit Windows'es). Or can this only be achieved by building with VC 6 instead of VCE 2008? I don't really care about which compiler to use, as long as I can get it compiled. However, I don't have VC 6 lying around, and don't want to pay for a compiler just to build svn, so I thought the free VCE 2008 would suit me ...
Regards,
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.