> Does this mean that single-profile is enabled by default? It depends on what you're building.
> (This is one thing I wish the build configurator did better - made it clear > what the defaults are). Check mozilla/config/autoconf.mk > > Also, are you saying that with this disabled, there will be a static > library I should link against? Or will it produce a dynamic library > that ends up in the components folder? (I believe this was what > happened in Mozilla 1.7.5) I think that neither are compiled while MOZ_SINGLE_PROFILE is 1 (in case of 1.8.0.x). But, I'm not sure if NS_PROFILE_CONTRACTID (profile manager) is needed at all. Firefox can live without it and why can't your application live? -dmitry. > > J > > On Aug 30, 2006, at 7:46 AM, Dmitry Dartz wrote: > > > NS_ERROR_FACTORY_NOT_REGISTERED is returned because no factory > > linked/registered for NS_PROFILE_CONTRACTID. > > Check mozilla/profile/build/nsProfileFactory.cpp, it's where the > > factory gets defined and this cpp is compiled only when > > MOZ_SINGLE_PROFILE is NOT defined. > > See the lines below in the makefile.in in mozilla/profile > > ifndef MOZ_SINGLE_PROFILE > > DIRS += src build resources defaults pref-migrator > > endif > > So, as far as I see you would need to specify that you're using > > multiple profiles, make sure that profile library is compiled and > > link against it :) > > > > -dmtry > _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
