Hi Robert,
This just seems like a lot of work for no real gain since all 4
libraries are samll and closely related. To build LAME we would need
a ./configure setup which builds 4 different libraries. so I guess I
just dont see any reason to seperate them.
Special applications, like embeded encoding, will be
using static libraries anyway, so they can just compile
a lightweight version of libmp3lame.a.
Mark
>
>
> So for backward compatibility we should make a wrapper library
> with the old interface (as much as possible) and mark this as
> old and outdated, to give clients the possibility for smooth
> migration to the new API.
>
>
> old client new clients
> | |
> v |
> wrapper lib |
> | |
> +--------------------+---------
> | | |
> v v v
> lame-enc-lib lame-dec-lib lame-hdr-lib
>
>
> lame-enc-lib:
> - lame's encoding engine
> - maybe with Xing's VBR header stuff if it must be
>
> lame-dec-lib
> - lame's wrapper to the mpg123 library
>
> lame-hdr-lib
> - wave header
> - Xing header
> - ID3 stuff
>
>
> wrapper lib
> - the old libmp3lame and interface
>
>
>
> Ciao Robert
>
>
>
> --
> MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
>
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
