public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@chez-thomas.org>
To: max <maxrtos@yahoo.com>
Cc: eCos Discussion <ecos-discuss@sources.redhat.com>,
	"David Marqvar (DAM)" <DAM@tt.dk>
Subject: Re: [ECOS] Opening SGML-manuals
Date: Fri, 21 Jun 2002 06:49:00 -0000	[thread overview]
Message-ID: <1024666819.4603.318.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <20020621132259.56280.qmail@web21309.mail.yahoo.com>

On Fri, 2002-06-21 at 07:22, max wrote:
> 
> --- Gary Thomas <gary@chez-thomas.org> wrote:
> > On Thu, 2002-06-20 at 04:43, Iztok Zupet wrote:
> > > On Thursday 20 June 2002 09:42, David Marqvar
> > (DAM) wrote:
> > > > Hello.
> > > >
> > > > I'm currently trying to get into the details of
> > eCos.
> > > > I've downloaded the latest CVS, including
> > documentation in SGML.
> > > >
> > > > How do I open the SGML-files? I've tried to use
> > sgml2html (linux) and
> > > > "SoftQuad XMetaL 3.0" (windows).
> > > > It seems that I need a Rules File, a DTD or a
> > Schema... I'm missing
> > > > something obviously..?
> > > >
> > > > Regards,
> > > > David Marqvar
> > > 
> > > Hi:
> > > 
> > >    Since I haven't updatet my eCos witht thel last
> > update (i'ts 3 weeks old), 
> > > my information may be out of date. 
> > > 
> > >  Seems that the only way one can try to build the
> > docs is:
> > > 
> > > Go to the ecos/doc/sgml directory and hack
> > makemakefile shell script , eg 
> > > replace every occurence of "ecc" with "packages".
> > >  -./makemakefile
> > >  -make
> > > Then You will notice that there are some
> > unresolved SGML link errors. Just 
> > > remove the links from SGML sources, because there
> > are some mising sgml files 
> > > in the repository tree.. The SGML documentation
> > scheme is new in the eCos 
> > > 2.0. ( I haven't tried that).
> > 
> > A much simpler way to do this is (on Linux):
> >   % cd XXX/ecos        // wherever your top-level is
> > installed
> 
> Just build in ecos repository?
>

Yes, that's how it's [currently] set up.
 
> 
> >   % ln -s packages ecc
> >   % cd doc/sgml
> >   % ./makemakefile
> >   % make html
> > 
> > This worked fine for me, no unresolved links, etc.
> > 
> > 
> > -- 
> > Before posting, please read the FAQ:
> > http://sources.redhat.com/fom/ecos
> > and search the list archive:
> > http://sources.redhat.com/ml/ecos-discuss
> > 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
> 
> -- 
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss



-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

      parent reply	other threads:[~2002-06-21 13:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20  0:42 David Marqvar (DAM)
2002-06-20  3:42 ` Iztok Zupet
2002-06-20  5:29   ` Gary Thomas
2002-06-20  9:44     ` Iztok Zupet
2002-06-21  6:23     ` max
2002-06-21  6:40       ` max
2002-06-21  6:49       ` Gary Thomas [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1024666819.4603.318.camel@hermes.chez-thomas.org \
    --to=gary@chez-thomas.org \
    --cc=DAM@tt.dk \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=maxrtos@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).