[Bug 782] New: Please support building against npapi-sdk as well

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=782

           Summary: Please support building against npapi-sdk as well
           Product: IcedTea-Web
           Version: hg
          Platform: all
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Plugin
        AssignedTo: dbhole at redhat.com
        ReportedBy: mgorny at gentoo.org
                CC: unassigned at icedtea.classpath.org


Created an attachment (id=566)
 --> (http://icedtea.classpath.org/bugzilla/attachment.cgi?id=566)
A simple patch to support npapi-sdk

NPAPI-SDK [1] is a package providing a tiny set of NPAPI headers. It is used by
a few browsers already. We [Gentoo] are working on making that package used by
plugins as well.

That's why the project was temporarily forked [2] to a version providing a
pkg-config file for it. We're going to have that patches pushed in the next few
days, so we are already pinging upstreams to prepare their buildsystems. We
will be also working on removing the relevant headers from Mozilla products and
making them reuse NPAPI-SDK as well.

Packages building against NPAPI should use 'npapi-sdk' pkg-config package. If
it's necessary to perform any kind of version check, the SDK package version
will correspond to NPAPI version, and that version should be checked (rather
than libxul/firefox version).

I'm attaching a quick patch which makes icedtea-web build fine with npapi-sdk.
Considering that the work is done on npapi-sdk 0.27, which corresponds to
Firefox 6.0/xulrunner 2.0, I've added a little hack to omit libxul version
check. Of course, it would be more correct if the code used NPAPI versions
instead.

[1]:http://code.google.com/p/npapi-sdk/
[2]:https://github.com/mgorny/npapi-sdk/


-- 
Configure bugmail: http://icedtea.classpath.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.