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 ;)