Alan W. Irwin wrote:
On 2007-01-11 08:45+0100 Arjen Markus wrote:
I checked the entire directory structure: there is only one file matching
cygfreetype*.dll
and that is cygfreetype-9.dll.
Hi Arjen:
One way cygfreetype-6.dll could still be interfering is if one of the system
librari
On 2007-01-11 08:45+0100 Arjen Markus wrote:
> I checked the entire directory structure: there is only one file matching
> cygfreetype*.dll
> and that is cygfreetype-9.dll.
Hi Arjen:
One way cygfreetype-6.dll could still be interfering is if one of the system
libraries required by PLplot is out
Alan W. Irwin wrote:
I rarely if ever test the combination of -DBUILD_TEST=ON
-DBUILD_SHARED_LIBS=OFF on Linux, but your error report inspired me to try
the combination, and it appears to work fine. Of course,
python, java, and octave (which require a shared libraries build) were OFF,
but both
Jim Dishaw wrote:
>Something is not quite right with using the Visual Studio compiler
>and the CMake build of plplot. I can build and successfully use
>plplot on win32 with the VS compiler if I use the sys/win32/msdev
>build method.
>
>I've made some changes to bindings/f77/CMakeLists.txt,
>bindi
Arjen Markus <[EMAIL PROTECTED]> writes:
> Windows/MSVC 6.0+CVF:
> - Building the library is no problem
> - Building the Fortran examples fails - because of a conflict with
> MSVCRTD.DLL
> (conflicting versions of the runtime libraries - a well-known and
> quite annoying
> problem)
>
Someth
On 2007-01-10 08:36+0100 Arjen Markus wrote:
> Hi,
>
> I tried to build the PLplot libraries statically. Here are my results:
>
> Cygwin/gcc+gfortran:
> - The Fortran examples work perfectly, but I had to switch off
> freetype support (see below)
> - Some strange problem occurred with pltcl - mis
