Search completed in 1.70 seconds.
4 results for "XPIDL_MODULE":
Creating custom Firefox extensions with the Mozilla build system - Archive of obsolete content
ArchiveAdd-onsCreating Custom Firefox Extensions with the Mozilla Build System
topsrcdir = @top_srcdir@ srcdir = @srcdir@ vpath = @srcdir@ include $(depth)/config/autoconf.mk module = myextension xpidl_module = myextension xpi_name = myextension exports = \ myheader.h \ $(null) xpidlsrcs = \ myifirstcomponent.idl \ myisecondcomponent.idl \ $(null) include $(topsrcdir)/config/rules.mk xpidl_module is the name of the generated xpt file that contains type information about your idl interfaces.
... if you have multiple modules, make absolutely sure that you use a different value for xpidl_module for each one.
...you can use the same module in both base/ and advanced/ so that all the generated include files go into the same directory, but make sure that you don't use the same xpidl_module in the two public/ directories or one of the component type libraries (i.e.
Installing headers using EXPORTS
MozillaDeveloper guideBuild InstructionsInstalling headers using EXPORTs
for xpidl-generated headers, you may also set xpidl_module to determine which typelib file is produced from the idl files.
... the distinction between xpidl_module and module is that each directory with idl files must have a unique typelib file, but several directories may export headers to the same location.
... here is an example <tt>makefile.in</tt> which has both c++ and idl headers: module = content xpidl_module = content_base exports = \ nsicontent.h \ nsidocument.h \ nsistylesheet.h \ $(null) xpidlsrcs = \ nsicontentpolicy.idl \ nsiselectioncontroller.idl \ $(null) include $(topsrcdir)/config/rules.mk ...
Makefile - variables
MozillaDeveloper guideBuild InstructionsHow Mozilla s build system worksMakefile - variables
xpidl_module module name to use when generating .xpt files, default to module.
How to build an XPCOM component in JavaScript
MozillaTechXPCOMGuideBuilding components in JavaScript
depth = @depth@ topsrcdir = @top_srcdir@ srcdir = @srcdir@ vpath = @srcdir@ include $(depth)/config/autoconf.mk # module specifies where header files from this makefile are installed # use dom if your component implements a dom api module = dom # name of the typelib xpidl_module = dom_apps # set to 1 if the module should be part of the gecko runtime common to all applications gre_module = 1 # the idl sources xpidlsrcs = \ helloworld.idl \ $(null) include $(topsrcdir)/config/rules.mk xpidl_flags += \ -i$(topsrcdir)/dom/interfaces/base \ -i$(topsrcdir)/dom/interfaces/events \ $(null) creating the component using xpcomutils in firefox 3 and later you can use imp...