Creating Custom Firefox Extensions with the Mozilla Build System

Actually there are sure to be a bunch of issues with using this on trunk (e.g. the library paths). I'll try to fix it when I have time.

-- User:Plasticmillion 11:25, 3 January 2007 (CET)

Has anyone tried these instructions with trunk/1.9? I think they should work fine, in which case the warning at that top could be removed.

-- User:Plasticmillion 20:05, 2 January 2007 (CET)

Random notes :)

  • Would it not be a good idea to set MOZILLA_STRICT_API=1 in any Makefile.in that builds C++ sources, to avoid using nonfrozen interfaces?
  • Similarly, might want to set NO_JAR_AUTO_REG=1 in any Makefile.in near the jar.mn files - assuming you actually want to install the extension to test and not have it show up in all profiles in that Firefox build :)
  • Might want to note somewhere that, for you component to work on Windows with normal Firefox, you need to use a Microsoft C++ compiler and not any variant of GCC.
  • Using Dependent Libraries In Extension Components should probably be linked to in the # Using Third-Party Libraries section? Otherwise anybody using DLLs won't work :)

-- Mook 16:17, 18 January 2006 (PST)

Document Tags and Contributors

Contributors to this page: Plasticmillion, Mook
Last updated by: Plasticmillion,