There has been a batch file that implements the steps in the INSTALL
instructions for quite a while now. It is even referred to within
INSTALL. Look at section E6.
Ben Collins-Sussman <sussman@collab.net> wrote on 08/11/2004 11:19:21 AM:
> On Wed, 2004-08-11 at 01:49, Patrick Mayweg wrote:
> > Hi Ben,
> > the windows build does not work out of the box because of an absolut
> > path to expat in build/win32/build_neon.bat. This should be a relative
> > path to included apr.
>
> Here comes an impressive display of ignorance:
>
> Since when are we auto-generating .dsp's and .bat scripts in our release
> tarballs? Is this a new thing, something to enhance our CRLF-eol-style
> .zip package? Have I been asleep?
>
> Up to now, my simple understanding of the world has always been: to
> build on win32, you must follow the instructions in INSTALL. And that
> means: 1. fetch lots of packages, arrange them in a special way, 2. run
> gen-make.py -t dsp etc, 3. run an 'msdev' commandline, 4. manually
> assemble the results.
>
> If I had known about auto-generated .dsp/.bat files, and if they're now
> being advertised as the "official" way to build a .zip release, then I
> would have insisted on testing the RC2 .zip file yesterday. It becomes
> just as important as testing ./configure in the .tar.gz packages. But
> living in total ignorance, I assumed the .zip file was nothing more than
> a CRLF-converted source tree.
>
> Someone... please de-confuse me.
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 11 17:31:55 2004