lynx-dev
[Top][All Lists]

## Re: lynx-dev Re: Lynx .IDE file for Borland C ++

 From: Mike Bledig Subject: Re: lynx-dev Re: Lynx .IDE file for Borland C ++ Date: Thu, 6 Jan 2000 10:35:15 +0200

```Hi there to all.

The thing is, I'm compiling the lynx as per the instructions found in
the Installation document.  There seems to be some differences
between the document and to what one must do to get the thing to
compile.

I have copied some of what the document says.  Note: some text
has been omitted so as to shorten the document.  I have
highlighted where I find the discrepancies.

IV. Compile instructions -- Win32

(Windows95/98/NT)

Before compiling the Lynx sources, you need a curses library, and
it is recommended that you have the zlib library.  Get
pdcurses2.3...  You will want to get zlib...  Compile these libraries,
and put them in a convenient place (pdcurses inside the Lynx
directory).

*Wrong!* Had to make the directory above the lynx directory.

Unpack the latest Lynx source distribution, and make an obj
directory under the source root to contain the compile output.
*Wrong!* Had to make the directory above the Lynx directory.

First build the .h files in src\chrtrans using "makew32.bat".  Double
check for new .tbl files; hand edit in any new ones, and then do
"makew32". Jump into Borland C++, load the project (IDE file) and
compile Lynx. Alternately, after compiling the chartrans tables, you
can come back to the top directory and compile manually, i.e., do
"make -f makefile.bcb".

The thing is, I think that there's something wrong with my .libs.
Because when I compiled the source for the pdcurses.lib, I got a
lot of warnings.  Could that be the problem?

Now I've just got to figure it out.  The source is compiling ok, but

Original message follows:
Subject:                Re: lynx-dev Re: Lynx .IDE file for Borland C ++

> On Wed, 5 Jan 2000, Klaus Weide wrote:
>
> > On Sat, 8 Jan 2000, Vlad Harchev wrote:
> >
> > >  The 'current_codepage' is referenced in the following code
> > >  fragement in
> > > LYCurses.c:
> > >
> > > #if defined(WIN_EX) && defined(CJK_EX) /* 1999/08/26 (Thu)
> > > #17:53:38 */
> > >     {
> > >         extern int current_codepage;    /* PDCurses lib. */
> > >
> > >         if (current_codepage == 932)
> > >             LYcols = COLS - 1;
> > >     }
> > > #endif
> >
> > So he is compiling with CJK_EX.  Why?  I don't know, but let's
> > assume he wants and needs it.
> >
> > >  Just hide this fragment from compiler - eg change 1st line to
> > > #if 0 && defined(WIN_EX) && defined(CJK_EX) /* 1999/08/26 (Thu)
> > > #17:53:38 */
> > >  You don't need this fragment.
> >
> > How do you know that he doesn't need it?
> >
> > Do you understand what the code is for?  (I don't.)  If he wants to
> > compile the CJK Extension, and that code is part of the CJK
> > Extension, then the normal assumption should be that he *does* need
> > that code.  If the code didn't do anything, presumably it wouldn't
> > be there.
>
>  As I remember, -DCJK_EX is in makefile he is using. So treat this as
>  not
> intentional (ie he doesn't want CJK extensions, but he doesn't know
> that he will get them by default :)
>  But don't worry: I don't understand what that code does :-)
>
> >
> >    Klaus
> >
>
>  Best regards,