On Tue, May 26, 2009 at 9:53 PM, DJ Delorie <[email protected]> wrote: > >> How do you do: >> gcc -c swig_wrapper.c >> gcc -shared pcb swig_wrapper.o -o swig_pcb.so >> without gcc cursing at you? > > %.so : %.c > gcc $(INCLUDES) -g -O2 -Wall -shared $< -o $@ >
This creates DYN objects for each .c file, the objects created during PCB's current build are REL not DYN... The goal was to have PCB and the bindings not have duplicate object code... which a shared library would solve. > Shared libraries can have cyclic dependencies with the app that loads > them. You don't link against the app, though. > True, but this is a different case where the app is not the one loading the bindings... and the functions at the core of the executable need to be accessed. Hence a shared library with those core functions would allow the bindings and app to not duplicate code. It looks like Igor's hid extension gets around this by the app loading the extension which then provides access to the core functions to the scripting language. Lots of middlemen that aren't really needed for bindings. I think I'm starting to understand my misconception, instead of PCB being an architecture having core technology (e.g. auto routing, etc...) that could be used by and expandable into other programs, everyone has to add-on to PCB... I was thinking of it the other way around. Oh, well. Jason _______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
