[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-users] Re: [lwip] New CVS Tree
From: |
Jani Monoses |
Subject: |
[lwip-users] Re: [lwip] New CVS Tree |
Date: |
Thu, 09 Jan 2003 00:13:25 -0000 |
How about keeping addon archs in a separate CVS module and tarball?
The lwIP module could contain the unix arch needed for simulation
while specific ports could be downloaded by those interested.
Some advantages of this that I see:
-smaller download size and cleaner diffs between versions
-arch specific hacks kept out of core.If they're a must then the core
might need a clean solution to that so other ports benefit.
-separate releases.(No need to grab lwIP form CVS because a fix in arch foo
and no need to release a new lwip with only fixes in archs).
>
> 1. I have the Windows and DOS port, should I add them into the appropiate
> proj and src/arch directorys? I think this would be the best place for
> them. If I add them, I would have to add the already discussed change for
> packed structures. On Windows I can't define a macro to do the packing, so
> I would add two include files begin_pack_struct.h and end_pack_struct.h
> which then would be included before and after the relevant structs. Thos
> include files would be placed in the arch directorys for every architecture.
>
> 2. Should we add something like a contrib directory with addons for lwip
> like my ftp server? That folder wouldn't necessarily be supported by
> everyone, but only by the author of the addon.
>
> Florian
>
>
>
> [This message was sent through the lwip discussion list.]
[This message was sent through the lwip discussion list.]