This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Adding STLport to eCos
- From: Øyvind Harboe <oyvind dot harboe at zylin dot com>
- To: ecos-discuss at sources dot redhat dot com
- Date: Fri, 30 Apr 2004 09:11:37 +0200
- Subject: [ECOS] Adding STLport to eCos
- Organization: Zylin AS
My writeup on how to use STLport:
http://www.zylin.com/opensource.html
A list of things to consider:
- Is there any interest in doing this?
- STLport has its own makefile for compiling the source. I think trying
to change STLport to use eCos makefiles to compile itself is make-work.
The result of compiling STLport are a couple of linker libraries.
- Write a .cdl file. This .cdl file would expose a couple of sensible
configuration options, add STLport to the include path, add the STLport
linker libraries to the include path, etc.
- A couple of patches to STLport have to be committed. Minor stuff. Some
examples:
http://sources.redhat.com/ml/ecos-patches/2004-01/msg00068.html
http://sources.redhat.com/ml/ecos-patches/2004-02/msg00072.html
- STLport consists ~600k source tar.bz2'd and ca. 1400 files. It seems
like a lot, but not too much to add to the eCos CVS.
- license issues. Looks fine. http://www.stlport.org/doc/license.html
Cons?
- STLport will be obsolete if eCos supports libstdc++.
--
Øyvind Harboe
http://www.zylin.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss