You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Greg Stein <gs...@lyra.org> on 2003/03/02 06:47:51 UTC
Re: svn commit: rev 5174 - trunk/build/generator
Before going hog-wild replacing everything with EZT templates, I wanted to
ask the list about it. My idea was to use the templates for the .dsp files,
.dsw files, and anything else where there is a good chunk of boilerplate
that is needed.
(note that templating doesn't apply the same to the Unix makefiles cuz
Makefile.in has all the "boilerplate" and build-outputs.mk is just the real
barebones data)
The advantage that I see is that we're moving from a procedural to a
declarative approach for the output files. Theoretically :-), the templates
are easier to edit. Also note that I've set the template to the right line
endings (altho it seems the output doesn't have it, so I gotta figure out
where they got lost).
After looking at the XML-ish nastiness in gen_vcnet_vcproj.py, I'd much
rather swap out that gunk for a simple template.
Thoughts?
Cheers,
-g
On Sat, Mar 01, 2003 at 11:56:45PM -0600, gstein@tigris.org wrote:
> Author: gstein
> Date: Sat Mar 1 23:56:34 2003
> New Revision: 5174
>
> Added:
> trunk/build/generator/ezt.py
> trunk/build/generator/msvc_dsp.ezt (text, props changed)
> Modified:
> trunk/build/generator/gen_msvc_dsp.py
> Log:
> Begin reimplementation using EZT templates for the .dsp files.
>
> * build/generator/ezt.py: add in the EZT easy templating system. this
> a copy of revision 85 of:
> http://svn.webdav.org/repos/projects/subwiki/trunk/lib/ezt.py
>
> * build/generator/msvc_dsp.ezt: template for .dsp files. the template
> is also set for an EOL style of CRLF. I wasn't sure how sensitive
> MSVC is to spaces/newlines, so this template precisely replicates
> the .dsp that Brandon's code generated [at the cost of a bit of
> readability of the template].
>
> * build/generator/gen_msvc_dsp.py:
> (Generator.write_project): gut this and replace with the generation
> from the msvc_dsp.ezt template.
>...
--
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: rev 5174 - trunk/build/generator
Posted by Daniel Rall <dl...@finemaltcoding.com>.
=?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <br...@xbc.nu> writes:
> Greg Stein wrote:
>
> >Before going hog-wild replacing everything with EZT templates, I wanted to
> >ask the list about it. My idea was to use the templates for the .dsp files,
> >.dsw files, and anything else where there is a good chunk of boilerplate
> >that is needed.
> >
> >(note that templating doesn't apply the same to the Unix makefiles cuz
> > Makefile.in has all the "boilerplate" and build-outputs.mk is just the real
> > barebones data)
> >
> >The advantage that I see is that we're moving from a procedural to a
> >declarative approach for the output files. Theoretically :-), the templates
> >are easier to edit. Also note that I've set the template to the right line
> >endings (altho it seems the output doesn't have it, so I gotta figure out
> >where they got lost).
> >
> >After looking at the XML-ish nastiness in gen_vcnet_vcproj.py, I'd much
> >rather swap out that gunk for a simple template.
> >
> >Thoughts?
> >
> >
> Aye! Template files embedded in code are yucky.
EZT is good stuff
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: rev 5174 - trunk/build/generator
Posted by Branko Čibej <br...@xbc.nu>.
Greg Stein wrote:
>Before going hog-wild replacing everything with EZT templates, I wanted to
>ask the list about it. My idea was to use the templates for the .dsp files,
>.dsw files, and anything else where there is a good chunk of boilerplate
>that is needed.
>
>(note that templating doesn't apply the same to the Unix makefiles cuz
> Makefile.in has all the "boilerplate" and build-outputs.mk is just the real
> barebones data)
>
>The advantage that I see is that we're moving from a procedural to a
>declarative approach for the output files. Theoretically :-), the templates
>are easier to edit. Also note that I've set the template to the right line
>endings (altho it seems the output doesn't have it, so I gotta figure out
>where they got lost).
>
>After looking at the XML-ish nastiness in gen_vcnet_vcproj.py, I'd much
>rather swap out that gunk for a simple template.
>
>Thoughts?
>
>
Aye! Template files embedded in code are yucky.
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org