Jeff Doozan wrote:
>>Haven't gotten around to all that yet. I'll see if I can arrange the
>>compiler this week. But wouldn't it be a good idea to package the things
>>you need to the compile K-Meleon executable? Like header files and
>>libraries I mean. It would cut the barrier down for those that only want
>>to play around with k-meleon itself.
>It would be great to be able to do that. Unfortunatelf, there is
>about 1Gb of headers and libraries produced from building mozilla and
>they're pretty much all required for building K-Meleon. It's much
>easier to says, grab the mozilla source and compile it rather
I got an msdev running, so that's a start. I took a look at the project
files, but it would seem that you need the necessary headers from the
mozilla/dist directory and the four import libraries xpcom.lib,
baseembed_s.lib, nspr4.lib, plc4_s.lib and of course a release of
k-meleon based on the same version of mozilla. That's not 1GB together,
It maybe worth an attempt to see if it works. Otherwise I need to build
Mozilla. What version do I need to compile with the current K-Meleon cvs
>>While I get my build system sorted, I'll put some thoughts on paper on
>>where I'd like to start my efforts.
>Sounds like a good plan. It's a very big project so there should be
>plenty of things that you'll be able to enjoy working on.
If nobody is doing it, I'll try to look into the toolbar/menu/skinning
code and see if something can be done for the configuration. Add a
simple gui to edit the configuration so editting of config files is no
longer needed. But also rework it a bit to see if the conflict between
user changes and new releases can be simplified.