On Tue, 2008-04-15 at 13:26 +0200, Vincent Torri wrote:
> >>> I have already patches for the compilation with cegcc (i've not tried
> >>> mingw32ce yet) of zlib and others, but I think that it would be
> >>> interesting to have a site like gnuwin32, which lists and proposes
> >>> libraries compiled with cegcc and/or mingw32ce. That would certainly save
> >>> people a lot of work.
> >>> I've been thinking about that myself.
>
> If you are interested, We can begin with zlib.
>
> I have a patch for the Makefile.gcc in the win32 subdir of the 1.2.3
> version of zlib (that can be found in the homepage)
>
> I can provide the source, bin and dev zip files, with a README which
> describes:
>
> * the diff
> * what is important to change in the Makefile
> * the compilation options
>
> I've already begun to work on libjpeg (which requires librle, it seems,
> at least for the programs, not the dll). The dll compiles flawlessly, but
> i've not tested it yet.
I'd like to figure out how to get all this organised and streamlined
before we actually start.
Here are some suggestions, please all comment so we can agree on
something that works for all :
1. Generic stuff
a) All submissions should be ports of a software that falls under some
free software license.
b) A minimal submission is a source port. A compiled version is optional
but desirable.
c) Submissions must be accompanied by a document which describes the
port. We'll design a template for that.
d) Compiled versions should use a standard set of compiler and configure
options :
PREFIX=/opt/wince
CFLAGS="-D_WIN32_WCE=0x0400 -D_WIN32_IE=0x0400"
2. Template
a) the license of the software
b) the URL from which to download the original version
c) the version of the software from which this port is derived
d) the maintainer of this port
e) a source patch
f) the version of cegcc that this is compiled with
(version number + architecture: e.g. arm-mingw32ce)
f) (optionally) description of porting issues
g) (optionally) file name of full source (patched)
h) (optionally) file name of binary version
The filled out template could go in the release notes in the SF file and
release mechanism.
3. Stuff derived from working with the SourceForge file and release
system.
a) for practical reasons, a limited set of people is currently capable
of accessing the SourceForge cegcc site, they are a filter.
b) Submissions must be uploaded in agreement with one of the people
outlined above, knowing that the SF upload facility keeps files for a
limited amount of time, so be prepared to upload again if the agreement
is not clear enough and nobody had the time to pick up your files before
SF expired them.
Comments please.
Danny
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel
