You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Martin Tomes <li...@tomes.org> on 2004/04/26 10:34:58 UTC
[PATCH] Update build instructions for the 1.0.x branch on the Win32
platform.
Update the instructions for building Subversion on the Win32 platform.
The new instructions are split into sections which describe what is needed, how to prepare the files
(unpacking, environment etc.) and how to actually build the binaries with all available options
turned on.
* INSTALL
Update Win32 build instructions.
--
Martin Tomes
echo 'Martin x Tomes at controls x eurotherm x co x uk'\
| sed -e 's/ x /\./g' -e 's/ at /@/'
Re: [PATCH] Update build instructions for the 1.0.x branch on the Win32 platform.
Posted by kf...@collab.net.
John Peacock <jp...@rowman.com> writes:
> kfogel@collab.net wrote:
> > IOW, this is about _minimum_ requirements.
>
> Except that it could also be list of _maximum_ or _excluded_
> requirements, too. There were issues with SWIG 1.3.21 I believe where
> .19 and .20 would work, but initially .21 wouldn't. It would be
> helpful if the INSTALL document reflected reality /as we know it at
> the time of each release/. This should not be considered to be a
> static document.
When we know that a upper version doesn't work, we edit the doc to say
"Neon 0.24.5 through 3.25.3" or whatever.
My point has nothing to do with making the document static. It's
about not forcing people to upgrade software that they don't really
have to upgrade, because upgrading may cause problems with *other*
things on their system. We want to force as little churn as we can.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the Win32 platform.
Posted by Ben Reser <be...@reser.org>.
On Mon, Apr 26, 2004 at 04:45:20PM -0400, John Peacock wrote:
> Except that it could also be list of _maximum_ or _excluded_ requirements,
> too. There were issues with SWIG 1.3.21 I believe where .19 and .20 would
> work, but initially .21 wouldn't. It would be helpful if the INSTALL
> document reflected reality /as we know it at the time of each release/.
> This should not be considered to be a static document.
Actually SWIG 1.3.20 or newer wouldn't work for a while. This was
missed because clkao was using a pre-release version of 1.3.20 that
didn't have a last minute change they made that broke us...
The realistic problem here is we're using libraries/tools that don't
advertise compatability gurantees. Neon probably has them but I'm
unsure of what they are. SWIG well, they have no compatability
guarantees...
This makes it difficult to say what versions are truely required...
We can document what we *KNOW* works. Not what we think will work in
the future. We can also document what we infer might work in the
future.
Here's an example:
Neon version 0.24.5 is recommended. Neon versions in the 0.24 line newer than
0.24.5 may work with subversion but are untested at this time.
Then if 0.24.6 comes out and we don't feel we need to increase our
minimum requirements but know that 0.24.6 work we could update the text
as follows:
Neon version 0.24.5 or 0.24.6 are recommended. Neon versions in the
0.24 line newer than 0.24.6 may work with subversion but are untested at
this time.
I think we should be frank and honest with our users. We simply can't
tell them what future releases of other software that we depend upon
will or will not work.
--
Ben Reser <be...@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by John Peacock <jp...@rowman.com>.
kfogel@collab.net wrote:
>
> IOW, this is about _minimum_ requirements.
>
Except that it could also be list of _maximum_ or _excluded_ requirements, too.
There were issues with SWIG 1.3.21 I believe where .19 and .20 would work, but
initially .21 wouldn't. It would be helpful if the INSTALL document reflected
reality /as we know it at the time of each release/. This should not be
considered to be a static document.
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by Martin Tomes <li...@tomes.org>.
kfogel@collab.net wrote:
> Martin Tomes <li...@tomes.org> writes:
>
>>Well, if I keep the information up to date then hopefully it will be
>>specifying the most up to date version of each package which works.
>
> IOW, this is about _minimum_ requirements.
OK, I'll stick to that principle.
--
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the Win32 platform.
Posted by kf...@collab.net.
Martin Tomes <li...@tomes.org> writes:
> Well, if I keep the information up to date then hopefully it will be
> specifying the most up to date version of each package which works.
But, that means the document will sometimes be requiring higher
versions than actually necessary.
For example, suppose we work with Neon 0.24.5 for the next three
years. Then it's better to say we require "Neon 0.24.5 or higher"
than "Neon 3.30.2", because people might already have a perfectly good
Neon library on their system. (Of course, we might up our recommended
Neon past 0.24.5, but that still doesn't mean we have to require the
bleeding edge of everything all the time.)
IOW, this is about _minimum_ requirements.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by Martin Tomes <li...@tomes.org>.
kfogel@collab.net wrote:
> Martin Tomes <li...@tomes.org> writes:
>
>>>Martin Tomes <li...@tomes.org> writes:
>>>
>>>>+ http:// or https:// url), you will require Neon.
>>>
>>>How did you generate this patch? The hunk above seems to make no
>>>changes -- it replaces text with completely identical text. Strange.
>>
>>I have emacs set to remove trailing space, I expect that's the
>>difference. I would have removed this hunk if I had noticed it!
> No, it's weirder than that, as the lines were *exactly* the same in
> the deleted and added portions, including trailing whitespace. Maybe
> if your mailer also removes trailing whitespace, that would explain
> it.
Maybe it does, I use thunderbird.
>>>>+ the script file explain how to use the script.
>>>
>>>Having a separate Prerequisites section seems like a very good idea.
>>>Most of the version requirements should say " or higher", I think.
>>>For example:
>>
>>I will do that, but I would like to update it prior to any releases so
>>it is accurate and works when a release happens!
> Not sure what you mean by that?...
Well, if I keep the information up to date then hopefully it will be
specifying the most up to date version of each package which works.
--
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the Win32 platform.
Posted by kf...@collab.net.
Martin Tomes <li...@tomes.org> writes:
> > Martin Tomes <li...@tomes.org> writes:
> >> + http:// or https:// url), you will require Neon.
> > How did you generate this patch? The hunk above seems to make no
> > changes -- it replaces text with completely identical text. Strange.
>
> I have emacs set to remove trailing space, I expect that's the
> difference. I would have removed this hunk if I had noticed it!
No, it's weirder than that, as the lines were *exactly* the same in
the deleted and added portions, including trailing whitespace. Maybe
if your mailer also removes trailing whitespace, that would explain
it.
> >>+ the script file explain how to use the script.
> > Having a separate Prerequisites section seems like a very good idea.
> > Most of the version requirements should say " or higher", I think.
> > For example:
>
> I will do that, but I would like to update it prior to any releases so
> it is accurate and works when a release happens!
Not sure what you mean by that?...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by Martin Tomes <li...@tomes.org>.
kfogel@collab.net wrote:
> Martin Tomes <li...@tomes.org> writes:
>>+ http:// or https:// url), you will require Neon.
> How did you generate this patch? The hunk above seems to make no
> changes -- it replaces text with completely identical text. Strange.
I have emacs set to remove trailing space, I expect that's the
difference. I would have removed this hunk if I had noticed it!
>>+ the script file explain how to use the script.
>
> Having a separate Prerequisites section seems like a very good idea.
>
> Most of the version requirements should say " or higher", I think.
> For example:
I will do that, but I would like to update it prior to any releases so
it is accurate and works when a release happens!
Martin.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the Win32 platform.
Posted by kf...@collab.net.
Martin Tomes <li...@tomes.org> writes:
> The new instructions are split into sections which describe what is
> needed, how to prepare the files (unpacking, environment etc.) and how
> to actually build the binaries with all available options turned on.
>
> * INSTALL
> Update Win32 build instructions.
Thanks! Some comments:
> Index: INSTALL
> ===================================================================
> --- INSTALL (revision 9468)
> +++ INSTALL (working copy)
> @@ -161,9 +161,9 @@
> 4. Neon library 0.24.5 (http://www.webdav.org/neon/)
>
> The Neon library allows a Subversion client to interact with remote
> - repositories over the Internet via a WebDAV based protocol. If you
> - want to use Subversion to connect to a server over ra_dav (via a
> - http:// or https:// url), you will require Neon.
> + repositories over the Internet via a WebDAV based protocol. If you
> + want to use Subversion to connect to a server over ra_dav (via a
> + http:// or https:// url), you will require Neon.
How did you generate this patch? The hunk above seems to make no
changes -- it replaces text with completely identical text. Strange.
> The Neon library source code can be installed in "./neon" if you
> want Subversion to build it. The source code is included with the
> @@ -578,134 +578,276 @@
> E. Building the Latest Source under Windows
> ----------------------------------------
>
> - (These instructions assume you have already installed Subversion
> - and checked out a Subversion working copy. See the section
> - "Bootstrapping from a Zip or Installer File under Windows" above
> - for more.)
> + E.1 Prerequisites
>
> - There is some support for building Subversion on Win32
> - platforms. The project files generated by gen-make.py are for
> - Microsoft Visual C++ 6.x; earlier versions of the compiler are
> - not supported. You'll also need a fairly recent version of the
> - Microsoft Platform SDK; the header files that come with MSVC 6.x
> - are too old.
> + * Visual Studio 6 with the latest service pack. It can be built
> + with Visual Studio 7 but these instructions assumes VS6.
> + * A recent Windows SDK, the one provided with Visual Studio 6 is
> + too old. You only need the 'Core SDK'. You can get it from MSDN
> + if you have it or from
> + http://www.microsoft.com/msdownload/platformsdk/sdkupdate/ if you
> + don't.
> + * Python 2.2, downloaded from http://www.python.org/ which is
> + used to generate the project files.
> + * Perl 5.8 from http://www.activestate.com/
> + * Neon 0.24.5, downloaded from
> + http://www.webdav.org/neon/neon-0.24.5.tar.gz which is required
> + for building the client components.
> + * Berkeley DB is required for support for local server components,
> + version 4.2.52 is available from
> + http://subversion.tigris.org/servlets/ProjectDocumentList as
> + db-4.2.52-win32.zip. For more information see Section I.5.
> + * Apache 2 source, downloaded from
> + http://httpd.apache.org/download.cgi, these instructions assume
> + version 2.0.49.
> + * Apache 2 msi install file, also from
> + http://httpd.apache.org/download.cgi (required for running the
> + tests)
> + * ZLib 1.1.4 binaries http://www.winimage.com/zLibDll/zlib114dll.zip and
> + sources http://www.gzip.org/zlib/zlib114.zip
> + * openssl-0.9.7d.tar.gz obtained from http://www.openssl.org/source/
> + * An assembler, e.g., nasm which is avaliable from
> + http://www.kernel.org/pub/software/devel/nasm/binaries/win32/
> + * The latest version of apr-util (see Section I.1) must be told
> + where to find the Berkeley DB include files and libraries. You
> + can do this with the w32locatedb.pl script (located in the
> + "build" directory in the apr-util sources), which modifies
> + apr-util's header and DSP files. The instructions at the top of
> + the script file explain how to use the script.
Having a separate Prerequisites section seems like a very good idea.
Most of the version requirements should say " or higher", I think.
For example:
* Neon 0.24.5 or higher. Download from
http://www.webdav.org/neon/neon-0.24.5.tar.gz.
Neon is required for building the client components.
(The original document has this problem, independent of your patch, of
course.)
I can't really evaluate the rest of the patch, as I don't build on
Windows myself, but it looks much more complete and detailed. Any
Windows users have any comments?
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by "D.J. Heap" <dj...@shadyvale.net>.
Martin Tomes wrote:
[snip]
>
>
> I have had some more feedback from Mark Phippard and he has made a
> couple of good points so I would like to make a couple of changes,
> unfortunately I cannot do that until tomorrow morning.
>
> Martin.
No problem, I'll watch for a new patch.
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by "D.J. Heap" <dj...@shadyvale.net>.
Martin Tomes wrote:
>> Log entry:
>> Update the instructions for building Subversion on the Win32 platform.
>>
>> The new instructions are split into sections which describe what is
>> needed, how to prepare the files (unpacking, environment etc.) and how
>> to actually build the binaries with all available options turned on.
>>
>> * INSTALL
>> Update Win32 build instructions.
>
>
> Sorry, this really is the last version of this file. Windoze is such a
> pain. I just ran through it using VMWare and found a couple of things
> which weren't quite right. Oh for a way to withdraw posts to a mailing
> list:-)
>
Committed in r9561, thanks!
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by Martin Tomes <li...@tomes.org>.
Jani Averbach wrote:
> On 2004-04-28 13:32+0100, Martin Tomes wrote:
>
>>Sorry, this really is the last version of this file.
>
> First of, thank you for doing this, and secondly, do you like to mention
> following information in your document?
>
> http://msdn.microsoft.com/visualc/vctoolkit2003/
You cannot use this to build Subversion as things currently stand as it
does not include msdev which is the build environment or nmake. You
would need to find a suitable make and write Makefiles for the Win32
build in order to use this.
--
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by Martin Tomes <li...@tomes.org>.
John Peacock wrote:
> Mark Phippard wrote:
>> I was going to take a look at this too (although I barely know what I
>> am doing). The first thing I have noticed is that the toolkit only
>> comes with the compiler and linker (CL and LINK) it does not come with
>> the NMAKE or MSDEV programs, both of which are used by the current
>> build process.
> nmake has been available for years as a standalone package:
>
> http://download.microsoft.com/download/vc15/Patch/1.52/W95/EN-US/Nmake15.exe
>
> but MSDEV is probably going to be a problem if it cannot be replaced in
> the build process.
You can generate nmake files from msdev but they are sometimes
sub-optimal! This is probably worth looking at though.
--
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the Win32
platform.
Posted by Mark Phippard <Ma...@softlanding.com>.
John Peacock <jp...@rowman.com> wrote on 04/28/2004 01:15:25 PM:
> nmake has been available for years as a standalone package:
>
>
http://download.microsoft.com/download/vc15/Patch/1.52/W95/EN-US/Nmake15.exe
>
> but MSDEV is probably going to be a problem if it cannot be replaced in
the
> build process.
>
Great! Thanks. I actually thought it might be available, I just hadn't
looked yet.
That URL is a tad suspicous though, since it is so old. Are you sure
there was no EULA that said if was just an update/fix for someone that
owned that version of VC++?
It just seems very odd that they would not have included it with the
toolkit if it were free.
It seems like MSDEV could be replaced with a batch file.
Mark
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by John Peacock <jp...@rowman.com>.
Mark Phippard wrote:
>
> I was going to take a look at this too (although I barely know what I am
> doing). The first thing I have noticed is that the toolkit only comes
> with the compiler and linker (CL and LINK) it does not come with the
> NMAKE or MSDEV programs, both of which are used by the current build
> process.
nmake has been available for years as a standalone package:
http://download.microsoft.com/download/vc15/Patch/1.52/W95/EN-US/Nmake15.exe
but MSDEV is probably going to be a problem if it cannot be replaced in the
build process.
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: [PATCH] Update build instructions for the 1.0.x branch on the Win32 platform.
Posted by Arild Fines <ar...@broadpark.no>.
Mark Phippard wrote:
> I was going to take a look at this too (although I barely know what I am
> doing). The first thing I have noticed is that the toolkit only comes
with
> the compiler and linker (CL and LINK) it does not come with the NMAKE or
> MSDEV programs, both of which are used by the current build process. So
> you would have to find a suitable make tool to replace NMAKE and then
> probably wrapper it all in a batch file that runs all of the makes. Also,
> it is possible the existing make files might have to be tweaked to handle
> differences between nmake and whatever make tool you used.
nmake *is* available in the .NET Framework SDK, though, which is also a free
download. But it would have been nice if MS could have provided it with the
toolkit release.
Also, the Rotor[1] source tree contains sources for nmake. I think they use
it for bootstrapping their build process on FreeBSD and OSX.
[1] http://sharedsourcecli.sscli.net/
--
Arild
AnkhSVN: http://ankhsvn.tigris.org
Blog: http://ankhsvn.com/blog
IRC: irc://irc.freenode.net/ankhsvn
"We've got to find out what people want from fire, how they relate to it,
what sort of image it has for them.' The crowd were tense. They were
expecting something wonderful from Ford.`Stick it up your nose,' he
said.`Which is precisely the sort of thing we need to know,' insisted the
girl, `Do people want fire that can be fitted nasally?'"
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the Win32
platform.
Posted by Mark Phippard <Ma...@softlanding.com>.
I was going to take a look at this too (although I barely know what I am
doing). The first thing I have noticed is that the toolkit only comes
with the compiler and linker (CL and LINK) it does not come with the NMAKE
or MSDEV programs, both of which are used by the current build process. So
you would have to find a suitable make tool to replace NMAKE and then
probably wrapper it all in a batch file that runs all of the makes. Also,
it is possible the existing make files might have to be tweaked to handle
differences between nmake and whatever make tool you used.
Does anyone know if there are settings that can be passed to gen-make.py
to generate "standard" make files that might work for this?
Finally to do a full build, something would have to be done to the Apache
build process to accomodate all of this. Maybe someone in the Apache
world is already working on this. Correct me if I am wrong, but I believe
you can build the complete Subversion client without building Apache. The
latter is only needed to be build the Apache server modules.
It would be nice if this could work with this compiler. I know I have
seen messages on this list in the past from some Subversion developers
that run on Linux that have said they have never messed around with the
Windows code simply because they did not have a Visual Studio license.
Personally, I am in MSDN so I have access to all of the tools.
Mark
Jani Averbach <ja...@jaa.iki.fi> wrote on 04/28/2004 12:35:40 PM:
> On 2004-04-28 13:32+0100, Martin Tomes wrote:
> >
> > Sorry, this really is the last version of this file.
>
> First of, thank you for doing this, and secondly, do you like to mention
> following information in your document?
>
> http://msdn.microsoft.com/visualc/vctoolkit2003/
>
> ---8<---
>
> Visual C++ Toolkit 2003 Q&A
>
> What is the Visual C++ Toolkit 2003?
>
> The Visual C++ Toolkit is a free edition of Microsoft.s
> professional Visual C++ optimizing compiler and standard libraries
> . the same optimizing compiler and standard libraries that ship in
> Visual Studio .NET 2003 Professional!
>
> Are there any restrictions on how I use the Visual C++ Toolkit?
>
> In general, no. You may use the Toolkit to build C++ -based
> applications, and you may redistribute those applications. Please
> read the End User License Agreement (EULA), included with the
> Toolkit, for complete details.
>
> ---8<---
>
> However, I haven't tried your instructions with VCToolKit2003, so I
> don't know if they work or not.
>
>
> > + * Visual Studio 6 and service pack. It can be built with
> Visual Studio
> > + 7 but these instructions assumes VS6.
> > + * A recent Windows SDK, the one provided with Visual Studio 6
is
> > + too old. You only need the 'Core SDK'. You can get it from
MSDN
> > + if you have it or from
> > + http://www.microsoft.com/msdownload/platformsdk/sdkupdate/ if
you
> > + don't.
>
> ...
>
> Br, Jani
>
> --
> Jani Averbach
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
Re: [PATCH] Update build instructions for the 1.0.x branch on the Win32 platform.
Posted by Jani Averbach <ja...@jaa.iki.fi>.
On 2004-04-28 13:32+0100, Martin Tomes wrote:
>
> Sorry, this really is the last version of this file.
First of, thank you for doing this, and secondly, do you like to mention
following information in your document?
http://msdn.microsoft.com/visualc/vctoolkit2003/
---8<---
Visual C++ Toolkit 2003 Q&A
What is the Visual C++ Toolkit 2003?
The Visual C++ Toolkit is a free edition of Microsoft.s
professional Visual C++ optimizing compiler and standard libraries
. the same optimizing compiler and standard libraries that ship in
Visual Studio .NET 2003 Professional!
Are there any restrictions on how I use the Visual C++ Toolkit?
In general, no. You may use the Toolkit to build C++ -based
applications, and you may redistribute those applications. Please
read the End User License Agreement (EULA), included with the
Toolkit, for complete details.
---8<---
However, I haven't tried your instructions with VCToolKit2003, so I
don't know if they work or not.
> + * Visual Studio 6 and service pack. It can be built with Visual Studio
> + 7 but these instructions assumes VS6.
> + * A recent Windows SDK, the one provided with Visual Studio 6 is
> + too old. You only need the 'Core SDK'. You can get it from MSDN
> + if you have it or from
> + http://www.microsoft.com/msdownload/platformsdk/sdkupdate/ if you
> + don't.
...
Br, Jani
--
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by Martin Tomes <li...@tomes.org>.
> Log entry:
> Update the instructions for building Subversion on the Win32 platform.
>
> The new instructions are split into sections which describe what is
> needed, how to prepare the files (unpacking, environment etc.) and how
> to actually build the binaries with all available options turned on.
>
> * INSTALL
> Update Win32 build instructions.
Sorry, this really is the last version of this file. Windoze is such a pain. I just ran through it
using VMWare and found a couple of things which weren't quite right. Oh for a way to withdraw posts
to a mailing list:-)
--
Martin Tomes
echo 'Martin x Tomes at controls x eurotherm x co x uk'\
| sed -e 's/ x /\./g' -e 's/ at /@/'
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by Martin Tomes <li...@tomes.org>.
Martin Tomes wrote:
> I have had some more feedback from Mark Phippard and he has made a
> couple of good points so I would like to make a couple of changes,
> unfortunately I cannot do that until tomorrow morning.
This should be it! Diff is against checkout of r9468, last changed at r9386. Many thanks to Mark
Phippard who tested it on a fresh VMWare install of Windows a couple of times.
Log entry:
Update the instructions for building Subversion on the Win32 platform.
The new instructions are split into sections which describe what is needed, how to prepare the files
(unpacking, environment etc.) and how to actually build the binaries with all available options
turned on.
* INSTALL
Update Win32 build instructions.
--
Martin Tomes
echo 'Martin x Tomes at controls x eurotherm x co x uk'\
| sed -e 's/ x /\./g' -e 's/ at /@/'
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by Martin Tomes <li...@tomes.org>.
kfogel@collab.net wrote:
> Martin Tomes <li...@tomes.org> writes:
>
>>It won't work for the trunk. My next job is to produce a patch which
>>will describe how to build the trunk. There are issues like libapr
>>being a dll now and the addition of gettext for i10n.
>
>
> Ah, sorry. Then yeah, just commit it into 1.0.x, D.J., and the trunk
> patch will be a separate change.
I have had some more feedback from Mark Phippard and he has made a
couple of good points so I would like to make a couple of changes,
unfortunately I cannot do that until tomorrow morning.
Martin.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the Win32 platform.
Posted by kf...@collab.net.
Martin Tomes <li...@tomes.org> writes:
> It won't work for the trunk. My next job is to produce a patch which
> will describe how to build the trunk. There are issues like libapr
> being a dll now and the addition of gettext for i10n.
Ah, sorry. Then yeah, just commit it into 1.0.x, D.J., and the trunk
patch will be a separate change.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by Martin Tomes <li...@tomes.org>.
kfogel@collab.net wrote:
> "D.J. Heap" <dj...@shadyvale.net> writes:
>
>>However, since this is for 1.0.x, I don't want to commit it to trunk,
>>obviously, and I'm not sure whether or not this kind of patch requires
>>voting on for the 1.0.x branch...Karl (or someone), should I put it up
>>for voting in the STATUS file with a pointer to the email or what?
>
> Is there some reason we wouldn't commit it to trunk first, then merge
> the change over to 1.0.x? The change is as good on trunk as it is on
> 1.0.x, I would think.
It won't work for the trunk. My next job is to produce a patch which will describe how to build the
trunk. There are issues like libapr being a dll now and the addition of gettext for i10n.
--
Martin Tomes
echo 'Martin x Tomes at controls x eurotherm x co x uk'\
| sed -e 's/ x /\./g' -e 's/ at /@/'
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the Win32 platform.
Posted by kf...@collab.net.
"D.J. Heap" <dj...@shadyvale.net> writes:
> However, since this is for 1.0.x, I don't want to commit it to trunk,
> obviously, and I'm not sure whether or not this kind of patch requires
> voting on for the 1.0.x branch...Karl (or someone), should I put it up
> for voting in the STATUS file with a pointer to the email or what?
Is there some reason we wouldn't commit it to trunk first, then merge
the change over to 1.0.x? The change is as good on trunk as it is on
1.0.x, I would think.
The normal way to do this is to commit it to trunk, then either add an
item in the STATUS file to vote on merging the change, or merge it
over directly if voting is not required.
Martin Tomes wrote:
> My understanding is that as this will not affect the code at all then
> it can go in without going through the STATUS file procedure. In the
> run up to the 1.0 release patches against documentation were accepted
> right up to the release date.
That's right, in this case voting is not required, so D.J. can just
merge the trunk change right into 1.0.x. See the section "Stabilizing
and maintaining releases" in the HACKING file for details about this.
Sometimes, even when voting isn't technically required, it's still a
good idea to give people a chance to review the change. In this case,
I don't think there's any benefit to waiting -- the change is a clear
improvement, so might as well get it in. People can still review it
and make more tweaks, after all.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by Martin Tomes <li...@tomes.org>.
D.J. Heap wrote:
> Martin Tomes wrote:
>
>> Update the instructions for building Subversion on the Win32 platform.
> However, since this is for 1.0.x, I don't want to commit it to trunk,
> obviously, and I'm not sure whether or not this kind of patch requires
> voting on for the 1.0.x branch...Karl (or someone), should I put it up
> for voting in the STATUS file with a pointer to the email or what?
My understanding is that as this will not affect the code at all then it can go in without going
through the STATUS file procedure. In the run up to the 1.0 release patches against documentation
were accepted right up to the release date.
--
Martin Tomes
echo 'Martin x Tomes at controls x eurotherm x co x uk'\
| sed -e 's/ x /\./g' -e 's/ at /@/'
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform.
Posted by "D.J. Heap" <dj...@shadyvale.net>.
Martin Tomes wrote:
> Update the instructions for building Subversion on the Win32 platform.
>
> The new instructions are split into sections which describe what is
> needed, how to prepare the files (unpacking, environment etc.) and how
> to actually build the binaries with all available options turned on.
>
> * INSTALL
> Update Win32 build instructions.
>
[snip]
+ * gen-make.py is supposed to configure the build to use apr* from
+ the Apache build, it doens't work so the built apr* files have
[snip]
Should be "doesn't" on the above line...
This looks pretty good aside from Karl's comment on minimum required
versions (which I agree with, also) and the small typo. If you want to
submit an updated patch, feel free, please. This is better than what
we've got, though...thanks!
However, since this is for 1.0.x, I don't want to commit it to trunk,
obviously, and I'm not sure whether or not this kind of patch requires
voting on for the 1.0.x branch...Karl (or someone), should I put it up
for voting in the STATUS file with a pointer to the email or what?
I've been kind of ignoring the 1.0.x branch and release process because
I can barely keep up with trunk, so I'm foggy on how to deal with this...
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update build instructions for the 1.0.x branch on the
Win32 platform - Final attempt?
Posted by Martin Tomes <li...@tomes.org>.
Update the instructions for building Subversion on the Win32 platform.
The new instructions are split into sections which describe what is
needed, how to prepare the files (unpacking, environment etc.) and how
to actually build the binaries with all available options turned on.
* INSTALL
Update Win32 build instructions.
--
Martin Tomes
echo 'Martin x Tomes at controls x eurotherm x co x uk'\
| sed -e 's/ x /\./g' -e 's/ at /@/'