well :) > I can certainly do that, however it's frustrating there's not an > easier/more straight-forward way of knowing what will be built if I > don't have anything in my .mozconfig file
I had have some problems with understanding how it works too but I'm not a Mozilla developer and have no associations with their team (yet). Probably you'd address this to someone else. To me it looks like you can never have an empty .mozconfig, It should have at least . $topsrcdir/browser/config/mozconfig if you're building browser. and probably ac_add_options --enable-crypto if you need SSL (by default it's off). > Well, perhaps I'm misunderstanding how profile management is supposed > to work, but for my application (the software for LEGO Mindstorms > NXT, actually) we have multiple user profiles and they can log into > secure web sites. What do you mean under "user profiles"? A server context? Such as data associated with username/password they logged in with? > I want to keep the cookies separate so that users > can't access others' secure pages. The profile switch can happen in > the application without shutting down and restarting. I suppose I > can just have one profile and make it kill the cookies/session when > the user switch occurs, but I'd rather be able to persist the browser I'm not sure if your task or your targets have any relation to the browser at all. I'm sure that security should be based on something people have no direct access to or in other words can't modify. Suppose you add an extension and provide them with your very own browser that will behaves differently and protects them from accessing some of the server pages. What if user just remove your extension and/or install a standard browser? To me it looks like you have to put all your efforts to the server side and establish your own server rules with either a server extension or backend application. -dmitry > >> Does this mean that single-profile is enabled by default? > > > > It depends on what you're building. > > Firefox browser? > > > > >> (This is one thing I wish the build configurator did better - > >> made it clear > >> what the defaults are). > > > > Check mozilla/config/autoconf.mk > > I can certainly do that, however it's frustrating there's not an > easier/more straight-forward way of knowing what will be built if I > don't have anything in my .mozconfig file > > >> > >> 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? > > Well, perhaps I'm misunderstanding how profile management is supposed > to work, but for my application (the software for LEGO Mindstorms > NXT, actually) we have multiple user profiles and they can log into > secure web sites. I want to keep the cookies separate so that users > can't access others' secure pages. The profile switch can happen in > the application without shutting down and restarting. I suppose I > can just have one profile and make it kill the cookies/session when > the user switch occurs, but I'd rather be able to persist the browser > state when they switch between users so that they're still logged in > when they switch back. This doesn't seem unreasonable to me, but > perhaps I'm missing something??? > > J > > > _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
