[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: rev 2897 - trunk trunk/build

From: <brane_at_xbc.nu>
Date: 2002-08-06 18:53:21 CEST

Karl Fogel wrote:

>brane@tigris.org writes:
>>* gen-make.py: Import gen_make instead of gen_base. All references updated.
>>Also load svn-dev.el.
>Ah, okay, I should have read the next commit mail before
>responding... This answers some of my questions.

Yes, I intentionally did this in two commits, so that the changes in
MakefileGenerator were not hidden within the added file.

>But still: "gen-make.py" and "gen_make.py"? How are we going to talk
>about these files (verbally, I mean) without getting confused? :-)

Well, I'm not confused: "gen dash make dot py" vs. "build slash gen make
dot py". :-)

The goal is to have a set of build script generators, living on top of
the gen_base module: gen_make.py for Unix makediles, gen_dsp.py for MSVC
6.x project files, gen_whoknowswhat.py for MSVC.NET project files, etc.

Actually, I feel that in this case, pairing off gen-make.py with
build/gen_make.py (and later gen-dsp.py with build/gen_dsp.py) is sort
of logical. If you keep in mind that you can't easily import a python
file as a module if it contains a dash, there's even a visual clue that
lets you tell the difference between scripts and modules.

In the end, I suspect we'll just have a gen.py in the top level that'll
generate appropriate files based on parameters/platform/whatever.

(And before you ask, I didn't name the new file gen_makefile.py because
Emacs in its glory decides that it should be in Makefile-mode, because
of the name... Yes, I know there are other ways to fix that.)

Brane ─îibej   <brane_at_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
Received on Tue Aug 6 18:53:53 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.