Re: generating mach-o executable files by hand
Re: generating mach-o executable files by hand
- Subject: Re: generating mach-o executable files by hand
- From: Joel Reymont <email@hidden>
- Date: Fri, 9 Jan 2009 20:33:50 +0000
Terry,
On Jan 9, 2009, at 8:03 PM, Terry Lambert wrote:
I assume you very much understand the difference between a linker
and a loader; the ld command can act both as a linker and a loader,
but by preventing it acting as a linker, you are cutting yourself
off from linking against libraries other than the ones you already
know about.
[...]
PS: I'm also still not seeing why you don't want to be able to link
your compiler's output with third party supplied libraries.
Because that's not how Forth works, at least not this Forth. I can use
any libraries by dynamically loading them into the running image. At
least I think I can with the Mach-O logic I'm using currently. If my
generated Mach-O does not support it then I'll need to modify my logic.
--
http://wagerlabs.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden