Hi Alfred, When moving to the new bundle type, I had real problems using Xcode's "bundle" presets. Instead, I modified my existing non-bundle UB dylib to have the appropriate bundle settings (as described by Jonathan in his original email on the subject), rather than using a bundle template, and this seemed to work just fine.
You can see this in the latest version of my UB plugin template (v1.3): http://www.thismuchiknow.co.uk/?p=20 Dave. > From: Alfred Van Hoek <[EMAIL PROTECTED]> > Reply-To: REALbasic Plugins <[email protected]> > Date: Sat, 10 Feb 2007 10:35:00 -0500 > To: REALbasic Plugins <[email protected]> > Subject: dylib to bundle > > 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> _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
