JehanneOS/newlib
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

* how-programming.texinfo: Remove obsolete w32api instructions and add some

Browse Source 
words about unpacking net release .tar.bz2.
This commit is contained in:
Christopher Faylor 2005-01-22 03:53:38 +00:00
parent b87d70463e
commit f2d6aeea17
2 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
winsup/doc/ChangeLog
View File

@ -1,3 +1,8 @@
2005-01-21 Christopher Faylor <cgf@timesys.com>
* how-programming.texinfo: Remove obsolete w32api instructions and add
some words about unpacking net release .tar.bz2.
2004-12-30 Joshua Daniel Franklin <joshuadfranklin@yahoo.com> 2004-12-30 Joshua Daniel Franklin <joshuadfranklin@yahoo.com>
* path.sgml: Encode programming example with CDATA. * path.sgml: Encode programming example with CDATA.

16
winsup/doc/how-programming.texinfo
View File

@ -309,15 +309,11 @@ Ideally, you should check out what you need from CVS
method} for acquiring the sources. Otherwise, you can install the method} for acquiring the sources. Otherwise, you can install the
appropriate source packages from the cygwin distribution. appropriate source packages from the cygwin distribution.
As of this writing, you need to install at least the cygwin source If you are trying to duplicate a cygwin release then you should just
package and the w32api source package. The winsup source package download the corresponding source package and use "tar xjf" to unpack
should be extracted first and the w32api source directory should it. This will unpack the sources into a directory named cygwin-x.y.z-n,
be extracted into the resulting 'winsup' directory. Then rename where x.y.z-n correspond to the version numbering of the tar.bz2
w32api-whatever to w32api. package.
It is possible that the cygwin source package may require a newer
version of the w32api package since the release of the packages is
not always in lock step (another reason to just use CVS).
You @emph{must} build cygwin in a separate directory from the source. You @emph{must} build cygwin in a separate directory from the source.
So, create something like a /obj directory. You'll be performing So, create something like a /obj directory. You'll be performing
@ -338,7 +334,7 @@ package named docbook-utils should get you most of what you need. For
more information on building the documentation, see the README included more information on building the documentation, see the README included
in the cygwin-doc package. in the cygwin-doc package.
To check a cygwin1.dll, run "make check" in the winsup/cygwin directory. To check a cygwin1.dll, run "make check" in the winsup/testsuite directory.
If that works, install everything @emph{except} the dll (if you can). If that works, install everything @emph{except} the dll (if you can).
Then, close down all cygwin programs (including bash windows, inetd, Then, close down all cygwin programs (including bash windows, inetd,
etc.), save your old dll, and copy the new dll to the correct place. etc.), save your old dll, and copy the new dll to the correct place.