This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libffi package
Tom Tromey <tromey@redhat.com> writes:
>>>>>> "Thomas" == Thomas Heller <theller@python.net> writes:
>
> Thomas> As soon as features are added or functionality is changed, libffi needs
> Thomas> another version number. Or something like that. Unless you see CVS
> Thomas> (branch?) tags as version numbers.
>
> We could do separate libffi releases and use whatever versioning
> scheme for them that we like, I think. So I think we're ok here.
> Actually, doing release separate from gcc is best all around, since in
> the gcc tree libffi is built as a convenience library and then only
> used by libgcj.
>
> Thomas> About features: I need additional features (for Windows at
> Thomas> least) which currently are not supported by libffi.
>
> Yeah. I think that is all fine, assuming the usual stuff (coding
> standards, maintainability, test cases, etc).
I guess the start would be to upload some patches, and/or maybe discuss
the implementation of new features.
The question is: where to start? I remember some time ago I tried to
checkout the HEAD, but that didn't build. As I said before, using the
gcc_3_3_2_release tag were more successful.
Thomas