Apache OpenOffice (AOO) Bugzilla – Issue 9912
Documentation for 643C Windows build needs some changes
Last modified: 2003-05-10 11:35:25 UTC
The documentation for the 643C Windows build on: http://www.openoffice.org/dev_docs/source/build_windows.html#BuildRequirements needs some changes. If you use the current version of cygwin you have to make sure that awk.exe, gunzip.exe and tar.exe are *NOT* cygwin symlinks. Check with ls -l /bin/<prog> if they are symlinks, and in case they are, remove the symlink and copy the program it points to to this name. In the /build_windows.html#GeneratingtheBuildEnvironmentandBuildTools part of the file all instructions with "Please enter the ..." want to have the "/cygdrive/c/path/to/file" notation in the case of the 643 build. This does not depend on new/old cygwin. There is a typo in: "Note the change in pathname notation. Since the cygwin bash shell won't accept backslashes, paths have to be typed in a cygwin bash notation which is //C/path/to/file or /cygwin/c/path/to/file for b-20 or new cygwin tools, respectively, instead of C:\path\to\file." It has to be /cygdrive/ instead of /cygwin/. We should use different links for the build instruchtions for OOo 1.0.x and 643C and up. This would make things easier.
Please remove the 'run autoconf' from teh document as well.
In principle I agree with splitting the build docs into two (one for developer and one for stable branch). Although that should converge again. I hope I find time to do that before the next stable release. In the meantime, I fixed the errors you've found.
And another problem: The cygwin unzip.exe is not working for the w32/4nt build, you have to use the native w32 version, but configure just checks for a unzip.exe in your path! !!!!!!!!!!!!!! Make sure that the first unzip.exe in your path *IS* the native w32 version. E.g. delete the unzip.exe in your cygwin /bin directory and copy the InfoZip version to this place. !!!!!!!!!!!!!! (I'll try to provide some magic for configure to catch this)
consider a negative check like unzip --version...
Another small change: The homepage of Info-ZIP is alive, it is: http://www.info-zip.org Version 2.3 of zip is released since December 1999, I'd like to change the build requirements to this version, since the patch for configure I send to Ken is only tested with the 2.3 version.
>The cygwin unzip.exe is not working for the w32/4nt build, you have >to use the native w32 version, but configure just checks for a >unzip.exe in your path! Correction to myself: Not unzip.exe is the problem, but zip.exe. !!!!!!!!!!!!!! Make sure that the first zip.exe in your path *IS* the native w32 version. E.g. delete the zip.exe in your cygwin /bin directory and copy the InfoZip version to this place. !!!!!!!!!!!!!!
The zip-related part of the build docs is now as below. I will change it again in the future if configure can take care of it, or when the 4NT shell becomes obsolete. <li> <CODE>zip.exe</CODE> Version 2.2 or higher, and <CODE>unzip.exe</CODE>. If you do not have these already, you can download them from <a href="http://www.info-zip.org">www.info-zip.org</a>. Note: The cygwin zip.exe is not working for the build under the 4NT shell. You have to use the native w32 version. Make sure that the first zip.exe in your path is the native w32 version, e.g. rename or delete the zip.exe in your cygwin /bin directory and copy the InfoZip version to this place. This issue should become obsolete once the 4NT shell is no longer a requirement for the build environment. </li>
The cvs part of the Build Requirements page is misleading. What is runsocks? We should remove the cvs part and insert an link to: http://www.openoffice.org/dev_docs/source/get_source.html
JA: re-prioritized according to new priority guide lines
Acutally, the build documentation was initially a summary of a bigger document of which the above URL is one part. We wanted to have a build guide on one single html page and only a few printed pages. In other words: a much more compact guide. Therefore, I personally am opposed to link to these old URLs. What is misleading in the current description? socks: see http://www.socks.permeo.com/
> Acutally, the build documentation was initially a summary of > a bigger document of which the above URL is one part. We wanted > to have a build guide on one single html page and only a few > printed pages. In other words: a much more compact guide. > Therefore, I personally am opposed to link to these old URLs. OK! But <http://www.openoffice.org/dev_docs/source/get_source.html> is a link directly from <http://tools.openoffice.de> > What is misleading in the current description? I don't need socks, I just start a cygwin shell and enter my cvs commands. > socks: see http://www.socks.permeo.com/ Not needed when you use a current cygwin environement, maybe usefull for cygwin b2x ?? We have a very good cvs help for cygwin on this server already, <http://website.openoffice.org/support/en/howtos/1.html> describes how to get cygwin, setup ssh tunnels and use cvs. Volker
small updates in respect to runsocks and link to cygwin help. I keep the issue open for future changes, for example I want to get rid of the references to older builds in which the old cygwin shell is needed. I think we don't need to encourage people to build old versions
Armin, can you please tell me where to find the master file (build_template.html). It's easier to post a patch agoinst the true file. Volker
Just an info! There now is a document in the Cygwin User's Guide describing the use of setup.exe: <http://cygwin.com/cygwin-ug-net/setup-net.html>
try: export CVSROOT=:pserver:vq@localhost:/cvs cvs co -A www
Hmm, well, I asked about the build_template.html because the first lines of "www/www/dev_docs/source/build_windows.html" say: <!-- PLEASE DO NOT COMMIT EDITED VERSION OF THE FILES BUILD_LINUX.HTML, BUILD_SOLARIS.HTML AND BUILD_WINDOWS.HTML. EDIT THE FILE BUILD_TEMPLATE INSTEAD AND USE ./MKBUILDDOC TO GENERATE THE PLATFORM SPECIFIC BUILD DOCUMENT--> Probably Armin doesn't keep this file in cvs.
As cws_srx644_ooo20030412 is now buildable without 4NT I tried to document the changes in build_template.html. These changes also remove all text concerning the interactive queries from the build instructions. See issue 12872. Attached are the patch for build_template.html and the generated build_windows.html. Please check for consistency and typing/spelling/grammar errors. I don't think this is the best solution, I'd prefer a build_windows.html for the W32-4NT build and a build_cygwin.html for the W32-tcsh build. Opinions?
Created attachment 5381 [details] Patch for build_template.html
Created attachment 5382 [details] Generated build_windows.html
Don't use this patches, use the patches from issue 13097 instead.
As suggested in the tools mailing list, it is probably a better idea to split this windows document into two separate build docs - one for win+4nt and one for win tcsh. At the end of the day, we want to get rid (not support) win+4nt anymore anyway, because 4nt is not free. about the build_<platform>.html file header remark: I just wanted to avoid people checking in new versions of these files directly but use the template instead. I wanted to avoid that after time the three documents get a different structure. Since the build experience is still more or less the same for all three platforms, the build docs should keep the same, too. That is all my opinion. What do you think?
> As suggested in the tools mailing list, it is probably a better > idea to split this windows document into two separate build docs - > one for win+4nt and one for win tcsh. At the end of the day, we > want to get rid (not support) win+4nt anymore anyway, because 4nt > is not free. 100% agreed. > about the build_<platform>.html file header remark: > I just wanted to avoid people checking in new versions of these > files directly but use the template instead. I wanted to avoid > that after time the three documents get a different structure. > Since the build experience is still more or less the same for > all three platforms, the build docs should keep the same, too. Yes, issue 13097 already contains a patch for mkbuilddoc and one for build_template to use linux, solaris, windows and win_tcsh. > That is all my opinion. What do you think? It's my opinion too. Go for it!
retargeting
Everyting is comitted
close