I can include functions if I extend past gaze and check additional
information... since I can create a list of binary objects installed
along with other objects installed and check the file type and respond
with full ldd information from the install log entries that respond as
"executable" object type...
how much information is needed as it'll be a toshiba tecra laptop
On Wed, 2005-27-07 at 16:53 -0400, Scott W wrote:
Henning Nielsen Lund wrote:
And a little question... do you know if it is going to include functions
(so we can check how many functions we need to implement - that are not
part of clib2 or newlib)?
thats why I asked for a template outline...
but it would all be "glibc" c library linkage... not
as I am entirely unsure how that differs from the above
I can only work from the installed system I am using unfortunately
Ouch. You want a call stack graph, or similar.
I'd be impressed if the
other tool does that, considering it's spanning languages..hekc, I'd
just be impressed, we'll leave it at that.
I also sent the last email prior to reading this one, so not sure if the
'base' dependencies list was useful or not. If not, sorry, back to lurk
mode I go :-(
I can do things graphically if I spend a bit more time...
otherwise i will have to do a whole folder tree and seperate text
information by what is needed so rather a LOT of generated data
(Im already running seriously short on diskspace as-is)
so ... needing to get offline for now and also needing a clear idea...
will get replies later when I get back online...
as soon as I see a template
I can do a package level graphic... including version change tracking
as well if needed over time...
additionally I can also throw in information about installed packages
on this laptop as well...
would need to rebuild sourcemage on top of newlib/clib2 instead of glibc
to have portability to AmigaOS sped up...
Send instant messages to your online friends http://au.messenger.yahoo.com