Re: statically linking plugin .o files?

From: Dom Lachowicz (domlachowicz@yahoo.com)
Date: Tue Mar 04 2003 - 23:38:56 EST

  • Next message: Andrew Dunbar: "Commit: plugin c casts upgraded to c++ casts"

    Yeah, so there are two ways that I can think of to do
    this.

    1) ifdef out a bunch of functions, reorganize code,
    change your makefiles, and then link them in

    2) Copy over the unix loadAllPlugins function from
    AP_UnixApp. This includes the "so_only" function. Call
    this on application startup in some sort of initialize
    function. Build and install the plugins without
    changing a line of code.

    You can pretty much guess which one I'd rather do. And
    it ain't #1.

    Dom

    --- Seth Delackner <seth@jtan.com> wrote:
    > On Tue, Mar 04, 2003 at 08:56:33PM -0500, Mark
    > Gilbert wrote:
    > > I don't know that you have, this is a good idea (I
    > fooled around with it
    > > long back, when I knew a lot less about the
    > system, and got nowhere).
    >
    > Well, all I really care about are the image and file
    > converters. Near as I can
    > tell most of the ones that work are essentially
    > unchanged from the pre-plugin
    > incarnations they had. I hope the answer isn't that
    > I just ifdef out the
    > function definitions.
    >
    > Why am I doing this? I have no idea how to load the
    > plugins at runtime in the
    > abiconvert tool. Eventually I would like to shift
    > to doing that.

    __________________________________________________
    Do you Yahoo!?
    Yahoo! Tax Center - forms, calculators, tips, more
    http://taxes.yahoo.com/

    This archive was generated by hypermail 2.1.4 : Tue Mar 04 2003 - 23:45:08 EST