How do I not build Venkman?
Venkman is built in two parts. • The platform specific XPCOM component, compiled, is about 75k. It is referred to as the jsd library, and is required if you ever want to install one of the XPIs from the Development Page. Other than a small amount of disk space, there is no overhead in including this library in your distribution, it lies dormant until Venkman (or some other component) makes use of it. If you maintain a port of Mozilla for others, and those users may want to install Venkman at some later point, you should not exclude the jsd library. If the build is just for you, and you never want to install Venkman, then add –disable-jsd to your configure options. • The cross platform front end, compressed into a .jar file, is about 240k. This is Venkman proper, and is what is included in the XPIs distributed from the Development Page. You can exclude this from your custom build and still be able to install Venkman at a later date via XPI.
Venkman is built in two parts. • The platform specific XPCOM component, compiled, is about 75k. It is referred to as the jsd library, and is required if you ever want to install one of the XPIs from the Development Page. Other than a small amount of disk space, there is no overhead in including this library in your distribution, it lies dormant until Venkman (or some other component) makes use of it. If you maintain a port of Mozilla for others, and those users may want to install Venkman at some later point, you should not exclude the jsd library. If the build is just for you, and you never want to install Venkman, then add –disable-jsd to your configure options. • The cross platform front end, compressed into a .jar file, is about 240k. This is Venkman proper, and is what is included in the XPIs distributed from the Development Page. You can exclude this from your custom build and still be able to install Venkman at a later date via XPI. If you want to disable the this, add –enable
