Difference between revisions of "Development:Third-Party Preference Panes"

From Camino Wiki
Jump to navigation Jump to search
(Minor cleanup and clarification.)
(Cleanup/clarification.)
Line 11: Line 11:
  
 
* Get info on your target (or project) and set "Other Linker Flags" to "-undefined dynamic_lookup" for all configurations
 
* Get info on your target (or project) and set "Other Linker Flags" to "-undefined dynamic_lookup" for all configurations
 
+
* You only need the appropriate header files (the header files for the classes you're using/subclassing) if you're using -undefined dynamic_lookup; you don't need to link against the Gecko code (often, this is just PrefPaneBase.h)
* you actually only need the proper header files if you're using -undefined dynamic_lookup
 
* you just need to make sure you've imported the headers into your project and you only need headers you're using
 
  
 
===Camino doesn't like my prefPane; it says it has to have a 'MOZC' signature===
 
===Camino doesn't like my prefPane; it says it has to have a 'MOZC' signature===

Revision as of 10:49, 21 August 2006

This page is very much under development

How do I build a prefPane for Camino?

Error messages

Undefined Symbols

it compiles ok, but if it's in deployment mode I get an undefined symbol error

  • Get info on your target (or project) and set "Other Linker Flags" to "-undefined dynamic_lookup" for all configurations
  • You only need the appropriate header files (the header files for the classes you're using/subclassing) if you're using -undefined dynamic_lookup; you don't need to link against the Gecko code (often, this is just PrefPaneBase.h)

Camino doesn't like my prefPane; it says it has to have a 'MOZC' signature

  • Get Info on your prefpane target
  • Go to "Properties"
  • Change the "Creator" field to "MOZC" (without quotes).