Mail Archives: djgpp/2001/08/13/08:46:53
> There is talk amongst the Allegro library developers of emulating some
> DOS functions to ease cross-platform migration. I personally think this is
> outside the scope of Allegro and should be available as a kit to provide
> some of the DJGPP library for other compilers.
OK, no problem here.
> I would like to start a Sourceforge project as outlined below, but as it
> would involve distributing your library code I thought I would ask you
> first.
Would it be easier to integrate the changes into the main djgpp source
repository? And what would you need out of djgpp's sources anyway?
As for licencing, as long as you're compatible with the LGPL (djgpp's
libc license), there's no problem. If you *use* djgpp's sources, it
must be LGPL. Note that you will not be able to offer the exception
djgpp does - anyone using this library will be *required* to
distribute it with source as per the LGPL.
> 1. Project Full Name
> DJGPP Suitcase
Hmmm... This might confuse people into thinking it is something that
works with djgpp, rather than something that emulates djgpp. I can't
think of anything better that isn't a whole sentence ;-)
> The primary goals are:-
>
> a) To support the filefirst() filenext() and fileclose() functions
> with the ffblk structure filled to the best of each O/Ses ability.
>
> b) The extra string functions which are not POSIX compliant, yet depended on
> by many, would be packaged for other compilers.
Have you checked out libiberty?
> 3. License
> LGPL - or whatever is more appropriate
If you're basing it on djgpp sources, it's LGPL.
- Raw text -