Re: Re: Re: compiling gnuplot on Windows & mac/linux

[Mojca M. <moj...@gm...>]

On 11/19/06, Petr Mikulik wrote:
> >> I'd rather you remove the stupid compiler that emits them.
> > makefile.mgw
> > #DESTDIR = /c/Progra~1/Gnuplot4.1
> >
> > any many other places still contain old strings. Can anyone grep for
> > them and replace them?
>
> By what? Isn't there some way to know whether that dir should be called
> "Program Files", "Programy", "Programme", etc?

I meant the number. Some files still contain 4.1 as the version number
(or 4.2 in cvs, which should be 4.3 now).

> > Now a question: is anyone ready to help me to write a clean makefile
> > for MinGW for cross-compiling (which would be suitable to add to CVS)
> > or does that exist already?
>
> Do you really need it? I "crosscompile" gnuplot for Windows on Linux by
> means of MingW: I run the wine console (wcmd), and then do what is written
> for mingw: go to src/, type "make -f ../config/makefile.mgw", and it is
> done.
>
> Isn't there a Wine for MacOSX on Intel?

Yes, there is - thanks for the hint, it will probably go more smoothly
(easier) there. I was compiling without wine (crosscompiling using
mingw) - successfully, but I didn't manage to integrate external
libraries (gd, wxt) yet.

> >> Microsoft has made it clear that they don't care about providing a
> >> working compiler, why should we care about supporting their broken product?
> >
> > OK, I accept that.
>
> There could be a message in that makefile that the
> compilation/binary/pgnuplot/... may not work for which version of the
> compiler.

It conditionally works with the latest version (apart from gd & wxt -
I have no idea whose fault that is because I cannot check with older
compilers), but I understood the answer more like
   "We don't want to fix (minor things that would make compiling a bit easier)."
and I'm OK with it.

> > Do you really need it? I "crosscompile" gnuplot for Windows on Linux by
> > means of MingW: I run the wine console (wcmd), and then do what is written
> > for mingw: go to src/, type "make -f ../config/makefile.mgw", and it is
> > done.
>
> That's not really cross-compiling.  Cross-compiling would mean you build
> a version of GCC running directly on Linux that builds Win32 executables
> based on the MinGW libraries and headers.

I don't really mind if this is called cross-compiling or not - I only
care about the end effect which should be a working windows
application. (And if it's easier to do it using wine, there should be
no reason for not using it.)

Mojca