Apple

On May 30, 2008, at 10:44 AM, J. Todd Slack wrote:

Hi Jean-Daniel,

On May 30, 2008, at 10:41 AM, Jean-Daniel Dupas wrote:
ld: absolute addressing (perhaps -mdynamic-no-pic) used in +[NSStatusBar(Addition) createStatusBarItemTiteled:withImageNamed:withAltImageNamed:doesHighlight:menu:length:] from /Users/slack/Sites and Projects/Get It Online LLC/Ring-Maker-Plugin/build/Ring-Maker-Plugin.build/Release/Ring-Maker-Bundle.build/Objects-normal/ppc/NSStatusItemAddition.o not allowed in slidable image
collect2: ld returned 1 exit status
ld: absolute addressing (perhaps -mdynamic-no-pic) used in +[NSStatusBar(Addition) createStatusBarItemTiteled:withImageNamed:withAltImageNamed:doesHighlight:menu:length:] from /Users/slack/Sites and Projects/Get It Online LLC/Ring-Maker-Plugin/build/Ring-Maker-Plugin.build/Release/Ring-Maker-Bundle.build/Objects-normal/ppc/NSStatusItemAddition.o not allowed in slidable image
collect2: ld returned 1 exit status

It's an error about binary image file (executable, library, etc…) not about image in the graphic term.

What is the value for the "Generate Position Dependant Code" in your target build settings (for your plugin)? It should be unchecked for dynamic loadable code (plugin, libraries).

I unchecked it and it works now. Can you explain what "Generate Position Dependant Code" does? I would like to understand versus just accepting the answer.

Build Fixed-Position Application Code

By default, most code is built with the -dynamic compiler option. This option enables indirect symbol addressing and position-independent code generation, which allows the generated code to be relocated within the virtual memory space of the process. For projects such as bundles and frameworks, this option is required. The dynamic-linker must be able to relocate the bundle or framework and patch up symbol references at runtime.

Unlike bundles and frameworks, applications do not need the position-independent code generation feature provided by the -dynamic option. Application code is never relocated within the process space. However, it does still require the indirect addressing feature to allow for dynamic linking to other code modules, such as bundles. To solve this problem, the GCC versions 3.1 and later support the -mdynamic-no-pic option, which disables position-independent code generation but allows indirect symbol addressing. You should always enable this option when building applications.

Note: In Xcode, you specify the -mdynamic-no-pic option by choosing the Generate Position Independent Code option from the Code Generation settings.

References:
	>What? (From: "J. Todd Slack" <email@hidden>)
	>Re: What? (From: Jean-Daniel Dupas <email@hidden>)
	>Re: What? (From: "J. Todd Slack" <email@hidden>)