Version française
Home     About     Download     Resources     Contact us    
Browse thread
MacOS port and file formats
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Jacques Garrigue <garrigue@m...>
Subject: Re: [Caml-list] MacOS port and file formats
From: Mary Fernandez <mff@research.att.com>

> I have a question regarding the ./configure options for MacOS/Darwin.
> 
> ./configure selects the -bundle option for MKSHAREDLIB, which
> has the effect of creating MacOS bundle type files for the dynamically
> linked libraries in lib/ocaml/stublibs.  I have had trouble linking
> these bundle files with the standard dynamically linked libraries
> created with the -dynamiclib option.    As an experiment, I replaced
> -bundle by -dynamiclib and attempted to rebuild the O'Caml compiler,
> but got an error deep in compilation of the compiler.  Ultimately,
> I just made the otherlibs/* libraries by hand with -dynamiclib and was
> able
> to link my application.
> 
> I will admit that I am overwhelmed by the Darwin documentation
> that explains how to port a Linux application to MacOS. 
> Can someone explain why the -bundle option is necessary to the compiler
> compilation?
> Is it because the O'Caml compiler a full-fledged Mac application?

Could you explain exactly what you are trying to do?
The dlls in stublibs are only intended to be dynamically loaded by an
ocaml application. The reason bundles are used rather than dynamic
libraries is that the API for bundles is simpler, and that their
explicit intent (plugins) seems close enough to the use of dlls in
ocaml.
Note that a bundle can depend on dynamic libraries, so this should not
induce other limitations.

Jacques Garrigue