gnupic@linuxhacker.org

gnupic@linuxhacker.org


Subject: Re: popt and other MIssing Headers
From: Martin McCormick
Date: Sun, 26 Oct 2003 13:45:37 -0600

Alex Holden writes:
>This looks like a bug to me. I think configure is not adding `gtk-config
>-cflags` to the CFLAGS if --disable-gui is enabled, but paraface is
>trying to include a gtk header file regardless. Try configuring gpsim
>without --disable-gui (having gui support included doesn't stop you from
>using it in command line mode).

	That did the trick.  My thanks to all who helped on this list.

	I also needed the gtkextra-dev library for another header that
showed up when I first tried to compile with the GUI, but it was
smooth sailing after that.  You also have to run it as

gpsim -i which disables the attempt to fire up the GUI on startup.  If
you aren't running X, this results in a warning that the display can't
open which immediately dumps you back to your command prompt.  I
accidentally found out about this when I tried  gpsim -? and got a
usage prompt which listed different options when calling gpsim.  When
I tried that, it came right up with the > command-line prompt and
responded to help with a list of all the commands to set up a gpsim
session.  It also does not leave one's terminal in the no echo mode
meaning that after a gpsim session, you can still see your typing
without having to type the word "reset" at the shell prompt.
So far, it looks good.

	One suggestion, though I don't know how practical it is:

	Since one needs a number of gtk libraries anyway and the size of
the gpsim executable is not large at all, it should be possible to
design gpsim to automatically go in to command-line mode when it
detects that it can't open the X display.  There are two wins.  You
don't have to make sure that the disable-gui option still works in the
configure script.  Anyone using the command line interface gets a
working gpsim without having to know or find out about gpsim -i.

	I hope the command-line interface is always there.  Command
lines can get long, clunky and down-right ugly, but you can script
them and they definitely get the jobs done.

	Let the PIC-in' begin.

Martin McCormick WB5AGZ  Stillwater, OK 
OSU Information Technology Division Network Operations Group

gnupic@linuxhacker.org