On 7/11/07, Peter B. Steiger <[EMAIL PROTECTED]> wrote: > I'd trade all the clever acronymns and extended metaphors in the world > for a project name that actually says what it does. Would it kill > people to give their project a meaningful name? > > I thought I'd try out the HTML editor with Firefox this time around, so > in the .mozconfig file I included the option to build the composer. The > build crashed saying it could not find the Makefile > for /mozilla/composer. Sure enough, that directory is almost completely > empty.
Sorry, you can't do that. The standalone composer is NVU. http://www.nvu.com/index.php It seems like it's in a state of flux, though. The lead developer has stopped development of nvu and is writing something new from scratch that's only in cvs, I think. http://glazman.org/weblog/dotclear/index.php?Nvu But, there's a fork of the old nvu codebase here: http://kompozer.net/ > So I went over to mozilla.org to find the composer module to build with > Firefox. There is no such thing, just a bunch of cute animal names. Do > I want Thunderbird? No, any fool can see that Thunderbird means "mail". > What about Sunbird? Of course, it's a calendar. Or perhaps > "Seamonkey"? Yes, it includes an HTML editor... as well as a browser, > email client, calendar, news client, flux capacitor... no way to have > JUST the composer. Wikipedia set me straight. > And what if I do decide to build Thunderbird? Can that go in the same > source tree with Firefox and get built at the same time, or is it better > to build them separately? Separate. Well, if you want to checkout from CVS, you can switch between tag names, but in the end I think it's easier to just keep the source trees separate. The good news is that with Gecko-1.9 (will be the base for firefox 3), you will be able to build the backend standalone as xulrunner. So, then you would just have to build the frontend for firefox/thunderbird/sunbird/whatever. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
