On Sunday, Dec 19, 2004, at 18:12 Europe/Stockholm, Edward Agabeg wrote:
Edward Agabeg on Sunday, December 19, 2004 at 2:01 AM -0500 wrote:
Subject: Xcode QT component?
To: QuickTime API List <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; format=flowed
What project type should I use to build a QuickTime component with
Xcode? I can't find any code samples on Apple's website.
- Andreas
Carbon dynamic library, then follow the instructions outlined in TN
2012 for Mach-O. Ignore all the legacy CFM, OS 9 stuff obviously.
Also, see Electric Image Component sample (includes five components).
Just realized, that will get you a non-bundled component. So, more
accurately you should start with the new project type "Carbon Bundle"
in Xcode. Remember to rename it to .component instead of .bundle
Both works. I tend to prefer the library kind instead of the bundle
kind. A bundle is a whole directory structure, which is fine for an
application but overkill for a simple QT component. Just create a
dynamic library and give it a .component extension. Works fine, but
Apple seems to prefer the bundle kind.
For a library component, external code you link needs to be compiled
with -fPIC. That's the only difference I've found.
If your component has support applications and multi-language NIB files
etc, a bundle would be more appropriate.
/Roine
_______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-API mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quicktime-api/email@hidden
