Home/ Questions/Q 524547
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T08:34:45+00:00

I am maintaining a small application that has some plugin-like functionality, which is implemented

  • 0

I am maintaining a small application that has some plugin-like functionality, which is implemented through runtime-loaded dynamic modules.

Specifically, since it’s a Gtk+ app, I’m using gmodule, but the question applies to dlfcn.h / dlopen() based dynamic library loading just as well.

My main program has a single, global struct variable holding some global information. I want this information to be available to functions defined in the dynamically loaded plugins.

On Linux, I could just refer to this global variable directly – this works well, and I’m guessing that gcc or the linker take care of exporting the global variables from the main program to dynamic libraries.

Problem is, this doesn’t work on Mac OS X. Is there a way to do this on OS X?

If not, is there a more “best practice” way to expose global information to dynamically loaded libraries?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Put the global in main.c and declare it extern in the shared object, and try this:

    MACOSX_DEPLOYMENT_TARGET=10.3 ld -dylib -undefined dynamic_lookup -o multiply.so multiply.o

    or

    MACOSX_DEPLOYMENT_TARGET=10.3 libtool -dynamic -undefined dynamic_lookup -o multiply.so multiply.o

    It worked for me on Mac OS X 10.4

    • 0