On Jan 2, 2012, at 6:18 PM, Jeremy Cowgar wrote: > On 1/2/2012 8:10 PM, Alfred Van Hoek wrote: >> On Jan 2, 2012, at 2:14 PM, Jeremy Cowgar wrote: >> >>> am guessing I am missing a define somewhere that controls the compilation >>> of my project. >> Most likely. You need a prefix file, to set certain compiler flags. These >> flags depend on the compiler flavor (Carbon or Cocoa), so the plugin SDK >> knows what target will be used, depend on the master header file, for >> example<Carbon/Carbon.h>, or<Cocoa/Cocoa.h>. >> >> Without knowing what you exactly do, it is hard for people (including me) to >> respond. >> > > Thank you for the response. I am using makefiles and compiling with g++. I > have also attempted to compile my plugins in XCode, with the same failure. > If, however, I copy PluginMain.cpp and add #include <RBCocoaHeaders.h> to the > top, my plugin compiles and functions properly.
So that means that the compiler does not include the RBCocoaHeaders.h to properly compile PluginMain.cpp. You need a precompiled header file that will automagically handle the inclusion of the appropriate headers. > > What is confusing is that looking at the Complete Class plugin, it does not > contain such code You better look more carefully. In Xcode, you set in the settings the prefix file and that should have done the trick. > and I can compile it. I did notice the Prefix File option in the build > settings of XCode, but applying that to my project didn't seem to fix my > problem. > I've fought w/it all afternoon w/no success (other than editing > pluginmain.cpp as stated above). > Then fight even harder, or analyze better; it's something you are overlooking, I presume. - Alfred Van Hoek [email protected] http://web.mac.com/vanhoek _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
