Re: [Gnuplot-info] Difficulty getting wxWidgets to work

[<HBB...@t-...>]

R. D. Ross wrote:

> I did a "make install" after the build was completed.  I'll mention
> that I've had no problems in the past running ./gnuplot, but I went
> ahead and ran it from the full path:
> 
> /tmp/external.rross/bin/gnuplot     (This is the install area)

That's not expected to be any improvement over

	./gnuplot

As I said: it should be run without specifying a path, to get the 
version that's actually installed.  Just like this:

	gnuplot

> The results were the same as before.  Also, the other terminal types
> seem to be OK.  At least, when I did this, it worked.

This, unfortunately, is not conclusive proof the installation is correct 
-- the gnuplot_x11 found this way could still be from a different 
version of gnuplot, mainly if you used environment variables to override 
default installation locations before.

> eventual intent is to link the gnuplot binary statically (with the exception
> of a few things like libm, libc) and distribute it along with a product that
> calls gnuplot.

I doubt that to be a viable option, mainly for X11 and stuff built on 
top of it (including wxwidgets).  You don't want to statically link libX11.

> You will see many of the libraries that I compiled and
> linked in the 'ldd gnuplot' list.  Eventually we want to produce ".a" files and 
> statically link the whole thing.  But first, it needs to work!

Wrong way round, I'm afraid.  Getting it to work with dynamic linking 
has no particular relevance to getting to work with static linking.

> # configure parameters
> 
>   export TERMLIBS="-Bstatic -lpng -lgd -lpng -lfontconfig -lfreetype -lexpat
> \
>                      -lwx_gtk2univ-2.8"

That will not work as planned.  You have to use configure arguments to 
specify which libraries you want, possibly overriding the entire library 
search path. The configure script doesn't do anything with TERMLIBS, so 
the autoconf'ed results will usually not match TERMLIBS.