From: Joachim W. <wu...@cr...> - 2002-11-28 06:48:43
|
Hi Olof: > The sys/win32/msdev port of plplot doesn't make use of configure, just > nmake as mentioned in the INSTALL.txt file. How did you manage to run > configure? Did you use cygwin?=20 Well, from the documentation the relation between the main level (plplot and plplot/tmp) and the windows-specific part (plplot/sys/win32/msdev) was not quite clear to me. Therefore I first built the whole thing on the main level, using cygwin, and then I proceeded with the windows = part. Question: could I completely leave out the first step if I only want to build plplot.lib for usage in windows programs ? Another remark, just for documentation (because mails we exchanged = earlier did not make it into the archive, being directed to the mailing list = only through CC): Several of the windows-specific installation steps can be made in the cygwin bash shell, instead of the DOS shell. This is, however, not true for step 4.5 "nmake plplib.mak". As you quoted from a mail by Wayne Richardson: "More importantly, the settings to run nmake are contained in the file Vcvars32.bat which is in the VC98\bin directory. Hence by=20 either first executing Vcvars32.bat, or placing it in the autoexec.bat file, it is possible to make nmake work properly." Translating these settings into bash will at least be cumbersome, given the idiotic = Windows path names with blanks and lots of backslashes. Rebuilding plplot.lib with double precision (shouldn=B4t we call it = plplotd.lib ?) was indeed quite straightforward: in plplot/sys/win32/msdev/makefile after > #define PLPLOT_VERSION "5.1.0" I just added the line > #define PL_DOUBLE 1 After going through the whole build procedure, everything seems = consistent. - Joachim=20 |