Re: building with AquaTerm

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

2011/3/10 Hans-Bernhard Bröker wrote:
> On 09.03.2011 22:48, Mojca Miklavec wrote:
>>
>> 2011/3/9 Hans-Bernhard Bröker wrote:
>
>> Here is where all the fun begins. I *have to* install AquaTerm to
>> /usr/local/...,
>
> Says who?  Why?

If I want to choose the option "a)" (make sure libraries are only in
places where the compiler already looks by default).

>> What do you refer to with "work _with_ system like MacPorts"?
>
> Respect the choices they made.  Put stuff where they expect it (and, more
> importantly, configured their compiler to look).  Make up your mind whether
> your newly built gnuplot is to become a part
> of yoru MacPorts world, or live outside it.

I forgot to say: I want my gnuplot to live *outside* of MacPorts.
MacPorts already comes with gnuplot, but that one doesn't satisfy my
needs, so I need a "personal" one that I link from $HOME/bin/gnuplot
that is in my PATH.

However I find it perfectly fine if that personal copy of gnuplot uses
libraries like pdflib, cairo etc. from MacPorts. In fact, most of the
time I prefer if it uses them since it is way too painful to install
some of these libraries (and they keep crashing if I try).

>> But then why do all the other libraries work? Or better: why do all
>> the other libraries get included even when I don't want them to be
>> included at all
>
> Because configure can't read your mind, so it has no way of knowing what you
> want if you don't tell it.

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)?
- 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.)

I know that configure can't read my mind, but:
- when I have aquaterm under both /usr and /opt, it uses the version from /opt
- when I have aquaterm only under /opt, it doesn't compile aquaterm
support at all (even though it could easily use the version from /opt)

I don't explicitely set anything to compile other libraries. They all
work out of the box. I honestly don't understand what is wrong with my
attempt to compile AquaTerm out-of-the-box as well.

>> Whenever I want to "get rid" of libraries that gnuplot or any other
>> program would take from MacPorts, I have to explicitely exclude
>> macports from PATH.
>
> Which es exactly the kind of "working against" MacPorts that I referred to
> earlier.

What exactly is "working against" here? If I remove MacPorts from
PATH? (If I do that *everything* works as expected.)

> 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
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?

Mojca