Did you complete both steps to build Mozilla, both the full installation
and the embedded version? That should build the necessary files in the
Embed directory so that when you build the K-Meleon files, everything
should run. I haven't reviewed the latest build instructions so I'm not
sure if all that is covered. Also, I know that when I've built the source
from the nightly Mozilla source, I can't get the PSM files to build
properly. What I do is download the nightly MFCEmbed build and use the
necessary files from that to handle the security components.
You should coordinate with Jeff about updates to the rest of the code. As
you've discovered, when you use the nightly sources, you have to update
some of the code to match the changes the Mozilla people have made.
Otherwise, you'll throw errors in xpcom.dll. One issue to be aware of is
that Jeff has made changes to fix problems that the Mozilla people were
slow to or have not changed. I know Jeff had the problems with Print
Preview and Page Setup fixed before it was fixed in the Mozilla code. You
probably don't want to step on each others toes.
On Tue, 21 May 2002, Mark Liffiton wrote:
> So I fought with Mozilla and built it (a single build takes about 3 hours
> on my poor little laptop... and I messed up and had to restart a lot...),
> then I fought with KM (much less) and built it. So I have a shiny new
> k-meleon.exe... what do I do with it?
> The build instructions said to copy some files into the win32_o.obj\bin
> directory. Well, that's nice, but k-meleon is in win32_o.obj\embed and
> can't see things it needs like xpcom.dll anyway...?
> I got a bastardized version running by copying over files from the \bin
> directory and my 0.65 directory until it worked, but it's pretty sketchy.
> At one point I even had a download dialog, but only because it was
> displaying Mozilla's download manager (some .xul thing) in a KM window -
> slightly odd.
> So how do I *properly* form an entire KM install?
> One more thing: I had to change a few things to get it to compile with
> the latest nightly Mozilla source (they had changed some things in the
> past few days since Jeff checked in some fixes, apparently). Should I
> check those in? If I make improvements or fix bugs in the main source, is
> it okay for me to check them in? Now that I'm loose in the main code
> (nothing can stop me, not even repeated 3 hour builds!), I'm reluctant to
> change things. When I was just playing in the bookmarks plugin, I
> basically had the playground to myself, but now I have to worry about
> breaking other people's toys...
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> Kmeleon-dev mailing list