Changeset 280 in kBuild for branches/GNU/src/gmake/README.W32.template
- Timestamp:
- May 16, 2005 4:54:02 PM (20 years ago)
- Location:
- branches/GNU/src/gmake
- Files:
-
- 2 edited
-
. (modified) (1 prop)
-
README.W32.template (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
branches/GNU/src/gmake
- Property svn:ignore
-
old new 34 34 README.DOS 35 35 README.W32 36 README.OS2 36 37 aclocal.m4 37 38 autom4te.cache
-
- Property svn:ignore
-
branches/GNU/src/gmake/README.W32.template
r54 r280 6 6 Tulloh, who is also the author of this README. 7 7 8 To build with nmake on Windows NT, Windows 95, or Windows 98:8 To build with nmake on MS-Windows: 9 9 10 10 1. Make sure cl.exe is in your %Path%. Example: … … 64 64 There are very few true ports of Bourne shell for NT right now. 65 65 There is a version of GNU bash available from Cygnus "Cygwin" 66 porting effort (http:// sourceware.cygnus.com/cygwin).66 porting effort (http://www.cygwin.com/). 67 67 Other possibilities are the MKS version of sh.exe, or building 68 68 your own with a package like NutCracker (DataFocus) or Portage 69 (Consensys). 69 (Consensys). Also MinGW includes sh (http://mingw.org/). 70 70 71 71 GNU make and brain-dead shells (BATCH_MODE_ONLY_SHELL): 72 72 73 Some versions of Bourne shell do esnot behave well when invoked73 Some versions of Bourne shell do not behave well when invoked 74 74 as 'sh -c' from CreateProcess(). The main problem is they seem 75 75 to have a hard time handling quoted strings correctly. This can … … 80 80 a batch mode. When BATCH_MODE_ONLY_SHELL is defined at compile 81 81 time, make forces all command lines to be executed via script 82 files instead of by command line. 82 files instead of by command line. In this mode you must have a 83 working sh.exe in order to use parallel builds (-j). 83 84 84 85 A native Windows32 system with no Bourne shell will also run 85 86 in batch mode. All command lines will be put into batch files 86 and executed via $(COMSPEC) (%COMSPEC%). 87 and executed via $(COMSPEC) (%COMSPEC%). Note that parallel 88 builds (-j) require a working Bourne shell; they will not work 89 with COM. 87 90 88 91 GNU make and Cygnus GNU Windows32 tools: … … 129 132 specification of paths. Make is able to figure out the intended 130 133 result and convert the paths internally to the format needed 131 when interacting with the operating system. 134 when interacting with the operating system, providing the path 135 is not within quotes, e.g. "x:/test/test.c". 132 136 133 137 You are encouraged to use colon as the separator character. … … 165 169 166 170 Unlike Unix, Windows 95/NT systems encourage pathnames which 167 contain white space (e.g. C:\Program Files\). These sorts of pathnames 168 are legal under Unix too, but are never encouraged. There is 169 at least one place in make (VPATH/vpath handling) where paths 170 containing white space will simply not work. There may be others 171 too. I chose to not try and port make in such a way so that 172 these sorts of paths could be handled. I offer these suggestions 173 as workarounds: 174 175 1. Use 8.3 notation 171 contain white space (e.g. C:\Program Files\). These sorts of 172 pathnames are legal under Unix too, but are never encouraged. 173 There is at least one place in make (VPATH/vpath handling) where 174 paths containing white space will simply not work. There may be 175 others too. I chose to not try and port make in such a way so 176 that these sorts of paths could be handled. I offer these 177 suggestions as workarounds: 178 179 1. Use 8.3 notation. i.e. "x:/long~1/", which is actually 180 "x:\longpathtest". Type "dir /x" to view these filenames 181 within the cmd.exe shell. 176 182 2. Rename the directory so it does not contain white space. 177 183
Note:
See TracChangeset
for help on using the changeset viewer.
