> >I am attempting to write a gimp plugin to 'bridge' between the gimp > >and a 3rd party piece of technology, under Linux. > > > > [...] > > > >My users need to stay with their currently deployed versions of > >software including the gimp (2.0.5) [...] > > If the code for your plugin will fit into a single C file, it is > a lot simpler to build and install it using the "gimptool-2.0 -- > install" > command. I'll work through some examples using the gimptool-2.0, but I don't think it is enough for the proof of concept. Unfortunately, the technology I'm bridging too isn't quite C/C++, though it does implement an 'extern "C"' calling interface, and does follow gcc ABI. But, I don't see a sure-fire way to build a plugin bridge within a single file, and even if I can do it somehow, it may be more clunky that having a multi-file build. This is only part of the complexity I need to sort out; there may be lots of other fun ways for it to break, it might have alternative, incompatible, implementation of library functions !-) That's what I'll find out. > As a framework for such a plug-in, you could start with > pretty much anything in plug-ins/common in the GIMP source code -- > you have to remove a few lines involving internationalization to > get a plug-in to compile using "gimptool --install", but it isn't > very difficult. Okay, I'm usually good at removing stuff. > > Also, you can find quite a number of plug-ins in the registry > (registry.gimp.org) that are specifically written for GIMP 2.0, > if you want a better starting point. Many are single-file plug-ins > that you install using gimptool, but a few are more complex. Ah! That feels like a great starting point. I've just had a quick dig through registry.gimp.org, and refocus-it looks like a 2.0 compatible multi-file build plugin, so I'll look at that. Thank you for the help. GB _______________________________________________ Gimp-developer mailing list Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
