public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Iztok Zupet <iz@vsr.si>
To: Gary Thomas <gary@chez-thomas.org>
Cc: "David Marqvar (DAM)" <DAM@tt.dk>,
	"'ecos-discuss@sources.redhat.com'"
	<ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Opening SGML-manuals
Date: Thu, 20 Jun 2002 09:44:00 -0000	[thread overview]
Message-ID: <200206201845.05967.iz@vsr.si> (raw)
In-Reply-To: <1024576161.4602.239.camel@hermes.chez-thomas.org>

On Thursday 20 June 2002 14:29, Gary Thomas 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
>   % ln -s packages ecc
>   % cd doc/sgml
>   % ./makemakefile
>   % make html
>
> This worked fine for me, no unresolved links, etc.

 After updating my ecoscvs the documentation builds with only two missing 
xrefs:

jade:../../ecc/kernel/current/doc/kernel.sgml:222:69:X: reference to 
non-existent ID "COUNTERS-CLOCKS-AND-ALARMS"
jade:../../ecc/kernel/current/doc/kernel.sgml:1703:22:X: reference to 
non-existent ID "COUNTERS-CLOCKS-AND-ALARMS"
jade:../../ecc/kernel/current/doc/kernel.sgml:1116:59:X: reference to 
non-existent ID "MEMORY-POOLS"
jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.76/html/dblink.dsl:203:1:E: 
XRef LinkEnd to missing ID 'COUNTERS-CLOCKS-AND-ALARMS'
jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.76/html/dblink.dsl:203:1:E: 
XRef LinkEnd to missing ID 'MEMORY-POOLS'
jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.76/html/dblink.dsl:203:1:E: 
XRef LinkEnd to missing ID 'COUNTERS-CLOCKS-AND-ALARMS'
make: *** [ecos.html] Error 1

But nevertheless the html tree works and seems to be fully browsable.

 Intresting, I've been using eCos cvs reposytory ever since 1.2x version but 
never noticed such a heavy load on the cvs server. (load average 56). 
 I wander if this heavy cvs access is related to the latest talks about RedHat 
and eCos and eCos developers and if the cvs snapshot at chez-thomas.org is 
accessed that much, too. 

Regards
iz

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

  reply	other threads:[~2002-06-20 16:44 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 [this message]
2002-06-21  6:23     ` max
2002-06-21  6:40       ` max
2002-06-21  6:49       ` Gary Thomas

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=200206201845.05967.iz@vsr.si \
    --to=iz@vsr.si \
    --cc=DAM@tt.dk \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gary@chez-thomas.org \
    /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).