From: Gurusamy Sarathy Date: Sun, 29 Nov 1998 19:13:52 +0000 (+0000) Subject: explain various win32 build caveats more clearly X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=a8deba26610ac9d6097c62e020502f4cc7ee6576;p=p5sagit%2Fp5-mst-13.2.git explain various win32 build caveats more clearly p4raw-id: //depot/perl@2391 --- diff --git a/README.win32 b/README.win32 index 7fcc58f..099c881 100644 --- a/README.win32 +++ b/README.win32 @@ -75,6 +75,9 @@ your mileage may vary. The surest way to build it is on WindowsNT, using the cmd shell. +Make sure the path to the build directory does not contain spaces. The +build usually works in this circumstance, but some tests will fail. + =item Borland C++ If you are using the Borland compiler, you will need dmake, a freely @@ -182,7 +185,14 @@ Perl will also build without des_fcrypt(), but the crypt() builtin will fail at run time. You will also have to make sure CCHOME points to wherever you installed -your compiler. +your compiler. Make sure this path has no spaces in it. If you +insist on spaces in your path names, there is no telling what else +will fail, but you can try putting the path in double quotes. Some +parts of perl try to accomodate that, but not all pieces do. + +The default value for CCHOME in the makefiles for Visual C++ +may not be correct if you have a version later than 5.2. Make +sure the default exists and is valid. Other options are explained in the makefiles. Be sure to read the instructions carefully. @@ -223,9 +233,10 @@ Type "dmake test" (or "nmake test"). This will run most of the tests from the testsuite (many tests will be skipped, and but no test should fail). If some tests do fail, it may be because you are using a different command -shell than the native "cmd.exe". +shell than the native "cmd.exe", or because you are building from a path +that contains spaces. So don't do that. -If you used the Borland compiler, you may see a failure in op/taint.t +If you're using the Borland compiler, you may see a failure in op/taint.t arising from the inability to find the Borland Runtime DLLs on the system default path. You will need to copy the DLLs reported by the messages from where Borland chose to install it, into the Windows system directory @@ -473,7 +484,7 @@ all of the ActiveState extensions and most other Win32 extensions from CPAN in source form, along with many added bugfixes, and with MakeMaker support. This bundle is available at: - http://www.perl.com/CPAN/authors/id/GSAR/libwin32-0.12.zip + http://www.perl.com/CPAN/authors/id/GSAR/libwin32-0.14.zip See the README in that distribution for building and installation instructions. Look for later versions that may be available at the @@ -707,7 +718,7 @@ Borland support was added in 5.004_01 (Gurusamy Sarathy). GCC/mingw32 support was added in 5.005 (Nick Ing-Simmons). -Last updated: 22 September 1998 +Last updated: 29 November 1998 =cut diff --git a/win32/Makefile b/win32/Makefile index be10a08..231f6dc 100644 --- a/win32/Makefile +++ b/win32/Makefile @@ -113,6 +113,11 @@ INST_VER = \5.00553 # Some versions of Visual C don't define MSVCDIR in the environment, # so you may have to set CCHOME explicitly. # +# If the path contains spaces, you can try putting it in double +# quotes, but support for this is not well-tested, and various +# other things may break, so you're kinda on your own if you are +# into specious paths. :-) +# #CCHOME = f:\msvc20 CCHOME = $(MSVCDIR) CCINCDIR = $(CCHOME)\include diff --git a/win32/makefile.mk b/win32/makefile.mk index e74dc68..8df1abb 100644 --- a/win32/makefile.mk +++ b/win32/makefile.mk @@ -124,6 +124,11 @@ CCTYPE *= BORLAND # Some versions of Visual C don't define MSVCDIR in the environment, # so you may have to set CCHOME explicitly. # +# If the path contains spaces, you can try putting it in double +# quotes, but support for this is not well-tested, and various +# other things may break, so you're kinda on your own if you are +# into specious paths. :-) +# CCHOME *= C:\bc5 #CCHOME *= $(MSVCDIR) #CCHOME *= D:\packages\mingw32