|
From: David B. <dav...@da...> - 2006-11-23 14:16:17
|
On Nov 23, 2006, at 8:02 AM, John Edwards wrote: > Hi David, > > Thank you very much for your quick reply. > >> I'm not aware of anything special about using gifplot on Windows--- >> it's basically just a standalone library that compiles without any >> other dependencies. > > Please excuse my ignorance but there are two makefiles in > C:\swig\Examples\GIFPlot> and C:\swig\Examples\GIFPlot\Lib>. I > tried the > following in each folder : gmake -f makefile.in and got the following > results : You definitely don't want to use the 'Makefile.in' files---those are inputs to the configure script which should create proper makefiles called 'makefile' in that directory. Since I don't maintain the Windows version of SWIG, I'm not exactly sure how this gets set up under cygwin, but I know for certain that you don't use the 'makefile.in' files. > I have both Microsoft and Borland compilers installed. I am sure > that I am > missing something pretty basic but I am not sure what. At one point, far, far in the past, I thought the GIFPlot example included makefiles set up for using nmake with Visual C++ (checking....). Yes, these seem to be part of the SWIG-1.1 distribution. If you can't get things to work normally, you might download an old SWIG version (1.1-883 perhaps), look in the GIFPlot directory and copy the makefile.msc files from GIFPlot/Lib, GIFPlot/ Python, etc. You'll probably have to tweak them a bit, but it might be a starter. Cheers, Dave |