Re: building with AquaTerm

[Ethan A M. <sf...@us...>]

On Wednesday, March 09, 2011 03:41:47 pm Mojca Miklavec wrote:

> So how can I for example:
> - Tell gnuplot's configure script to use the version of aquaterm from
> /usr and not the one from /opt (when I have macports in path)?

If the one in MacPorts doesn't work, why not just replace it altogether?
Anyhow, we're past this issue now, right?  You need to set the environmental
variables appropriately before running configure.

> - Use UTF-8 input on Mac asssuming that I entirely remove MacPorts
> from my system? (utf8.dem works fine, but no non-ascii characters are
> accepted on input and I cannot use left alt as "alt-gr"; I just
> realized that now.)

Aha.  If you had explained that to start with it would have saved time.

What you describe is a symptom of linking to the fake readline supplied
as part of OSX.  It is really a wrapper for the BSD libedit library,
which cannot handle UTF-8 input.   To fix this you need to install and
link to a copy of the real gnu libreadline.   Or if you like, you could
use gnuplot's built-in readline.  That is less capable in some other areas,
but it has no trouble handling UTF-8.

This is explained in the current release and installation notes for
gnuplot.

 
> > If you don't want to use your MacPorts, why did you install them
> > in the first place?
> 
> Let's say that I want to build a standalone Gnuplot.app that any user
> could copy from my homepage and it would then work out of the box.

I don't think that is possible, or at least if it is possible than I don't 
know how to do it.  It would have to be statically linked, and even then
I don't think that would solve your aquaterm issues.


> I
> need MacPorts most of the time, but if I leave MacPorts in PATH when I
> compile gnuplot, other users won't be able to use the binary that I
> compile due to dependencies on libraries provided by MacPorts. Please
> don't tell me that I need to buy a new machine without MacPorts just
> for the sake of compiling gnuplot that will be usable on other
> machines?

The shared libraries present when you run a program must be the same
(or at least API compatible with) with libraries used to link the program.
That requirement is true for gnuplot, or aquaterm, or MacPorts, just as
it is for all other programs and shared libraries.