Go to the FreeLists Home Page Home Signup Help Login
 



[openbeosstorage] || [Date Prev] [06-2003 Date Index] [Date Next] || [Thread Prev] [06-2003 Thread Index] [Thread Next]

[openbeosstorage] Re: Amiga RDB

  • From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
  • To: openbeosstorage@xxxxxxxxxxxxx
  • Date: Thu, 12 Jun 2003 13:08:19 +0200 (MEST)
On Thu, 12 Jun 2003, Axel Dörfler wrote:

> Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> > On Wed, 11 Jun 2003, Axel Dörfler wrote:
> > > Fair enough - but I'll try to be faster than you this one time :-)
> > I wouldn't be too disappointed. ;-)
>
> Well, perhaps you will if I messed it up ;-))

I'm faithful, that you won't. :-)

> > > Maybe I will just move it then before doing any changes. We might
> > > want
> > > to recompile it with different capabilities though at a later time.
> > Different capabilities?
>
> Yes, for example: why should we compile the whole driver_settings suite
> into the boot loader which only needs one way parsing of files/strings?

The partition/FS modules may want to use unparse features to create the
[content] parameter strings. I suspect, in most cases an sprintf() (is it
available in the boot loader?) will do just fine, but one never knows...

> Something like that - maybe it's not even an issue, but if we got space
> issues some day...

Are there any space restrictions to the boot loader? Other than that it
has to fit on the boot media, of course -- which, I suppose, could be an
issue only for floppy disks, which will face extinction earlier or later
anyway.

> well, a .a archive would do fine, though - but
> that's not compatible with a shared library since its contents won't be
> exported (at least I didn't find a way to do that, and it somehow
> negates the sense of those .a's).

One can, of course, re-extract the object files from the archive, but then
it makes little sense to build one in the first place. :-)

CU, Ingo





[ Home | Signup | Help | Login | Archives | Lists ]

All trademarks and copyrights within the FreeLists archives are owned by their respective owners.
Everything else ©2007 Avenir Technologies, LLC.