[PATCH 0/2] mtd-utils export libraries

[Mike Frysinger]

On Wed, Jan 7, 2009 at 11:15, Artem Bityutskiy wrote:
> On Wed, 2009-01-07 at 11:08 -0500, Mike Frysinger wrote:
>> On Wed, Jan 7, 2009 at 07:39, Sidney Amani wrote:
>> > What we are trying to do is an UBI based userspace filesystem (using fuse).
>> > We use the libubi to get volumes and devices info (ubi_get_dev_info,
>> > ubi_get_vol_info, ubi_get_dev_info1, ubi_get_vol_info1).
>> > Otherwise we communicate with the UBI volume through the cdev driver.
>> > I am not sure a shared library is really desirable, probably not,
>> > anyway it's not fundamental for us...
>> > I particularly though that it could be useful for ubi-tools but I also
>> > realize that it's much more restrictive to have shared libraries.
>>
>> i'm not terribly familiar with the fuse implementation details.  are
>> new filesystems plugins or shared libraries or standalone executables
>> or ... ?  i.e. are you going to be linking the UBI code into another
>> library or into a final application ?
>
> I believe they should first actually _develop_ their file-system. I
> believe they will change/improve the libubi a lot during the
> development. And then we may think about a shared library.

i was inquiring after building a PIC version of libubi for
applications/libraries to link against.  that way people can use it
but still leaves the API open for changes since there is no ABI.
-mike