drew
/
acadia-newlib
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Tidied up formatting a bit. 

New entries:
	How do I convert between Windows and UNIX paths?
	Why are compiled executables so huge?!?
This commit is contained in:
David Starks-Browning 2000-06-14 16:34:57 +00:00
parent 3092135d8c
commit a9ba336498
1 changed files with 24 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
winsup/doc/how.texinfo
View File

@ -145,6 +145,22 @@ additional Cygwin applications that are not part of the core net
release. (That is, anything not found in an ftp mirror of @code{latest} release. (That is, anything not found in an ftp mirror of @code{latest}
and installed by @code{setup.exe}.) and installed by @code{setup.exe}.)
@subsection How do I convert between Windows and UNIX paths?
Use the 'cygpath' utility. Type '@code{cygpath}' with no arguments to
get usage information. For example (on my installation):
@example
bash$ cygpath --windows ~/.bashrc
D:\starksb\.bashrc
bash$ cygpath --unix C:/cygwin/bin/cygwin.bat
/usr/bin/cygwin.bat
bash$ cygpath --unix C:\\cygwin\\bin\\cygwin.bat
/usr/bin/cygwin.bat
@end example
Note that bash interprets the backslash '\' as an escape character, so
you must type it twice in the bash shell if you want it to be recognised
as such.
@subsection How do I set /etc up? @subsection How do I set /etc up?
@strong{(Please note: This section has not yet been updated for the latest @strong{(Please note: This section has not yet been updated for the latest
@ -180,13 +196,10 @@ used by Cygwin tools.
In particular, bash interprets space as a word separator. You would have In particular, bash interprets space as a word separator. You would have
to quote a filename containing spaces, or escape the space character. to quote a filename containing spaces, or escape the space character.
For example: For example:
@example @example
bash-2.03$ cd '/cygdrive/c/Program Files' bash-2.03$ cd '/cygdrive/c/Program Files'
@end example @end example
or or
@example @example
bash-2.03$ cd /cygdrive/c/Program\ Files bash-2.03$ cd /cygdrive/c/Program\ Files
@end example @end example
@ -269,21 +282,17 @@ In some applications (notably bash), you can use the familiar windows
backward-slashes ('\'). (But see the warning below!) This maps in the backward-slashes ('\'). (But see the warning below!) This maps in the
obvious way to the Windows path, but will be converted internally to use obvious way to the Windows path, but will be converted internally to use
the Cygwin path, following mounts (default or explicit). For example: the Cygwin path, following mounts (default or explicit). For example:
@example @example
bash-2.03$ cd C:/Windows bash-2.03$ cd C:/Windows
bash-2.03$ pwd bash-2.03$ pwd
/cygdrive/c/Windows /cygdrive/c/Windows
@end example @end example
and and
@example @example
bash-2.03$ cd C:/cygwin bash-2.03$ cd C:/cygwin
bash-2.03$ pwd bash-2.03$ pwd
/ /
@end example @end example
for a default setup. (You could also use backward-slashes in the for a default setup. (You could also use backward-slashes in the
Windows path, but these would have to be escaped from the shell.) Windows path, but these would have to be escaped from the shell.)
@ -296,13 +305,11 @@ get there.
You can avoid the ambiguity of Windows paths, and avoid typing You can avoid the ambiguity of Windows paths, and avoid typing
"/cygdrive", by explicitly mounting drives to posix paths. For example: "/cygdrive", by explicitly mounting drives to posix paths. For example:
@example @example
bash$ mkdir /c bash$ mkdir /c
bash$ mount c:/ /c bash$ mount c:/ /c
bash$ ls /c bash$ ls /c
@end example @end example
Note that you only need to mount drives once. The mapping is kept Note that you only need to mount drives once. The mapping is kept
in the registry so mounts stay valid pretty much indefinitely. in the registry so mounts stay valid pretty much indefinitely.
You can only get rid of them with umount (or the registry editor). You can only get rid of them with umount (or the registry editor).
@ -469,7 +476,6 @@ read those info files. This is how you do it:
bash$ cd /usr/info bash$ cd /usr/info
bash$ for f in *.info ; do install-info $f dir ; done bash$ for f in *.info ; do install-info $f dir ; done
@end example @end example
This may generate warnings: This may generate warnings:
@example @example
install-info: warning: no info dir entry in `gzip.info' install-info: warning: no info dir entry in `gzip.info'
@ -839,6 +845,14 @@ If not, you must do so.
@section Programming Questions @section Programming Questions
@subsection Why are compiled executables so huge?!?
By default, gcc compiles in all symbols. You'll also find that gcc
creates large executables on UNIX.
If that bothers you, just use the 'strip' program, part of the binutils
package.
@subsection Why is gcc failing? @subsection Why is gcc failing?
@strong{(Please note: This section has not yet been updated for the latest @strong{(Please note: This section has not yet been updated for the latest