[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: xiterm-0.4 & arabic

On Thu, Nov 28, 2002 at 03:56:02PM +0900, Jiro SEKIBA wrote:
> At Wed, 27 Nov 2002 23:54:02 -0600,
> Mohammed Elzubeir wrote:
> > I tried to compile iterm, xiterm or whatever it's called now. It failed on
> > the Xaw/lib part (the second thing to compile).
>  You need install libiterm first.  Or you have to specify the --includedir.

That doesn't help, it is simply ignored. I added it to the Makefile.am (though I'm pretty
sure that's not where it should go) -- but it did it for me:

Index: Makefile.am
RCS file: /cvsroot/iterm/unix/Xaw/lib/Makefile.am,v
retrieving revision 1.2
diff -u -B -r1.2 Makefile.am
--- Makefile.am	2002/10/21 07:21:19	1.2
+++ Makefile.am	2002/11/28 20:48:14
@@ -2,7 +2,7 @@
 libXiterm_la_SOURCES =  Iterm.c Iterm.h ItermP.h VT.c VT.h VTP.h VTScreenView.c VTScreenView.h actions.c actions.h config.h scrollbar.c scrollbar.h xim.c xim.h
-CPPFLAGS        = -I$(top_srcdir)/include -DBIDI
+CPPFLAGS        = -I$(includedir) -I$(top_srcdir)/include -DBIDI
 libXiterm_la_LDFLAGS     = -version-info 1:0:0

>  About the name, iterm is the name of framework.  The framework aims
> to create reusable internationalized terminal model.  Basic component of
> iterm is libiterm, the _model_ of terminal emulator.  fbiterm/libXiterm
> are the libiterm applications,  the _view_ of terminal emulator.
> fbiterm is the terminal emulator using libiterm, works on Linux Framebuffer.
> libXiterm is a terminal emulator _Widget_ of Athena.  And the xiterm is the
> terminal emulator using the Widget.  So it's not like xterm/mlterm and 
> other existing single binary terminal emulators.

Thanks. I think many people are very confused by the way it is structured.

>   This case, libiterm was successfully compiled, but libXiterm can't
> find the include file of libiterm.

And the problem lies in the autotools configuration. If I were to want to install it
system-wide, I probably wouldn't have experienced any of the problems. I've had to do
similar (and sometimes different) things through out the process to get everything to
compiler properly. 

>  Sorry, I can't get what you mean exactly, but each configure scripts
> are prepared to create Makefiles.  The scripts may be re-generated
> in make stage, it's because time stamp doesn't change properly, I think.
> I don't know the way to avoid re-generating other than committing same
> files.

I am no automake or autoconf expert, but in my very short experience, I have seen very few
projects that keep the 'configure' script in CVS. In other words, they leave the
bootstrapping out of CVS. However, I don't really see how that affects anything (after all,
the 'configure' script itself is what generates the Makefiles).

Thank you.
| Mohammed Elzubeir    | Visit us at:                 |
|                      |  http://www.arabeyes.org/    |
| Arabeyes Project     | Homepage:                    |
| Unix the 'right' way |  http://fakkir.net/~elzubeir/|
Was I helpful? Let others know:

Attachment: pgp00024.pgp
Description: PGP signature