This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Splitting out Jim to a seperate module from athttpd
- From: Sergei Gavrikov <sergei dot gavrikov at gmail dot com>
- To: ?yvind Harboe <oyvind dot harboe at zylin dot com>
- Cc: eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Thu, 15 Nov 2007 09:41:42 +0200
- Subject: Re: [ECOS] Splitting out Jim to a seperate module from athttpd
- References: <c09652430711142310v6a7e0362g9d71165c832f59d2@mail.gmail.com>
On Thu, Nov 15, 2007 at 08:10:28AM +0100, ?yvind Harboe wrote:
> Is there a reason why Tcl Jim is inside the athttpd package?
>
> It may be possible to use Tcl Jim without using the athttpd stuff when
> adding the athttpd package, and if so, it's only a matter of lack of
> documentation/marketing of that feature + I guess an estethic thing(no
> observable difference in executables by a seperate package) to split
> out seperate features in seperate packages. I haven't checked, but the
> athttpd probably relies on tcp/ip stuff which would make ecosconfig
> refuse to add that package in an environment without tcp/ip.
It seems, that eCos Jim package must live here
$ECOS_REPOSITORY/language/tcl/jim
SYNOPSYS
...
ecosconfig add athttpd
ecosconfig add jim
Sergei
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss