On 12/20/05, Randy McMurchy <[EMAIL PROTECTED]> wrote: > > This is off by default. MOZ_SVG is not set unless you pass > > --enable-svg. In turn it uses cairo to do the svg unless you > > --enable-svg-renderer=something_else. > > You obviously have done more homework than me. I was going on > the fact that not using --enable-svg and because about:config > shows that the svg.enabled parameter is set to status:true. > > What exactly does that mean then?
Hmm. Well, looking through configure, the only way to set MOZ_SVG is through --enable-svg. Now, a lot of things appear in about:config than don't mean much. Can you actually view svg files? > Furthermore, in order to use --enable-svg we'll need to come up > with: > > 1. What it does. Allows you to view svg graphics in your browser. For a better presentation than I could give, see the Moz website: http://developer.mozilla.org/en/docs/SVG_in_Firefox_1.5 > 2. Why we need it. > 3. What added functionality does it give us. It seems to be a very cool function. SVG is the wave of the future graphics wise, and cairo renders it. I like new features. Here's a really cool presentation (you won't be able to see much if you don't have svg and html:canvas in your browser). Even without seeing the goodies, I think you'll want these features after reading it. http://developer.mozilla.org/presentations/xtech2005/svg-canvas/ > 4. What functionality is lost if you don't have it. You can't view svgs. Although, I could see how not having svg capability and not linking in cairo would give you a smaller browser. I get caught up in all the goodies, though. (In turn, firefox is a hog on my machine. Bring on the new hardware!) <snip> > >>ac_add_options \ > >> --with-default-mozilla-five-home=/usr/lib/firefox-1.5 # > >> MOZILLA_FIVE_HOME <snip> > > Probably not, but it is in /usr/include/firefox-1.5/mozilla-config.h, > > so something else may depend on it on the macro. Needs more research. > > I agree with you that it doesn't affect running firefox. > > How do we do this "research". I'll be happy to, but starting from > scratch on this, I may not be able to find out too much. Perhaps > for now we should just leave it in, but how do we describe it? > What does it do? I wish I new. grep the source for the Mplayer plugin and see if it pull in DEFAULT_MOZILLA_FIVE_HOME. I doubt anything does anymore. I'm pretty sure this is probably historical. Google MOZILLA_FIVE_HOME. I can't decide if it's actually needed or not. I think some applications use the variable, but use the same runtime detection used by Firefox, etc. I don't think they're using the #define DEFAULT_MOZILLA_FIVE_HOME = ... which is the only thing passing the parameter in the Firefox build does. I can't decide. I also googled DEFAULT_MOZILLA_FIVE_HOME and the only hit was the blfs bug :). It's probably worthless since the configure flag doesn't set any environment variables or anything. > >>ac_add_options --enable-xinerama # dual display support <snip> > I will certainly take your word on this. I was mistaken. I thought > again it was something that about:config said was enable, but as I > said, I was mistaken. No biggie. I think about:config may be a red herring. If you want to see what's built in your browser, look through /usr/include/firefox-1.5/mozilla-config.h. > Should it be enabled by default, or turned off with a comment to > unremark it from .mozconfig if you want it? Beats the hell out of me. I don't have two monitors. I had to google xinerama just to see what it was. > Thanks for the input, Dan. No problem. This is probably the one package that I can speak with any authority on. I used to build it unprivelaged on a poorly administered Solaris box. I had to get to know the build system pretty well since there were a lot of gotchas. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
