[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] Incorporating other calls into the
- To: MiNT mailing list <mint@fishpool.com>
- Subject: Re: [MiNT] Incorporating other calls into the
- From: "Guido Flohr" <gufl0000@stud.uni-sb.de>
- Date: Mon, 28 Jun 1999 10:31:45 +0200
- In-reply-to: <199906280338.XAA27088@sparticus.bright.net>; from Lonny Pursell on Sun, Jun 27, 1999 at 11:38:12PM -0400
- Mail-followup-to: MiNT mailing list <mint@fishpool.com>
- References: <199906280338.XAA27088@sparticus.bright.net>
- Sender: owner-mint@fishpool.com
On Sun, Jun 27, 1999 at 11:38:12PM -0400, Lonny Pursell wrote:
> >Anyway, if there is a chance for a conversion - good news for you - I have
> >recently written a library converter. It should be possible to do the
> >same for the format you need.
>
> i don't have this doc in text form it's in a book.
> so i type it in:
>
> first 2 bytes are magic number FF65 (hex)
> ...
OK, and the object files. Let me guess:
struct drexec {
short a_magic; /* Always 0x601a. */
ulong a_text; /* Size of text segment. */
ulong a_data; /* Size of data segment. */
ulong a_bss; /* Size of bss. */
ulong a_syms; /* Size of the symbol table. */
char reserved[10]; /* Always zero. */
};
What is the format of the symbol table? What is the name of the symbol
index in the library archive? Could you please create a library from two
really small (!) object files, plus the source both in C (Pascal, or
whatever) and Assembler. I will be able to figure out the rest then.
But you will have to be able to find a way to pass parameters on the
stack, not in registers. Otherwise things won't work.
Ciao
Guido
P.S.: Please make sure that in the object files you use both short symbol
names and long ones. Is there any limit in the length of a symbol name?
--
http://stud.uni-sb.de/~gufl0000
mailto:gufl0000@stud.uni-sb.de