That sucks. I'm still learning how the whole profile mess and how it is setup in everything (unfortunately its not very well documented on how it works in the entire scope of things so I'm learning from every example I can get my hands on from context and making some weird assumptions, so forgive me as I might be way off here). Do think there is anyway I can avoid it to still embed gecko? Maybe even just go right to nsIProfile instead, and possibly provide my own profile?
I have requirement that I cannot statically link anything unless its included in the devel packages included by most distros. Discussion of even using khtml in my group (which would suck because many of our guys are the founders of gnome :-P) has even come up if its not possible. I might (and I stress might) be able to use a hack that even uses gtkmozembed to bootstrap the start up process, and then provide something that statically links things in the Win32 builds (as we only really like to distribute binaries for Win32 and we don't want it be a requirement to have to build mozilla to build the source versions of our libraries as many of the packagers wouldn't not even bother with it at that point). I'm also debating, because this is to going to fill a gap in code that mostly likely won't be in mainstream use for a good few months, so it might be ok to start working against xulrunner. Zac Bowling On Mon, 2006-05-29 at 11:17 -0400, Benjamin Smedberg wrote: > Zac Bowling wrote: > > > One part I'm trying to get around is the the ProfileDirServiceProvider. > > I can't find any documentation on it, but its not exposed in FF > > 1.8/XulRunner/Seamonkey so i'm guessing its inlined in embedded > > projects. Does anyone have any info/documentation on that service, or if > > it is automatically by anything that I could call or some other way to > > start it up and use it. > > The profiledirserviceprovider is, in current stable embedding situations, a > statically linked component (depending on your linkage, you will need to > link either libprofdirserviceprovider_s.a or libprofdirserviceprovidersa_s.a). > > On trunk xulrunner, there is a new profile-management API which will replace > the old profdirserviceprovider. (see nsXULAppAPI.h). It prevents the need > for unpleasant static linking and is relatively freezable. > > --BDS -- Zac Bowling <[EMAIL PROTECTED]> _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
