Do you mean GRE(Gecko Runtime Engine) or XULRunner?
Replacing XUL binaries would not help if K-Meleon
sources don't use certain functions.
Who compiled 1.6b2 XULRunner 220.127.116.11pre binaries?
I don't know where to get that version.
Someone with full sources should run it in
debug mode and set a breakpoint
to "PRBool is_targetable = is_primary ||"
in nsFrameLoader.cpp to see if/when it is called.
GRE = Gecko Runtime Engine, naturally. Yes, even I know that Mozill.org propagates Xulrunner for applications using their GREs' now. But K-Meleon project is much older than that.
No idea what should be done since I am no developer/programmer.
Currently I do not know where to get any specific GRE version but from the Mozilla servers. Especially I do not know where to get any builds with shared libraries instead of a big lib xul or a static exe.
The 1.6.bet2 GRE binaries/dll are based on Suite not Xulruner.
I assume Dorian has built the GRE18.104.22.168pre
but I do not know.
To me it seems open which GRE will be the base in the future?
desga2 was so kind to elaborate so I could understand Your post about xul.dll
If the problem is really the xul.dll file the problem should not happen in 1.7a2 because this use xul.dll from Firefox 3.6.13 and this include the strings (hexadecimal viewer search):
c o n t e n t -
(also includes in Firefox 3.5.13 xul.dll file)
xul.dll file from Seamonkey 2.0.11 (1.6 Beta2) not include this strings.
p.s. K-Meleon is based on mfcembed which was elementary browser-only subset of a GRE based on suite. It was fully support till GRE 1.7. Until GRE 1.9.1.x it was more or less supported and the sources shipped the source to build mfcembed.exe (the ancestor of all current K-Meleon.exe - since version 0.3).
Mozilla 1.92.x sources do not ship MFCembed but only winembed.exe and sources for it now (the ancestor of K-Meleon 0.1 - 0.2).
Xukrunner is a all inclusive package - it can e.g. also support a mail client.
That is a waste of resources for a small browser app like K-Meleon.
Part of his frugal use of resources comes from using only browser components.
But probably Xulrunner.dlls and toolkit.jar is the way to go with current and future ample PC resources and the scarce dev man-hours that this project can muster.
I did/do not build any K-Meleon.exe or dll. From what I read in older Forum posts You can build the debug version from what is in CVS about K-Meleon 1.6.
To build You'd need VC8 - according to Dorian.
(Ich persönlich denke, dass VC Express 2005 und Microsoft Platform SDK for Windows Server 2003 R2 reichen könnten. / Beides gibt es noch umsonst im Netz, wenn man gut googelt.)
Sometimes I have build a GRE for updating.
Which meant that I was able to build custom GREs too.
Currently I have problems to build any GREs.
Build stops with
# error C2039...
I googled the problem to.
which points to
which points to other pages like.
No idea what stops it.
I use only: Mozilla sources and Build environment (usually version 1.3) & Microsoft Platform SDK for Windows Server 2003 R2
Edited 1 time(s). Last edit at 02/15/2011 03:06AM by guenter.