Search completed in 1.63 seconds.
6 results for "XPCOM_Glue":
XPCOM glue
MozillaTechXPCOMGlue
embedding code which wishes to use only frozen symbols and cannot tolerate a load-time dependency on xpcom.dll should #define xpcom_glue 1 while compiling, and link against xpcomglue.lib.
...as described in bug 299664, the preprocessor symbol xpcom_glue_use_nspr needs to be defined.
... linking strategy: dependent glue standalone glue compiler flags: cross-platform #include "xpcom-config.h" #include "xpcom-config.h" #define xpcom_glue windows /fi "xpcom-config.h" linux -include "xpcom-config.h" linker flags: windows for older versions of the firefox sdk: -libpath:c:/path/to/sdk/lib xpcomglue_s.lib xpcom.lib nspr4.lib for recent versions of the firefox sdk (at least version 42, but possibly earlier versions as well): -libpath:c/path/to/sdk/lib xpcomglue_s.lib xul.
2006-09-30 - Archive of obsolete content
ArchiveNewsgroup summariesmozilla-dev-tech-xpcom2006-09-30
summary: mozilla.dev.tech.xpcom - sept 30- oct 5, 2006 announcements build a xpcom component on mac os x benjamin smedberg confirmed that this tutorial http://www.iosart.com/firefox/xpcom/ is misleading as it uses the standalone glue (-dxpcom_glue) for components, which is not recommended.
... developers should use this sample instead: http://developer.mozilla.org/en/docs/xpcom_glue discussions dynamic load overlay a short discussion about the possibilities of loading and unloading xul overlay runtime reading binary data from file discusses about the code to read binary data from file how to build xpcom component on mac os x discusses about the make file code used to build xpcom components on mac os x successfully meetings none during this week.
How to build a binary XPCOM component using Visual Studio
MozillaTechXPCOMHow to build a binary XPCOM component using Visual Studio
b" to additional library directories add "nspr4.lib xpcom.lib xpcomglue_s.lib" to additional dependencies add "xp_win;xp_win32″ to preprocessor definitions turn off precompiled headers (just to keep it simple) use a custom build step for the xpcom idl file (spawns xpidl-build.bat to process the idl with mozilla toolset, not midl) vc++ express project: xpcom-test.zip note: the project uses xpcom_glue.
...i am not defining xpcom_glue and i am linking against xpcomglue_s.lib create an xpcom component a full tutorial of xpcom is beyond the scope of this posting.
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 is_component = 1 module = myextension library_name = myadvanced use_static_libs = 1 xpi_name = myextension defines += xpcom_glue shared_library_libs = \ $(dist)/lib/$(lib_prefix)myintricate_s.$(lib_suffix) \ $(dist)/lib/$(lib_prefix)mymultifarious_s.$(lib_suffix) \ $(dist)/lib/$(lib_prefix)xpcomglue_s.$(lib_suffix) \ $(dist)/lib/$(lib_prefix)xul.$(lib_suffix) \ $(dist)/lib/$(lib_prefix)nss3.$(lib_suffix) \ $(null) cppsrcs = \ advanced.cpp \ $(null) include $(topsrcdir)/config/rules.mk local_includes += ...
GRE - Archive of obsolete content
ArchiveMozillaGRE
to use the xpcom glue, you must follow these steps: compile your code with xpcom_glue defined.
Setting up the Gecko SDK
MozillaTechXPCOMGuideCreating componentsSetting up the Gecko SDK
this window is where you add the include paths to the gecko sdk as well as two preprocessor defines: xpcom_glue mozilla_strict_api at a minimum, you must include the nspr, the embedstring and string include directories, and the xpcom include subdirectory.