On 2/3/10 4:04 PM, Timothy Madden wrote: Follow up to mozilla.dev.embedding please.
On this mozilla.org page http://www.mozilla.org/projects/embedding/embedapiref/embedapi2.html#1099700 about Embedding Initialization I think the documentation for NS_InitEmbedding should say the first parameter aMozBinDirectory should be "nsnull to indicate the *main executable* directory" instead of "nsnull to indicate the *working* directory".
Yeah, we've had problems in the past where we have a confusing "XPCOM working directory" parameter which has nothing to do with the OS working directory. The executable directory is clearer. Although, I strongly suggest always passing a value for this item and never passing null.
I think the documentation should also say that if user wants to have the entire xulrunner SDK in a different directory, including xpcom.dll and nspr4.dll for the XPCOM architecture, then user should, at least with Visual Studio, also use delayed loading of imports for these libraries and provide a delayed loading hook function as described in MSDN to load this libraries from the given directory with LoadLibraryEx and the ALTERED_SEARCH_PATH flag.
This is not the best/good way to do this. Instead, use the standalone XPCOM glue and XPCOMGlueStartup(), which a cross-platform method of dynamically loading the platform from an arbitrary directory without linking against it directly.
--BDS _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
