You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "D.J. Heap" <dj...@shadyvale.net> on 2003/05/17 04:50:34 UTC
[PATCH] Windows vcproj generator
This patch (with the attached vcproj files put into the build/win32
directory) gets the vcproj generator working -- at least for me. :)
The __INSTALLER__ project does not generate for some reason (causing the
solution to leave it unloaded when it is brought up), and I haven't
tested building the swig projects, but everything else builds for me
with debug symbols and resources where appropriate.
I'm not very happy about having to provide the vcproj files for apr and
friends, but since they are not provided by apr and trying to reference
the dsp's from the solution just causes VCNet to choke, I'm not sure
what else to do. The generator copies them from the build/win32
directory if they do not already exists in the various apr directories.
Perhaps someone with more knowledge of the build system on Windows
(Sandar, Greg, Brane?) can look this over and see a better way to handle
the apr projects and the __INSTALLER__?
One last possible problem is that I can't test the apr and friends
vcproj files on VCNet 7.0 (2002). I'm using VCNet 7.1 (2003) so I had
to tweak them a bit -- I think they will work on VCNet 7.0, but I'm not
positive.
Log:
Get the vcproj generator functional.
* build/generator/vcnet_vcproj.ezt:
many template files changes
* build/generator/gen_vcnet_vcproj.py:
much copying from the dsp generator and tweaking
* build/win32/svn_config.vcproj:
* build/win32/xml.vcproj:
* build/win32/apr.vcproj:
* build/win32/aprutil.vcproj:
* build/win32/gen_uri_delims.vcproj:
* build/win32/apriconv.vcproj:
* build/win32/apriconv_ccs_modules.vcproj:
* build/win32/apriconv_ces_modules.vcproj:
new pre-built project files
Re: [PATCH] Windows vcproj generator
Posted by "D.J. Heap" <dj...@shadyvale.net>.
Sander Striker wrote:
>>From: D.J. Heap [mailto:dj@shadyvale.net]
>>Sent: Saturday, May 17, 2003 6:51 AM
>
>
>>This patch (with the attached vcproj files put into the build/win32
>>directory) gets the vcproj generator working -- at least for me. :)
>
>
> Thanks for doing this.
No problem, it was fun getting back into Python a bit...I'd (almost)
forgotten how slick it can be.
>
> We probably end up committing .vcproj and .sln files to apr and friends.
> Unless apr switches to a generated model aswell... but somehow I think that
> isn't as easy to push through there as it was here ;).
>
Ah, that would be great...the generator really is *very* nice --
impressive work.
>
>>One last possible problem is that I can't test the apr and friends
>>vcproj files on VCNet 7.0 (2002). I'm using VCNet 7.1 (2003) so I had
>>to tweak them a bit -- I think they will work on VCNet 7.0, but I'm not
>>positive.
>
>
> I have VS.NET 2002, so I can test that. Not sure I'm going to be doing that
> today though.
>
>
> Sander
Cool, thanks! If the apr vcproj files don't work, then you should be
able to just convert the dsp's and use those -- that might be a better
option anyway.
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: [PATCH] Windows vcproj generator
Posted by Sander Striker <st...@apache.org>.
> From: Sander Striker [mailto:striker@apache.org]
> Sent: Saturday, May 17, 2003 11:10 AM
>> From: D.J. Heap [mailto:dj@shadyvale.net]
>> Sent: Saturday, May 17, 2003 6:51 AM
>
> > This patch (with the attached vcproj files put into the build/win32
> > directory) gets the vcproj generator working -- at least for me. :)
>
> Thanks for doing this.
>
>> The __INSTALLER__ project does not generate for some reason (causing the
>> solution to leave it unloaded when it is brought up), and I haven't
>> tested building the swig projects, but everything else builds for me
>> with debug symbols and resources where appropriate.
>
> Very nice!
Tested and confirmed that __INSTALLER__ indeed pops up a warning.
[...]
> I have VS.NET 2002, so I can test that. Not sure I'm going to be doing that
> today though.
The svn_config.vcproj needed a tweak, since it deleted *.bat on cleanup which
killed build_neon.bat. I guess that is some silly default because prior to my
change, I couldn't see anything in that .vcproj that referred to *.bat.
--- ..\subversion-vs.net\svn_config.vcproj Sat May 17 14:14:00 2003
+++ build\win32\svn_config.vcproj Sat May 17 13:04:56 2003
@@ -35,7 +35,8 @@
IntermediateDirectory="."
ConfigurationType="10"
UseOfMFC="0"
- ATLMinimizesCRunTimeLibraryUsage="FALSE">
+ ATLMinimizesCRunTimeLibraryUsage="FALSE"
+ DeleteExtensionsOnClean="*.obj;*.ilk;*.pdb;*.tlb;*.tli;*.tlh;*.tmp;*.rsp;$(TargetPath)">
<Tool
Name="VCCustomBuildTool"/>
<Tool
Otherwise it seems like a step in the good direction. User wise that is. I
haven't really had a chance to review your generator patches thouroughly.
Sander
RE: [PATCH] Windows vcproj generator
Posted by Sander Striker <st...@apache.org>.
> From: D.J. Heap [mailto:dj@shadyvale.net]
> Sent: Saturday, May 17, 2003 6:51 AM
> This patch (with the attached vcproj files put into the build/win32
> directory) gets the vcproj generator working -- at least for me. :)
Thanks for doing this.
> The __INSTALLER__ project does not generate for some reason (causing the
> solution to leave it unloaded when it is brought up), and I haven't
> tested building the swig projects, but everything else builds for me
> with debug symbols and resources where appropriate.
Very nice!
> I'm not very happy about having to provide the vcproj files for apr and
> friends, but since they are not provided by apr and trying to reference
> the dsp's from the solution just causes VCNet to choke, I'm not sure
> what else to do. The generator copies them from the build/win32
> directory if they do not already exists in the various apr directories.
>
> Perhaps someone with more knowledge of the build system on Windows
> (Sandar, Greg, Brane?) can look this over and see a better way to handle
> the apr projects and the __INSTALLER__?
We probably end up committing .vcproj and .sln files to apr and friends.
Unless apr switches to a generated model aswell... but somehow I think that
isn't as easy to push through there as it was here ;).
> One last possible problem is that I can't test the apr and friends
> vcproj files on VCNet 7.0 (2002). I'm using VCNet 7.1 (2003) so I had
> to tweak them a bit -- I think they will work on VCNet 7.0, but I'm not
> positive.
I have VS.NET 2002, so I can test that. Not sure I'm going to be doing that
today though.
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org