Re: Build problem

[<tim...@en...>]

Ethan Merritt wrote:
>
>>> As I previously described, in order to get wxWidgets up and running
>>> I first had to find and install pkgconfig. But that wasn't
>>> sufficient; I then had to go back and re-install earlier packages.
>>> What a pain.
>>>      =20
>> I think that's the fault of your distribution.
>>    =20
>
> We'll have to agree to disagree on this point.
> I think that the fewer packages I have to install, the better.
> Installing pkgconfig was unnecessary before wxt entered the
> picture, so there was no reason to install it.
>  =20
As were pango, cairo, glib, gtk ... I acknowledge that, I just thought=20
pkg-config was a very small and natural dependency compared to the=20
formers. And it is still unneeded if you don't want wxt.

>  =20
>> Checking for libraries' versions at run-time? Unless I have
>> cairo>0.9, the necessary functions are not even defined in the
>> headers. That's a compile-time requirement.
>>    =20
>
> The existence of particular entry points in a library is what the=20
> AC_CHECK_LIB macro is for. That's what we use elsewhere
> in configure.in.  Can't we use it here also?
>  =20
Oh yes, we could, you are right.
> If you link against shared libraries, the version must also be
> checked at run-time.  However, this is conflating possible problems
> at very different stages, so let's not worry about anything past
> the configuration stage.
>  =20
Ok, I see what you mean. I don't really know how to handle that.
>  =20
>> Relying on the magic of wxWidgets compile and linking flags ? What if
>> I want to write a static terminal based on cairo and independant of
>> wxWidgets then ?
>>    =20
>
> Sorry, I'm not following you there.  What's a "static terminal"?
>  =20
A terminal that would output to a file :

gnuplot> set term cairopng
gnuplot> set output 'plot.png'
gnuplot> plot x
gnuplot> set output

> I'm pretty sure that aquaterm uses cairo, but does not use wxWidgets.
> Does that count?
>  =20
I don't think it does. aquaterm is based on the native MacOS X vector=20
drawing library ("Cocoa"), not on cairo.
> Anyhow, I don't want to flog a dead horse.
> I appreciate your work, and you are clearly more comfortable with
> all the auto-build tools and accoutrements than I am.
> If it's all working now - great. I'm happy.
>  =20
I hope it is ;-)
I would really like to let configure.in as it is now.

> Getting back to the main concern: what's needed for a 4.2 release...
> Do you know what, if anything, needs to be added to the config and
> makefiles for the various gnuplot platforms that don't use the main
> configure script?=20
>  =20
Currently, the wxWidgets terminal is only available when compiled with=20
the configure script or with makefile.mgw. The others makefiles will=20
hopefully just compile gnuplot without it. I don't think I have enough=20
experience to modify those.

As far as the other features are concerned, I can only see the=20
GNUPLOT_PS_DIR stuff as a show-stopper. And the config/config.* files=20
may be updated to enable the features that have been introduced since=20
they have been generated.

Best regards,

Timoth=C3=A9e