From: Stefan Z. <sz...@gm...> - 2011-08-30 21:51:38
|
On Tue, Aug 30, 2011 at 5:53 AM, Andrew Ward <and...@gm...> wrote: > Thanks for your suggestion Stefan, it works well. > The product I work on has scripting in multiple languages built-in to the > executable and we use SWIG to generate the application specific API for each > language. For historical reasons the implementation of the API must reside > in the main application executable and this is why I link the SWIG C++ > output for each language into the application executable and each scripting > language wrapper calls the functions exposed by the executable. Ideally I > would have had a separate shared library for each supported language, but > the way it is done works fine and does not require sweeping changes to our > build system. OK, that makes sense. I couldn't think of any technical reason why you would do it that way, but preserving legacy code is a perfectly valid reason. Thanks, Stefan |