gnuplot-beta — Developers and beta testers of new gnuplot code

Porting Gnuplot to Trolltech Qt

[Sebi35 <bob...@ho...>]

Hi all,

I've been working a lot with Qt and I often have to use plot functions. I've
recently discovered the power of Gnuplot and I'd like to encapsulate gnuplot
in a Qt widget.
Is that possible? What is the best to do this?

I have read all the docs of the gnuplot distribution, and I feel like if I
code a "Qt" terminal, the widget will only be reachable through the gnuplot
application. Is there anyway to use Gnuplot as a library?

Cheers,

Sebastien
-- 
View this message in context: http://www.nabble.com/Porting-Gnuplot-to-Trolltech-Qt-tp15065854p15065854.html
Sent from the Gnuplot - Dev mailing list archive at Nabble.com.

Re: Crash with postscript terminal

[MortenMacFly <ma...@gm...>]

MortenMacFly wrote:
> 
> I checked out the branch "Release_4_2_1"
> 
I realised there is also a branch called "Release_4_4_2". (Maybe a typo but
should read "Release_4_2_2"???) This one is not affected, too. No issues.
With regards, Morten.
-- 
View this message in context: http://www.nabble.com/Crash-with-postscript-terminal-tp15040716p15060826.html
Sent from the Gnuplot - Dev mailing list archive at Nabble.com.

Re: Crash with postscript terminal

[MortenMacFly <ma...@gm...>]

Ethan Merritt wrote:
> 
> Could you please check whether an equivalent patch is needed for version
> 4.2
> 
I checked out the branch "Release_4_2_1" (if that is hopefully what you
mean). It's not required there as the function "PS_dump_prologue_file" does
not return a file pointer but handles all itself. So this shouldn't be
broken.
With regards, Morten.
PS: BTW: This also explains why it was working all the time last year - it
seems this separation of the functions in HEAD is "brand new"...
-- 
View this message in context: http://www.nabble.com/Crash-with-postscript-terminal-tp15040716p15060756.html
Sent from the Gnuplot - Dev mailing list archive at Nabble.com.

Re: Crash with postscript terminal

[Ethan M. <merritt@u.washington.edu>]

On Wednesday 23 January 2008 07:28, MortenMacFly wrote:

> I digged into this myself and found a serious bug in the postscript terminal
> driver. The fact that it was working before for me was that the envvar
> "GNUPLOT_PS_DIR" was defined at compile time. Now that it is not (as I
> changed the makefile) and I am using the internal prologue (that gets
> compiled into the executable) the bug was raised on my machine.
> 
> Anyways - I was able to fix it. See patch #1878095
> (http://sourceforge.net/tracker/index.php?func=detail&aid=1878095&group_id=2055&atid=302055)
> for a proper fix. I hope this gets applied at some time cause this is really
> a bad bug.

I will apply your patch to the current CVS version.

Could you please check whether an equivalent patch is needed for version 4.2,
and if so prepare a patch for the 4.2 source tree also?

	thanks,

		Ethan

Re: Crash with postscript terminal

[MortenMacFly <ma...@gm...>]

MortenMacFly wrote:
> 
> The current CVS version of Gnuplot crashes for the following script on
> Windows:
> set terminal postscript
> set output "pstest.eps"
> plot sin(x)
> 

I digged into this myself and found a serious bug in the postscript terminal
driver. The fact that it was working before for me was that the envvar
"GNUPLOT_PS_DIR" was defined at compile time. Now that it is not (as I
changed the makefile) and I am using the internal prologue (that gets
compiled into the executable) the bug was raised on my machine.

Anyways - I was able to fix it. See patch #1878095
(http://sourceforge.net/tracker/index.php?func=detail&aid=1878095&group_id=2055&atid=302055)
for a proper fix. I hope this gets applied at some time cause this is really
a bad bug.

With regards, Morten.
-- 
View this message in context: http://www.nabble.com/Crash-with-postscript-terminal-tp15040716p15041572.html
Sent from the Gnuplot - Dev mailing list archive at Nabble.com.

Crash with postscript terminal

[MortenMacFly <ma...@gm...>]

The current CVS version of Gnuplot crashes for the following script on
Windows:
set terminal postscript
set output "pstest.eps"
plot sin(x)
I have compiled GP myself successfully for the last couple of years, no
problems at all with this driver. Today I had to create the prologues.h file
myself using the ps_header.sh script as the current one in CVS is too old
and thus compilation broken. But: A comparision between the old, and new
prologues.h showed the creation is in fact OK.
Here are some more details:
- created prologues.h using cygwin
- created GP using MSVC6 (makefile.nt)
- modified makefile.nt NOT to define GNUPLOT_PS_DIR so that the PS sources
are included (and in fact they are)
All this worked 100% in the past (last compilation was around October of
last year though) but now it's broken.
With regards, Morten.
-- 
View this message in context: http://www.nabble.com/Crash-with-postscript-terminal-tp15040716p15040716.html
Sent from the Gnuplot - Dev mailing list archive at Nabble.com.

Re: new rfunctions

[<pl...@pi...>]

On Wed, 23 Jan 2008 02:57:31 +0100, Philipp K. Janert <ja...@ie...>
wrote:

>
> I am also not sure that having min(), max(),
> etc for some fixed number of args would be
> all that useful.
>
> What would be AWESOME, however (at least
> in my opinion) is to have those kinds of functions
> to operate on input data.
>

Well that is getting into the realm of data processing that some feel is=

beyond the scope of a plotting tool and indeed the line has to be drawn
somewhere.

This sort of thing can already be done using the new assignment syntax b=
ut
requires two passes. ie a first plot command that calls some function on=

each point as it is plotted , then a new plot command that uses some
stored result and plots what you want to see.


> Why? Here is an example. Often I would like to
> do this:
>
> plot "data" u 1:($2 - mean($2))
>
> or
>
> plot "data" u 1:( ($2-mean($2))/stddev($2) )
>
> etc.
>

mean_sd(x)=3D (....... , mean=3D..., sdddev=3D...);

   plot "data" u 1:(mean_sd($2))
   plot "data" u 1:( ($2-mean)/stddev )

I currently do something like this to plot an arrow representing the mea=
n
y value. The arrow has to be defined before the plot so I have to do one=

run just to get the mean with a trivial function then replot with my arr=
ow.

> Given how data file input is currently handled,
> something like the above would be difficult to
> implement, I think (would require multiple passes).
>
> A very useful alternative might be to have a
> "stat" command, so that I could say:
>
> stat "data" u 1
>
> and it prints a brief report to the terminal, including
> all the usual suspects (mean, stddev, min, max, median...)
> That would be tremendously useful when working with
> data...
>

That would be an never ending list of desired functions that someone wou=
ld
always want extending.
There exists now two mechanisms , one internal and of course the
traditional ablility to call any outside prog or script to do more compl=
ex
analysis.

Maybe someone with a good grounding in these stats could provide a set o=
f
gnuplot functions as a .gnu that could be added to any users .gnu with o=
ne
line of load "basic-stats.gnu" like Ethan suggested.

If something is to be added here like your stat suggestion it could be a=

dont_plot option that mimics the way plot goes through the data without
spending time creating the output. This would allow a prepass for simple=

d.p. functions as outlines above without much of the redundancy.

I expect it would be pretty simple to add this as an plot option or null=

line type that simple avoids calling the output routine. I'd have to dig=

into the code.

The above example could become:

   plot "data" u 1:(mean_sd($2)) noplot
   plot "data" u 1:( ($2-mean)/stddev )

This could substancially improve the efficiency of the dual pass appraoc=
h.


regards, Peter.


> Best,
>
> 		Ph.
>
>
> On Tuesday 22 January 2008 14:41, Ethan Merritt wrote:
>> On Tuesday 22 January 2008 14:30, Mojca Miklavec wrote:
>> > On Jan 22, 2008 11:20 PM, Ethan Merritt wrote:
>> > > On Tuesday 22 January 2008 05:54, Daniel Heiserer wrote:
>> > > > I would like to add some functions to the CVS version of gnuplo=
t.
>> > > > These functions include:
>> > > > min()
>> > > > max()
>> > > > std()
>> > > > mean()
>> > > > etc.
>> > >
>> > > Could you explain why you need to have these as built-in function=
s?
>> > > What is wrong with just defining them yourself:
>> > >
>> > >   min(A,B) =3D A < B ? A : B
>> > >
>> > > You can put that definition in your customization file ~/.gnuplot=

>> > > if you always like to have it.
>> >
>> > I agree that min, max, mean and others might be handy to have. I
>> > always "hack them" with ($1+$2+$3+$4)/4 or the way you have just
>> > shown, but these are really basic functions that are often used and=

>> > easy to implement.
>>
>> The two argument case is trivial, as shown above.
>> The general case of N arguments would be less trivial, particularly i=
f
>> you are looking for a way to make the calculation over an arbitrary
>> number of data points read from a data file.
>>
>> Before jumping in with both feet, I think it would be useful to
>> block out what exactly is the goal.
>>
>> I can understand wanting MIN and MAX for simple bookkeeping,
>> for example choosing which of two column values to use.
>>
>> But the need for a command line  std(a,b,c,...) or mean(a,b,c,...)
>> function is not obvious to me.  This seems more like something one
>> would track automatically during the course of data input than
>> something one would type in manually at the command line.
>>
>> > Instead of asking "why one would want to add them", I would rather =
ask
>> > "why not".
>>
>> The reason to ask "why" is that there may be a better way to achieve
>> the actual goal.
>
> ----------------------------------------------------------------------=
---
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
>

Re: new rfunctions

[Philipp K. J. <ja...@ie...>]

I am also not sure that having min(), max(),
etc for some fixed number of args would be
all that useful.

What would be AWESOME, however (at least
in my opinion) is to have those kinds of functions
to operate on input data.

Why? Here is an example. Often I would like to
do this:

plot "data" u 1:($2 - mean($2))

or 

plot "data" u 1:( ($2-mean($2))/stddev($2) )

etc.

Given how data file input is currently handled,
something like the above would be difficult to
implement, I think (would require multiple passes).

A very useful alternative might be to have a 
"stat" command, so that I could say:

stat "data" u 1

and it prints a brief report to the terminal, including 
all the usual suspects (mean, stddev, min, max, median...)
That would be tremendously useful when working with
data...

Best,

		Ph.


On Tuesday 22 January 2008 14:41, Ethan Merritt wrote:
> On Tuesday 22 January 2008 14:30, Mojca Miklavec wrote:
> > On Jan 22, 2008 11:20 PM, Ethan Merritt wrote:
> > > On Tuesday 22 January 2008 05:54, Daniel Heiserer wrote:
> > > > I would like to add some functions to the CVS version of gnuplot.
> > > > These functions include:
> > > > min()
> > > > max()
> > > > std()
> > > > mean()
> > > > etc.
> > >
> > > Could you explain why you need to have these as built-in functions?
> > > What is wrong with just defining them yourself:
> > >
> > >   min(A,B) = A < B ? A : B
> > >
> > > You can put that definition in your customization file ~/.gnuplot
> > > if you always like to have it.
> >
> > I agree that min, max, mean and others might be handy to have. I
> > always "hack them" with ($1+$2+$3+$4)/4 or the way you have just
> > shown, but these are really basic functions that are often used and
> > easy to implement.
>
> The two argument case is trivial, as shown above.
> The general case of N arguments would be less trivial, particularly if
> you are looking for a way to make the calculation over an arbitrary
> number of data points read from a data file.
>
> Before jumping in with both feet, I think it would be useful to
> block out what exactly is the goal.
>
> I can understand wanting MIN and MAX for simple bookkeeping,
> for example choosing which of two column values to use.
>
> But the need for a command line  std(a,b,c,...) or mean(a,b,c,...)
> function is not obvious to me.  This seems more like something one
> would track automatically during the course of data input than
> something one would type in manually at the command line.
>
> > Instead of asking "why one would want to add them", I would rather ask
> > "why not".
>
> The reason to ask "why" is that there may be a better way to achieve
> the actual goal.

Re: end the pause

[Maximilian F. <mx...@gm...>]

On Jan 23, 2008 1:19 AM, Ethan Merritt <merritt@u.washington.edu> wrote:
> On Tuesday 22 January 2008 16:03, Maximilian Fabricius wrote:
> > Hi all,
> >
> > fist of all I apologize if this topic came up recently already.
> >
> > I love to use shell scripts for my work and to use gnuplot to present
> > intermediate results.
> > Now, it would be great if I could present a plot, let the user use all
> > the great interactive
> > features of the x11 terminal like zooming and continue my script only
> > after the user closed
> > the terminal. Alternatively if I could define a key - "q" for example
> > - which closes the current plot
> > and continues the gunplot script, that would be great.
>
> You have many such options.
> Please see the examples given with "help pause".
>

Ethan,

thank you for the quick answer. To my understanding the closest thing
to what I meant
is "pause mouse keypress". Now, as soon as I press the Apple ALT key
on my mac keyboard
in order to zoom in, pause is interupted.

It be great if I could define "paues mouse keypress q".

Cheers,

Maximilian

Re: end the pause

[Ethan M. <merritt@u.washington.edu>]

On Tuesday 22 January 2008 16:03, Maximilian Fabricius wrote:
> Hi all,
> 
> fist of all I apologize if this topic came up recently already.
> 
> I love to use shell scripts for my work and to use gnuplot to present
> intermediate results.
> Now, it would be great if I could present a plot, let the user use all
> the great interactive
> features of the x11 terminal like zooming and continue my script only
> after the user closed
> the terminal. Alternatively if I could define a key - "q" for example
> - which closes the current plot
> and continues the gunplot script, that would be great.

You have many such options.
Please see the examples given with "help pause".

In the CVS version of gnuplot you also have the option to bind
an arbitrary command sequence to the event generated by closing
the plot window:

	bind "close" "N=N+1; load 'plot'.N"

That would load successive plots plot1 plot2 plot3 etc;
each would display until the window was closed, then the next one would
pop up in sequence.

> Before I start digging through code, is there already a solution to
> this? 

There are many solutions.
As to focus or re-focus of the window to catch keystrokes,
that is more a matter for your window manager than for gnuplot.

-- 
Ethan A Merritt

end the pause

[Maximilian F. <mx...@gm...>]

Hi all,

fist of all I apologize if this topic came up recently already.

I love to use shell scripts for my work and to use gnuplot to present
intermediate results.
Now, it would be great if I could present a plot, let the user use all
the great interactive
features of the x11 terminal like zooming and continue my script only
after the user closed
the terminal. Alternatively if I could define a key - "q" for example
- which closes the current plot
and continues the gunplot script, that would be great.

A typical shell script of mine would look like this
--- SNIP ---
### generate some data in data.dat

echo "plot 'data.dat'" > plotit.tmp
echo "pause -1" >> plotit.tmp
gnuplot plotit.tmp

### continue working on the data
--- SNIP SNIP ---

But because of the "pause -1" the user has to focus the terminal and
hit a key before the script continues.

Before I start digging through code, is there already a solution to
this? Am I trying to do something stupid?

Cheers,

Maximilian

Re: new rfunctions

[Ethan M. <merritt@u.washington.edu>]

On Tuesday 22 January 2008 14:30, Mojca Miklavec wrote:
> On Jan 22, 2008 11:20 PM, Ethan Merritt wrote:
> > On Tuesday 22 January 2008 05:54, Daniel Heiserer wrote:
> > > I would like to add some functions to the CVS version of gnuplot.
> > > These functions include:
> > > min()
> > > max()
> > > std()
> > > mean()
> > > etc.

> > Could you explain why you need to have these as built-in functions?
> > What is wrong with just defining them yourself:
> >
> >   min(A,B) = A < B ? A : B
> >
> > You can put that definition in your customization file ~/.gnuplot
> > if you always like to have it.
> 
> I agree that min, max, mean and others might be handy to have. I
> always "hack them" with ($1+$2+$3+$4)/4 or the way you have just
> shown, but these are really basic functions that are often used and
> easy to implement.

The two argument case is trivial, as shown above.
The general case of N arguments would be less trivial, particularly if
you are looking for a way to make the calculation over an arbitrary
number of data points read from a data file.

Before jumping in with both feet, I think it would be useful to
block out what exactly is the goal.

I can understand wanting MIN and MAX for simple bookkeeping,
for example choosing which of two column values to use.

But the need for a command line  std(a,b,c,...) or mean(a,b,c,...)
function is not obvious to me.  This seems more like something one
would track automatically during the course of data input than 
something one would type in manually at the command line.

> Instead of asking "why one would want to add them", I would rather ask
> "why not".

The reason to ask "why" is that there may be a better way to achieve
the actual goal.

-- 
Ethan A Merritt

Re: new rfunctions

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

On Jan 22, 2008 11:20 PM, Ethan Merritt wrote:
> On Tuesday 22 January 2008 05:54, Daniel Heiserer wrote:
> > dear developers,
> >
> > I am nost sure if this is the developers list, but I didn't find another link to it.
>
> The is the developer list, yes.
> Welcome.
>
> > Problem:
> > I would like to add some functions to the CVS version of gnuplot.
> > These functions include:
> > min()
> > max()
> > std()
> > mean()
> > etc.
> >
> > so for example it would be possible to run:
> >
> > plot  "summary_01.ascii"   using 1:(0.90*min($2,$3)) with lines lt 1 lc rgb "#0000ff" lw 2
>
> Could you explain why you need to have these as built-in functions?
> What is wrong with just defining them yourself:
>
>   min(A,B) = A < B ? A : B
>
> You can put that definition in your customization file ~/.gnuplot
> if you always like to have it.

I agree that min, max, mean and others might be handy to have. I
always "hack them" with ($1+$2+$3+$4)/4 or the way you have just
shown, but these are really basic functions that are often used and
easy to implement.

Instead of asking "why one would want to add them", I would rather ask
"why not".

But this is just my humble opinion, nothing else.

Mojca

Re: new rfunctions

[Ethan M. <merritt@u.washington.edu>]

On Tuesday 22 January 2008 05:54, Daniel Heiserer wrote:
> dear developers,
> 
> I am nost sure if this is the developers list, but I didn't find another link to it.

The is the developer list, yes. 
Welcome.

> Problem:
> I would like to add some functions to the CVS version of gnuplot.
> These functions include:
> min()
> max()
> std()
> mean()
> etc.
> 
> so for example it would be possible to run:
> 
> plot  "summary_01.ascii"   using 1:(0.90*min($2,$3)) with lines lt 1 lc rgb "#0000ff" lw 2

Could you explain why you need to have these as built-in functions?
What is wrong with just defining them yourself:

  min(A,B) = A < B ? A : B

You can put that definition in your customization file ~/.gnuplot 
if you always like to have it.

  
> Is there a way, that the gnuplot "parser" detects the number of arguments 
> on another way and I have access to it 

It knows internally, yes.  You could look at the implementation of
sprintf() for example.  That takes an arbitrary number of arguments.
The internal name for this function is f_sprintf().
You can find the source code in internal.c


-- 
Ethan A Merritt

Re: context terminal

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

On Jan 22, 2008 8:41 PM, GDutilleux <gui...@fr...> wrote:
>
> Hello,
> I download 4.3.0 from the CVS and did find the prepare script.
> After customizing for ConTeXt as below, ./configure returns a list of
> terminals with no mention of the context one. I stopped there during my
> first attempt with 4.2.0, thinking that something was wrong. This time I
> chose to ignore this disappointing message and compiled the 4.3.0 source
> anyway. The result is a gnuplot binary that understands "set terminal
> context".
> Thanks for your help. Best regards,
> G. Dutilleux

Oh, I didn't read your message carefully enough. I have thought that
the terminal doesn't appear in the list when running gnuplot.
Since the terminal gets hardcoded into gnuplot, one would need to
patch that messages in configure script as well (I both didn't think
about it and now I would not consider it worth mentioning to fix that
unles the terminal would be added to CVS one day).

I have also started modifying the terminal already to output TikZ
code, but then I have figured out that someone did that already using
lua (and would only need minor modifications to make it work in plan
TeX & ConTeXt as well). But nobody has ever commented about that TikZ
terminal so far, although I suspect that quito some people use it
already. It would indeed be nice to have a better any-TeX support.

http://peter.affenbande.org/gnuplot/

Mojca

> GDutilleux wrote:
> >
> >
> > On Mac OS X 10.3.9 i tried to compile gnuplot 4.2.0 from source with the
> > ConTeXt terminal. To do so
> > 1 I added   in term/ the context.trm file provided by Mojka Miklavec.
> > 2 I added #include "context.trm" in src/term.h.
> >
> > On his recipe for building this custom gnuplot Mojka Miklavec mentions a
> > ./prepare gnuplot utility to run first. I don't find it in the 4.2.0
> > source release.
> > After running ./configure script the context terminal is not mentioned in
> > the list of terminals taken into account. Any idea ?
> > Best regards,
> >
> > G. Dutilleux

Re: context terminal

[GDutilleux <gui...@fr...>]

Hello,
I download 4.3.0 from the CVS and did find the prepare script.
After customizing for ConTeXt as below, ./configure returns a list of
terminals with no mention of the context one. I stopped there during my
first attempt with 4.2.0, thinking that something was wrong. This time I
chose to ignore this disappointing message and compiled the 4.3.0 source
anyway. The result is a gnuplot binary that understands "set terminal
context". 
Thanks for your help. Best regards,
G. Dutilleux


GDutilleux wrote:
> 
> 
> On Mac OS X 10.3.9 i tried to compile gnuplot 4.2.0 from source with the
> ConTeXt terminal. To do so 
> 1 I added   in term/ the context.trm file provided by Mojka Miklavec. 
> 2 I added #include "context.trm" in src/term.h. 
> 
> On his recipe for building this custom gnuplot Mojka Miklavec mentions a
> ./prepare gnuplot utility to run first. I don't find it in the 4.2.0
> source release. 
> After running ./configure script the context terminal is not mentioned in
> the list of terminals taken into account. Any idea ?
> Best regards,
> 
> G. Dutilleux
> 

-- 
View this message in context: http://www.nabble.com/context-terminal-tp14975999p15026588.html
Sent from the Gnuplot - Dev mailing list archive at Nabble.com.

new rfunctions

[Daniel H. <dan...@ya...>]

dear developers,=0A=0AI am nost sure if this is the developers list, but I =
didn't find another link to it.=0A=0AIf it is see below my questions if not=
, please forward me to the "right" adress.=0A=0AThanks.=0A=0A--------------=
-----------------------=0AProblem:=0AI would like to add some functions to =
the CVS version of gnuplot.=0AThese functions include:=0Amin()=0Amax()=0Ast=
d()=0Amean()=0Aetc.=0A=0Aso for example it would be possible to run:=0A=0Ap=
lot  "summary_01.ascii"   using 1:(0.90*min($2,$3)) with lines lt 1 lc rgb =
"#0000ff" lw 2=0A=0AHowever for min and max this is doable with two argumen=
ts only even if it is awesome if I have more then two values=0Ato build the=
 "minimum":=0A ....  using 1:(0.90*min($2,min($3,min($4,$5)))) ...=0AFor me=
an and std this is not doable.=0A=0AOne option would be to add a number-of-=
arguments arguments: such as=0Amin(nargs,$2,$3,$4). However this looks ugly=
 for me.=0A=0AIs there a way, that the gnuplot "parser" detects the number =
of arguments on another way and I have access to it=0Acounting the number a=
rguments so I could simply live with a=0A=0Amin($2,$3,$3) for example.=0A=
=0AMaybe there is already another solution inside gnuplot for these kinds o=
f "problem".=0A=0APlease let me know. =0A=0AThanks, daniel heiserer=0A=0A=
=0A=0A=0A      Jetzt Mails schnell in einem Vorschaufenster =FCberfliegen. =
Dies und viel mehr bietet das neue Yahoo! Mail - www.yahoo.de/mail

Re: gnu readline & UTF-8

[Allin C. <cot...@wf...>]

On Mon, 21 Jan 2008, Mojca Miklavec wrote:

> On Jan 21, 2008 11:28 PM, Ethan Merritt wrote:
> > I suggest that you add "-lreadline -lhistory" to CFLAGS and
> > try ./configure again.  This is an OSX peculiarity.
> 
> How exactly do I do that? I have tried this, but it fails...

In general, one would not add linker directives such as "-lfoo" to 
the CFLAGS variable.  Perhaps to LDFLAGS or LIBS or some such 
variable.

Allin Cottrell

Re: minimum installation query

[<pl...@pi...>]

On Tue, 22 Jan 2008 00:02:57 +0100, Ethan Merritt  
<merritt@u.washington.edu> wrote:

> On Monday 21 January 2008 13:16, pl...@pi... wrote:
>> > If you are willing to sacrifice the help subsystem in order to make  
>> the
>> > footprint smaller, then logically you would also want to omit help.c  
>> from
>> > the list of source files and comment out the calls to its routines.
>>
>> I'm not that tight I need to byte pinch at this stage but saving 500k  
>> + is
>> relevant.
>
> So now I'm curious as to how small you managed to make the executable.
>
> What drivers have you decided to include?
> Did you link to shared libraries, or is it static?
> What sort of display is present on the device you are building for?
>
> Can you suggest alternative mechanisms for help access that would be
> reasonable?   Maybe the "help" command could trigger a web browser
> pointed to on-line documentation hosted elsewhere.
>


well I haven't really tried to optimise the footprint , just lighten it a  
bit. I may need to dig further later. It's mainly a case of removing as  
many deps as possible.

I really do not require gnuplot help in the current context. I am using  
gnuplot on an SBC that does some simple control and data logging. The idea  
is to use gnuplot to preprocess the live data and provide graphical output  
in svg format that can be served up by apache. There will probably be some  
simple user interface via javascript so all calls to gnuplot will be  
scripts not user.

This means I can dump most of the baggage like x11 , png ,gd etc since svg  
is one of the std terminals. It looks like about 2MB for gnuplot itself  
but I still have -g at this stage and not -Os. I expect I can drop that a  
lot if needed.

I'm currently trying to determine exactly what deps I do need to  
cross-build so if you have any hints on determining the list it would be  
helpful.

eg is zlib reqd if I'm not using gd/png ?

Hans:
>> doc2gih is not meant to be installed anywhere.  It's compiled inside  
>> the build treeand used to create gnuplot.gih, and that's the end of its  
>> usefulness.  This will mostprobably fail to work in a cross build.

thanks for explaining what that was about. Luckily I have got around the  
problem as Ethan suggested by hacking the SUBDIRS line.


Thank you both for your help ;)

Re: minimum installation query

[Ethan M. <merritt@u.washington.edu>]

On Monday 21 January 2008 13:16, pl...@pi... wrote:
> > If you are willing to sacrifice the help subsystem in order to make the
> > footprint smaller, then logically you would also want to omit help.c from
> > the list of source files and comment out the calls to its routines.
> 
> I'm not that tight I need to byte pinch at this stage but saving 500k + is  
> relevant.

So now I'm curious as to how small you managed to make the executable.

What drivers have you decided to include?
Did you link to shared libraries, or is it static?
What sort of display is present on the device you are building for?

Can you suggest alternative mechanisms for help access that would be
reasonable?   Maybe the "help" command could trigger a web browser 
pointed to on-line documentation hosted elsewhere.

-- 
Ethan A Merritt

gnu readline & UTF-8

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

On Jan 21, 2008 11:28 PM, Ethan Merritt wrote:
> On Monday 21 January 2008 14:18, Mojca Miklavec wrote:
> >
> > I have tried to compile a fresh gnuplot version (4.2.2) and it the
> > compilation says:
> >     checking for remove_history in -lreadline... no
> >     configure: WARNING: GNU readline not found - falling back to
> > builtin readline
> >
> > Does that mean that gnuplot interprets the current line?
>
> I have not experimented with the builtin readline, so I don't
> know whether it handles 8-bit characters or UTF8 characters
> gracefully.
>
> I suggest that you add "-lreadline -lhistory" to CFLAGS and
> try ./configure again.  This is an OSX peculiarity.

How exactly do I do that? I have tried this, but it fails (4.2.2, I
will try with the cvs version again):

> export CFLAGS="-lreadline -lhistory"
> ./configure
checking for a BSD-compatible install... /sw/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... configure: error:
C compiler cannot create executables
See `config.log' for more details.

Mojca


## ----------- ##
## Core tests. ##
## ----------- ##

configure:1472: checking for a BSD-compatible install
configure:1527: result: /sw/bin/ginstall -c
configure:1538: checking whether build environment is sane
configure:1581: result: yes
configure:1646: checking for gawk
configure:1662: found /sw/bin/gawk
configure:1672: result: gawk
configure:1682: checking whether make sets $(MAKE)
configure:1702: result: yes
configure:1921: checking for gcc
configure:1937: found /usr/bin/gcc
configure:1947: result: gcc
configure:2191: checking for C compiler version
configure:2194: gcc --version </dev/null >&5
i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5367)
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:2197: $? = 0
configure:2199: gcc -v </dev/null >&5
Using built-in specs.
Target: i686-apple-darwin8
Configured with: /private/var/tmp/gcc/gcc-5367.obj~1/src/configure
--disable-checking -enable-werror --prefix=/usr --mandir=/share/man
--enable-languages=c,objc,c++,obj-c++
--program-transform-name=/^[cg][^.-]*$/s/$/-4.0/
--with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib
--build=powerpc-apple-darwin8 --with-arch=nocona --with-tune=generic
--program-prefix= --host=i686-apple-darwin8
--target=i686-apple-darwin8
Thread model: posix
gcc version 4.0.1 (Apple Computer, Inc. build 5367)
configure:2202: $? = 0
configure:2204: gcc -V </dev/null >&5
gcc: argument to `-V' is missing
configure:2207: $? = 1
configure:2230: checking for C compiler default output file name
configure:2233: gcc -lreadline -lhistory   conftest.c  >&5
/usr/bin/ld: can't locate file for: -lhistory
collect2: ld returned 1 exit status
configure:2236: $? = 1
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "gnuplot"
| #define PACKAGE_TARNAME "gnuplot"
| #define PACKAGE_VERSION "4.2.2"
| #define PACKAGE_STRING "gnuplot 4.2.2"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "gnuplot"
| #define VERSION "4.2.2"
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:2275: error: C compiler cannot create executables
See `config.log' for more details.

Re: minimum installation query

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

pl...@pi... wrote:

> What this does bring out is that there is no check for doc2gih in the  
> preamble. Since this fails to compile and hence fails to install even the  
> executable this is a fatal error

doc2gih is not meant to be installed anywhere.  It's compiled inside the 
build tree and used to create gnuplot.gih, and that's the end of its 
usefulness.  This will most probably fail to work in a cross build.

Re: context terminal

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

Hello G.,

On Jan 19, 2008 11:23 PM, GDutilleux wrote:
>
> Hello,
>
> On Mac OS X 10.3.9 i tried to compile gnuplot 4.2.0 from source with the
> ConTeXt terminal. To do so
> 1 I added   in term/ the context.trm file provided by Mojka Miklavec.
> 2 I added #include "context.trm" in src/term.h.

At what place? (I assume you did it properly, but in case that you
have put it in some section which is only executed conditionally, it
might not work ...)
I simply put it next to #include "latex.trm".

> On his recipe

her :)

> for building this custom gnuplot Mojka Miklavec mentions a
> ./prepare gnuplot utility to run first. I don't find it in the 4.2.0 source
> release.

Allin, thanks for the note. Apparently "./prepare" is only needed for
the CVS version of gnuplot (where it's not possible to do it without).
You only need to run "./configure" and "make" ("make install"). See
also http://www.gnuplot.info/announce.4.2.2

(I will fix the note on contextgarden.net.)

> After running ./configure script the context terminal is not mentioned in
> the list of terminals taken into account. Any idea ?

Just to make sure: did you run the new gnuplot or the old one? "make"
will create "./src/gnuplot" executable. If you simply type "gnuplot"
in your terminal without replacing the old gnuplot executable, the old
one will be executed (and that one doesn't contain the new terminal).

I would be glad to get any feedback once you manage to make it work.

Mojca

Re: how to use iso-latin-2 with PS terminal

[Ethan M. <merritt@u.washington.edu>]

On Monday 21 January 2008 14:18, Mojca Miklavec wrote:
> 
> I have tried to compile a fresh gnuplot version (4.2.2) and it the
> compilation says:
>     checking for remove_history in -lreadline... no
>     configure: WARNING: GNU readline not found - falling back to
> builtin readline
> 
> Does that mean that gnuplot interprets the current line?

I have not experimented with the builtin readline, so I don't
know whether it handles 8-bit characters or UTF8 characters
gracefully.

I suggest that you add "-lreadline -lhistory" to CFLAGS and
try ./configure again.  This is an OSX peculiarity.

The CVS tree for 4.2 has several fixes for building under OSX.
I was figuring to release a 4.2.3 incremental version somewhere
around the beginning of March.  The list of fixes is small, but
I think it's worth it for the improved auto-build under OSX if
nothing else.

Current status of NEWS in the 4.2 CVS tree:

New features, changes and fixes in gnuplot version 4.2.3
===========================================================
* NEW options front and back to "set colorbox"
* NEW character encoding support for emf and pdf terminals
* FIX minitics in log scale
* FIX tweak installation scripts for OSX, nt, Sun
* FIX minor bugfixes to terminals fig, emf, post, svg, x11
* FIX protect against overly long font names in gd, svg
* FIX infinite loop from x11 plot window resizing under ion, fluxbox
* FIX never estimate zero size for a non-empty string
* FIX discard degenerate polygons during hidden3d processing
* FIX segfault if replot is called while terminal type is unknown
* FIX discard axis ticks read from previous data file
* FIX Do not clip image against Z range in 3D splot with "set view map"
* CHANGE install Xresource file as Gnuplot, not Gnuplot.app-defaults
* CHANGE Remove limitation of 10 args max to internal function sprintf()
* CHANGE Bring emf point types into conformity with other terminals



-- 
Ethan A Merritt            Courier Deliveries: 1959 NE Pacific
Dept of Biochemistry
Health Sciences Building
University of Washington - Seattle WA 98195-7742

Re: how to use iso-latin-2 with PS terminal

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

On Jan 20, 2008 5:42 AM, Ethan A Merritt wrote:
> On Saturday 19 January 2008 17:43, Mojca Miklavec wrote:
>
> > I'm using Mac OS X and ...
>
> > No, wait ... it's more weird than that. I'm trying to use these
> > characters before issuing any other command (setting encoding etc.).
> > These letters work "per-se". But they fail in one particular case:
> > when I type normally, it works OK, but once I press left arrow (to go
> > back in the line), it completely confuses gnuplot whenever I play with
> > accented letters (multibyte) forth and back.
>
> That sounds like a problem with the input stream.
> Are you using gnu libreadline?  gnuplot's built-in readline?
> No readline at all?  Given that this is OSX, we may have to
> worry also that the library claims to be gnu libreadline but
> is really BSD's editline in disguise.

I have tried to compile a fresh gnuplot version (4.2.2) and it the
compilation says:
    checking for remove_history in -lreadline... no
    configure: WARNING: GNU readline not found - falling back to
builtin readline

Does that mean that gnuplot interprets the current line?

Thanks for the hint,
    Mojca