Only Dorian or Hao will know or have.
It is not finished completly, else it would have been published.
I just try to learn more about making a K-Meleon.
Quote
lian
I downloaded the files most unfortunately I could not build. Used the visual studio 2003 for this
?
I tried to get through the build process with current version first.
Dorian's: K-MeleonBE1.5 download.
Quote
Dorian
Release MFC Static and Release MFC Static Unicode are used
for the official build but need a custom build of MFC.
Release and Release Unicode should work right away, but the
build will require mfc71.dll (or mfc71u.dll for unicode)
The later built for me with Net VC 2003 Standard (English Edition) out of the box.
That is for GRE version 1.8. So I know my buildsetup for Net 2003 is ok.
No idea what can be done for the first two.
No idea what to prepare additionally to compile for 1.9 GRE?
I assume:
You have to compile the GRE 1.9 with the same compiler You want to use to get the 1.9 SDK.
I can build the GRE 1.8 and 1.9 with VC 7.1 Toolkit & Net Standard 2003.
I can also build GRE 1.8 and 1.9 with VC 8 Express.
And GRe 1.9 but not GRE 1.8 I can build with VC 8 Standard .
Now what is next?
To make fast GRE 1.9 with jemalloc You need commercial VC 2005 aka VC 8 Standard or whatever. I have been through that also. VC 2005 Express did not do the fast GRE 1.9 / only a slower version that is not interesting, I probably do not know enough to build that with free toolz
The 1.9 GREs are always slower when I build with any VC7.1 optimizing compilers.
I know that You can build K-Meleon with one compiler and the GRE with another.
The final product will work together.
Both VC 8 Standard & Express and VC 9 Express will build K-Meleon.exe but only the debug versions.
The release versions fail because they error LNK2005: ___@@_PchSym_@00@UpRnvovlmRyfrowUpRnvovlmyvBOFPexJUhixUivovzhvUhgwzucOlyq@ ist bereits in PrintSetupDialog.obj definiert.
..\release\k-meleon.exe : fatal error LNK1169: Mindestens ein mehrfach definiertes Symbol gefunden.
The German reads: that this Symbol Name has been passed out and defined twice.
Now my question is how too get past it.
Edit by hand? No idea.
So before I do not know what to do I cannot even try to move to build for 1.9.
p.s. This is not a mere shift to a different GRE but the shift to another Toolkit with other code - IMHO this is not a normal College Assignment but requires several months of coding. Guess Dorian can say how much coding.
I already know from chrome making that the old certificates handling is broken.
I know that much of the .mozconfig must be altered to get the 1.9 SDK.
The changes make me think that more is broken.
p.s.
Fred pointed You to the thread where Dorian posted his .mozconfig for 1.8.
I attached my mozconfig that You can use to build SDK for 1.9.
You will notice from my mozconfig that not all old 1.8 targets have been build.
Changes were needed to build.
When You later try to build the K-Meleon exe - you may get errors (You did not post the version of Your uses files) in StdAfx.h (nsIDocShell.h, nsICacheService.h, nsIPref.h, nsIWebProgressListener2.h, nsIWalletService.h, nsIContextMenuListener2.h, nsIEmbeddingSiteWindow2.h, nsCWebBrowser.h, nsIWebBrowserPersist.h, imgIContainer.h, nsAppDirectoryServiceDefs.h, nsNetCID.h)
nsNetCID.h)
and PrintSetupDialog.cpp (nsIPrintSettings.h)
On the long run You probably need to find their new name or location.
For a short try whether it compiles You can comment out.
I stopped at printsetup.
An oddity - For GRE 1.9 builds additional lib files from Microsoft Platform SDK for Windows Server 2003 R2 were needed/used. It looked like it anyway.
Uuid.lib
advapi32.lib
wsock32.lib
winmm.lib
user32.lib
gdi32.lib
shell32.lib
ole32.lib
version.lib
usp10.lib
olepro32.lib
oleaut32.lib
msimg32.lib
comctl32.lib
winspool.lib
comdlg32.lib
imm32.lib
rpcns4.lib
urlmon.lib
Maybe also header files?
Edited 4 time(s). Last edit at 12/25/2009 08:28PM by guenter.