Home/ Questions/Q 5978561
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T21:32:01+00:00

I have registered a binary component in my chrome.manifest : binary-component components/linux/myLib.so abi=Linux_x86-gcc3 Now

  • 0

I have registered a binary component in my chrome.manifest:

binary-component components/linux/myLib.so abi=Linux_x86-gcc3

Now I want to pass its path to ctypes.open(). My question is: how do I reference the binary component so I can pass it to ctypes.open()?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The binary components listed in chrome.manifest should be XPCOM components. Yours on the other hand is a regular library, no need to list it in the manifest – it is a very “manual” approach instead. Your code needs to check nsIXULRuntime.XPCOMABI (see https://developer.mozilla.org/En/NsIXULRuntime) to see whether the platform is compatible. Then you need to get the location of your library file, something like this:

    Components.utils.import("resource://gre/modules/AddonManager.jsm");
AddonManager.getAddonByID("myAddon@foo.com", function(addon)
{
    var uri = addon.getResourceURI("components/linux/myLib.so");
    if (uri instanceof Components.interfaces.nsIFileURL)
    {
        ctypes.open(uri.file.path);
        ...
    }
});

    The first parameter to getAddonByID() needs to be replaced by the ID of your add-on of course. And the assumption here is that your add-on is installed unpacked (<em:unpack>true</em:unpack> specified in install.rdf) because otherwise there won’t be a file on disk to be loaded.

    • 0