: K-Meleon Forum
K-Meleon development related discussions.
[quote=guenter] [quote=JamesD] Does someone know what Mozilla product might have the correct componet files to update the KM 1.7.0a code? I have copied six files for the preferences system into 1.7.0 and they seem to work OK. I will need to test more. I see the 1.7.0 version uses 220.127.116.11pre and I was trying to find the latest product which uses a compatible Gecko engine. The plan was to copy the matching componet files into 1.7.0. I tried by getting FF but all the files there are js instead of xpt. Perhaps some version of Seamonkey might be correct?[/quote] e.g. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; [b]rv:18.104.22.168pre[/b]) Gecko K-Meleon/1.7.0 will run :) That GRE is from a Firefox 3.6.12pre. And later ones will probably also run. SeaMonkey and XulRunner builds based on that GRE will also be suitable. Firefox 4 and builds based one the same GRE 2 engine are no go (K-Meleon1.7.exe does not start with current Firefox 4 components. Tested with: Mozilla/5.0 (Windows NT 5.1; rv:2.0b8pre) Gecko/20101023 Firefox/4.0b8pre). [b]How 2:[/b] I always start the procedure with copying K-Meleon.exe over. I only invest more effort when it starts at all. If it started successfully I shut it down and start to copy over: desga2's newest chrome, I delete ./defaults folder and replace it with K-Meleon's defaults folder, I create a profile.ini (to make its profiles old style self contained), I copy over missing folders ./skins, macros & kplugins. Now I start it again and open ErrorConsole. Error Console will complain about errors in components. Now I will delete all *.js files that cause a complaint. Else I delete all ./components/*.s files that Dorian did not use. Mozilla.org usually builds [b]all components[/b] needed to run any XUL application. The number of ./componets/*.xpt of builds can vary because You can join the individual xpt to a big single one (starts faster). That is done by a script and xpt_link.exe after the build. The number of ./components/*.dll can vary because they can be linked into an exe (see the big 7 mb firefox.exe of Firefox 2) or dll (see the big Xul.dll of the firefox-3.6.12pre.en-US.win32 that I mentioned as running K-Meleon 1.7 example). The build params of .mozconfig to build & link ./components/*.dll into a big exe are ac_add_options --disable-shared --enable-static The build params of .mozconfig to build & link ./components/*.dll into a big Xul.dll are ac_add_options --enable-libxul K-Meleon project usually only builds the subset of components that is used by a web browser! The xpt and dll files of this subset are rarely joined. The build params of .mozconfig to build individual ./components/*.dll are ac_add_options --disable-libxul ac_add_options --enable-shared K-Meleon 1.6.and later has AFAIK only a maximum of 3 native files in ./components/ wallet.xpt/dll and jsbridge.xpt.[/quote]
K-Meleon forum is powered by