[info-mcl] Mach-O foreign functions [was: RMCL Documentation]
terje at in-progress.com
Wed Jun 16 05:31:55 CDT 2010
On Jun 14, 2010, at 1:55 AM, Sandro Pedrazzini wrote:
> Does anyone know what are the current options for using foreign
> Are there different "define-entry-point" ways of referring to external
> libraries, and where are those libraries looked for?
> I am currently still using some "old-styled" Carbon libraries, setting
> the *dont-use-cfm* to NIL. In this case the library can be placed into
> the RMCL directory, added to the serch path with "ccl::add-to-shared-
> library-search-path" and found at runtime.
> I tried to use the same processing with a framework and with a Mach-O
> dynamic library (libXYZ.dylib file). Unfortunately it seems as if the
> library cannot be found, specifying it in different ways (full name,
> Unix shared library convension name, etc.).
> In the latter case (Mach-O dynamic library), the Mach-O address cannot
> be resolved.
> Any hint or documentation?
The old entry-point functionality seems less useful when it comes to Mach-O. To work around it, see e.g. the declare-bundle-ff in my kqueue.lisp:
-- Terje Norderhaug
More information about the info-mcl