could someone please briefly explain the diff between a dylib and a bundle (I gather the latter is a collection of libs?), and why you'd use one over the other.
I only create dylibs from my plugins but maybe I should understand this better. Thx! Peter. On 2/10/07, Alfred Van Hoek <[EMAIL PROTECTED]> wrote:
It possibly is a question for xcode, but nonetheless (could be useful for others on this list). 1) We have two similar targets defined in xcode, target 1 uses exclusively an older static lib, while target 2 uses the new static lib. Both libs define their own header file, with the same name, "LibHeader.h". There are differences. When the dylib option is used, xcode specifies in its target: Dylib: Copy Headers Link Binary With Libraries Compile Sources but for a bundle, Bundle: Copy Bundle Resources Compile Sources Link Binary With Libraries The Bundle option therefore does not allow the specification "LibHeader.h" at a defined path during a compile, leading to compile errors. It also does not help when the header search path is set in the target->get info. Perhaps someone has an idea? Alfred _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
-- ------------------------------------------------------------------------------- Peter K. Stys, MD Professor of Medicine(Neurology), Senior Scientist Ottawa Health Research Institute, Div. of Neuroscience Ottawa Hospital / University of Ottawa Ontario, CANADA tel: (613)761-5444 fax: (613)761-5330 http://www.ohri.ca/profiles/stys.asp ------------------------------------------------------------------------------- _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
