library formats
library formats
- Subject: library formats
- From: Ross Boylan <email@hidden>
- Date: Tue, 21 Feb 2006 16:52:59 -0800
- Organization: University of California San Francisco--Biostatistics
Can anyone summarize, or direct me to a summary, of the requirements for
mixing and matching different library and object formats?
In particular, I have an R package (a module for a statistics system)
that includes C code in the LAM library. LAM was present only as .a
and .la files, not .dylib. The R module included a .so file, which I
think is a "bundle". The LAM code seems to be inside the .so file
(otool shows no external links to lam, and does show symbols and code
inside the .so file). And it all seemed to work.
I am used to dynamically loaded code requiring special options at
compile and link time, and would expect static (.a) libraries not to
work in this scenario. The docs I've seen mention no such restriction
for Darwin, though I've seen some references to PIC (compile time)
helping performance. One non-apple site said the common option was
necessary.
Basically, I'm wondering what combinations of compile and link formats
are possible, and which are recommended.
Thanks.
--
Ross Boylan wk: (415) 514-8146
185 Berry St #5700 email@hidden
Dept of Epidemiology and Biostatistics fax: (415) 514-8150
University of California, San Francisco
San Francisco, CA 94107-1739 hm: (415) 550-1062
_______________________________________________
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