Hi Werner,
I tested the batch file make_all_vc.bat this morning. Here are my results:
- I ran it in a separate DOS-box
- Preparation includes:
- running vcvars32 - otherwise CMake can not identify the proper compilers
- making sure CMake in the path
- A minor but important fix is needed:
(Repost with renamed file ending, so that it gets through spam/virus checks)
Hi,
I wrote and tested now a batch file, which assembles a binary package of
plplot for MinGW or Visual C++ and can easily adjusted for other
compilers. It copies the dlls of the gd, libharu and wxwidgets libraries
if
Hi Arjen,
The problem with the additional libraries is that right now we rely on them
being present at build-time and at run-time - we do not have mechanisms
to detect
whether they are actually available at run-time. Nothing to worry about
in the
current way of working, but a nuisance
Hi Jim,
What third party libraries do I need to include?
You don't need to include them, but they provide additional
functionality or drivers. In the moment these are:
* gd library - used for the gd driver (png, jpeg, gif output)
* freetype library - used for nice font rendering in some
Werner Smekal wrote:
* qhull library - not sure actually, but I think it is used for
interpolation in grids, so they look more nicely (or something similar :)
qhull is a library/program to determine the convex hull of a set of
points in
n dimensions. The CSIRO library that is part of
Werner Smekal [EMAIL PROTECTED] writes:
A windows script would be easy to write with windows commands apart from
the tar stuff - zip should be used on the windows platform and than we
would need a zip program also :) (which we would get via
gnuwin32.sf.net). Anyway, Jim was already able
On 2006-12-17 09:37+0100 Werner Smekal wrote:
Alan W. Irwin wrote:
There is also some indication on the CMake list that a solution to the
current limitation for CPack will be found. One way or another I hope
this
showstopper for binary releases of PLplot is resolved within the next week
Hi Alan,
I'll have a look into this topic. Ideally we should provide two
packages, one with Visual Studio C++ 6.0 libraries and one with MinGW
libraries. Python and so on, can use both or at least one of these
packages. I'm not aware of projects which would depend on Borland
libraries and so
Alan W. Irwin [EMAIL PROTECTED] writes:
On 2006-12-15 09:56+0100 Werner Smekal wrote:
There are two issues here (and a third one below):
(1) Working out the current bugs in the package target. I suggest you first
do that with your MinGW platform since that is obviously an important
