"The executable could not be loaded" error trying to load plug-in

View: New views
4 Messages — Rating Filter:   Alert me  

"The executable could not be loaded" error trying to load plug-in

by RobbieG :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,
I'm updating some plug-ins, for which we have the source code, to work on Intel Macs as well as be unicode compliant (therefore linking against the v11 plugin API). We have a test DB for testing the functionality of our plugin. All is well on Windows as well as the Intel Mac using the universal binary.

However, if I copy the same test DB and universal binary version of the plugin to a PPC Mac, the plugin doesn't get loaded properly. I don't get any error dialog or anything on startup, but if I look in the list of Plug-ins in the Explorer window and click on my plugin, there is red text which says:

Disabled
The executable could not be loaded

If I go to execute a method that uses any of the plugin methods, of course, I get an error dialog. It says there's a "License or privilege error" (Error -9949). The plugin doesn't use any kind of licensing and I've double checked the file permissions, and everything in the package, including the packaged itself is R/W. So, I have a feeling that error is a red herring.

Does anyone have any ideas as to what might be going on here? Any ideas of what to try? Any help would be greatly appreciated.


Thanks in advance,
Robbie

Re: "The executable could not be loaded" error trying to load plug-in

by Matthias Schmidt-6 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Am/On Tue, 17 Jun 2008 16:15:07 -0700 schrieb/wrote RobbieG:

>I'm updating some plug-ins, for which we have the source code, to work on
>Intel Macs as well as be unicode compliant (therefore linking against the
>v11 plugin API). We have a test DB for testing the functionality of our
>plugin. All is well on Windows as well as the Intel Mac using the universal
>binary.
>
>However, if I copy the same test DB and universal binary version of the
>plugin to a PPC Mac, the plugin doesn't get loaded properly. I don't get any
>error dialog or anything on startup, but if I look in the list of Plug-ins
>in the Explorer window and click on my plugin, there is red text which says:
>
>Disabled
>The executable could not be loaded
>
>If I go to execute a method that uses any of the plugin methods, of course,
>I get an error dialog. It says there's a "License or privilege error" (Error
>-9949). The plugin doesn't use any kind of licensing and I've double checked
>the file permissions, and everything in the package, including the packaged
>itself is R/W. So, I have a feeling that error is a red herring.
>
>Does anyone have any ideas as to what might be going on here? Any ideas of
>what to try? Any help would be greatly appreciated.

did you compile the plugin for both architectures - i386 and PPC?

Does the PPC run an unsupported OS (the Plugin is compiled for Leopard
and PPC runs on Tiger)?

cheers,

Matthias

------------------------------------------------------------------------
Admilon Consulting GmbH
Am Wiesengrund 9a, 90584 Allersberg, Germany
Geschäftsführer: Peter Frank, Matthias Schmidt
Amtsgericht Nürnberg: HRB 21750
Tel.: +49-9174 - 6646 Fax: +49-9174 - 6647
<http://www.admilon-consulting.de>
-------------------------------------------------------------------------


**********************************************************************
4D Plugins hosted by 4D, Inc.                      http://www.4D.com/


    Did you know?  The 4D Partner Program now gives you
    access to Hotfix releases as soon as they are available!
    To learn more, go to http://www.4D.com/support/partner.html

To Unsubscribe:                      mailto:4D-Plugins-off@...
***********************************************************************


Re: "The executable could not be loaded" error trying to load plug-in

by RobbieG :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Matthias Schmidt-6 wrote:
did you compile the plugin for both architectures - i386 and PPC?

Does the PPC run an unsupported OS (the Plugin is compiled for Leopard
and PPC runs on Tiger)?

cheers,

Matthias
Matthias,
I think you may be on to something...  First of all, please forgive my lack of experience on Macs.  I come from a Windows background.

So, when you say "the Plugin is compiled for Leopard," what do you mean exactly? I did build the plugin ON Leopard using XCode 3.0. But I have to believe that I can build on Leopard (even using XCode 3.0) and still have the Plug-in run on Tiger, right?  Looking at my XCode project, I have my Base SDK Path set as MacOSX10.5.sdk. This seems like a likely culprit. Hopefully it won't be too difficult to link against the older SDK. I'll give this a go and let you know where it gets me.

Thanks,
Robbie

Re: "The executable could not be loaded" error trying to load plug-in

by RobbieG :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Just an update... I was able to get my plugin working on PPC by downgrading my base SDK to 10.4u. I had to iron out some build issues, but I was still able to get it going in XCode 3.0 from my MacTel. Then, copying it over to a PPC worked just fine.

Good luck,
Robbie

RobbieG wrote:
Matthias Schmidt-6 wrote:
did you compile the plugin for both architectures - i386 and PPC?

Does the PPC run an unsupported OS (the Plugin is compiled for Leopard
and PPC runs on Tiger)?

cheers,

Matthias
Matthias,
I think you may be on to something...  First of all, please forgive my lack of experience on Macs.  I come from a Windows background.

So, when you say "the Plugin is compiled for Leopard," what do you mean exactly? I did build the plugin ON Leopard using XCode 3.0. But I have to believe that I can build on Leopard (even using XCode 3.0) and still have the Plug-in run on Tiger, right?  Looking at my XCode project, I have my Base SDK Path set as MacOSX10.5.sdk. This seems like a likely culprit. Hopefully it won't be too difficult to link against the older SDK. I'll give this a go and let you know where it gets me.

Thanks,
Robbie