r3dfox, a modern Firefox based web browser for Windows Vista, 7, and 8!

[K4sum1]

On 3/8/2026 at 10:08 PM, user57 said:

that one ?

https://releases.rs/docs/1.52.0/

it names LLVM v12 i made v17.0.1.0

https://msfn.org/board/topic/183588-project-saphire-dragon-port-llvm-and-clang/

i need a bit more information about greyrat´s answer

in the forum he links is like old LLVM versions from 2015 (the oldest version on LLVM github is LLVM 7.1.0 and is from 2019)

and writes something about a LLVM driver - i do not understand that part - it might be a missunderstanding

LLVM is a compiler that generates a code, its not a software driver 

if a function is called and returned not possible or something it might be an different problem 

 

 

LLVM is newer then VS 2019 (v16.11) (LLVM v17 is from Sep 19, 2023) and allows more modern c++ styles then vs2019 

Cool, but this is missing a lot of tools like lld-link.exe making it unusable for r3dfox.

If I was to aim for XP, LLVM v9 has worked up to v91, but I get a ton of warns and had to do a few code changes to make it compile. I'd need to upgrade the compiler to go much further than that.

[user57]

how many exactly to relation to redfox is missing ?

the project had like 150 small projects 

that being said a few might not be problem to add

the 150 where made by the cmake project file maker (standart settings) - i saw are few where left out, so hard to say

still the questioning regarding that linker problem would rather be to edit the .obj file trick 

it would be a read through where exactly the compiler has that problem (i certainly can rewrite that code)

so one actually could also compile it on a win10/11 machine too and just have the modifications

 

you made a huge jump from v128 to v146 ? seems something has happend here

how the the xp version going ?

 

[K4sum1]

@feodor2Can you 7z up and send me your C:\DEV folder similar to how I've done this with VS2019? https://archive.org/details/funny-windows-development-kit

I can't use my FWDK itself with Mypal68 as it complains about some error that I've forgotten. So I went to use EWDK, but you seem to have modified EWDK as using the ISO you linked and unpacking it into the folder results in it complaining about the Win 10 SDK being too old. I've used MSVC14 folder from EWDK and Windows Kits folder from FWDK to compile and that's worked fine from Firefox 68+, however using it to build latest Mypal68 gives me these errors.

16 hours ago, user57 said:

how many exactly to relation to redfox is missing ?

Not sure tbh, Mypal68 uses the LLVM 9 that you can download and that could be used for reference. For 68, on top of that you need a llvm-config.exe, which you can get from compiling Rust. For 78 and later, llvm-dlltool.exe is also required to be added.

Also the listed minimum Clang up to 140 at least is still 9, so maybe I will just continue on and fix what comes. 102 was actually kinda painless, and 115 hasn't been too bad so far. 91 made me think it would be horrible because I had to bisect a bunch.

16 hours ago, user57 said:

you made a huge jump from v128 to v146 ? seems something has happend here

No? I've just been working on it over the months and years. I started at 122, and basically have had a release for every major version.

16 hours ago, user57 said:

how the the xp version going ?

idk if it's possible, I think it will be a lot and very hard going by Mypal68 changes on top of extrapolating to like 140 or so if I were to try it. A lot of the reason I wanted to try this was to have a build system to build older releases that can no longer be bootstrapped. With this, I was able to build 91, and disable WebRender and have Cairo on a (relatively) recent version. https://github.com/Eclipse-Community/r3dfox/issues/32#issuecomment-4262918711

[user57]

you have that lock functions, i gave the xp ones to you - there are some around

a few around are disfunctional, other have specifical bugged, while others only part work (like cant handle 4 jobs in 4 cores)

if you could undef them from global namespace thats actually a good thing - then it can search the XP or maybe the vista ones

the problem with this is that they not only apear in this part of code 

then you might code around a lot but still end to the .obj trick

the .obj trick i described here:

https://msfn.org/board/topic/182888-how-vs-makes-working-code-still-incompatible/#comment-1203133

long story short - it has a static .obj file hidden somewhere (and skip reading the code)

thus it cant be edited, scoped - for that part of code you shown - that might work - but not with the .obj file part question

 

what is a .obj file

in a compiler the compiler reads out the code and generate .obj files (these are then linked together)

in this case the .obj file have been pre-compiled - and the vs2019 compiler then only links against "their .obj file" 

so that should be this trick explained

so very likely if you use that rewrite method - you end up in this one

this has nothing to do with rust or whatsoever 

[K4sum1]

On 4/15/2026 at 10:54 AM, K4sum1 said:

Also if you could, it would be nice to have the 1.45 patch (you only ever released 1.35 and 1.52), and a fixed 1.52 patch in case I want to build and test an older release.

On 4/15/2026 at 12:27 PM, feodor2 said:

About 1.52 likely not going to fix because it totally unnecessary now, what was built with 1.52 will do same with 1.62, of course you easy can fix youself if so really want.

I found you released the proper 1.45 patch under an issue, so you linked to the 1.35 patch until you replaced it. Also the patch linked for 1.52 only applies cleanly to 1.56. Were you considering 1.56 at some point? I ported the 1.56 patch to apply to 1.52, but I do wish I could get a clean 1.52 patch in case something's missing or I did anything wrong.

[K4sum1]

39 minutes ago, K4sum1 said:

I ported the 1.56 patch to apply to 1.52, but I do wish I could get a clean 1.52 patch in case something's missing or I did anything wrong.

[feodor2]

1 hour ago, K4sum1 said:

I found you released the proper 1.45 patch under an issue, so you linked to the 1.35 patch until you replaced it. Also the patch linked for 1.52 only applies cleanly to 1.56. Were you considering 1.56 at some point? I ported the 1.56 patch to apply to 1.52, but I do wish I could get a clean 1.52 patch in case something's missing or I did anything wrong.

I do not remember, whatever, already told that 1.52 or 1.56 no matter is now obsolete and not needed.

 

On 4/17/2026 at 1:28 AM, K4sum1 said:

I can't use my FWDK itself with Mypal68 as it complains about some error that I've forgotten.

Did you fix this for now? I remember have put there mozwrlbase.h on intent. Also I dropped win10 sdk for a time, now I use win8 sdk, but it must work with default ewdks win10 sdk too. I shall look an fix.

[K4sum1]

11 minutes ago, feodor2 said:

I do not remember, whatever, already told that 1.52 or 1.56 no matter is now obsolete and not needed.

I would like it for my own use, in case I need it. I made this fix for it based off of the changes comparing your 1.62.1 and 1.45 patches, and it compiled, but I haven't tested it yet. https://github.com/Eclipse-Community/eRust/commit/619ed0e48e3e0a6602727dd58918a7783c2d422c

11 minutes ago, feodor2 said:

Did you fix this for now? I remember have put there mozwrlbase.h on intent. Also I dropped win10 sdk for a time, now I use win8 sdk, but it must work with default ewdks win10 sdk too. I shall look an fix.

I haven't tried building Mypal68 in a few days, mostly just been managing and juggling commits and building rust 20 times. I don't know what to use or where to get it, so I've just been waiting to see if you could share your tools.

Edited April 20 by K4sum1

[feodor2]

Okey I have fixed

So old EWDK not suitable because of the buggy wrl stuff inside its sdk.

I shall examine this further, I restored wrl to make angle work at least on win7, to try drop it again and fix for xp too, but when, this is so unimportant.

For now go to EWDK_rs5_release_svc_prod2_17763_190129-1747 and apply the patch

Also if you do not want go for newer EWDK you poke its wrl stuff and build anyway, not worth a time I think. Newer EWDK is huge yes, while you need the same amount as older and other throw out.

 

 

win10sdk.patch

[Guest Gregg]

For some reason, the latest version, r3d 151.02/64, has a Menu Bar that sits tightly on the Titlebar. There is no way to take it down under the Titlebar as it should be, even using Chrome.css. The 150.01 version has no such issue. Here is a screenshot from a freshly downloaded 151.02/64 browser immediately after unpacking:

Any ideas how to fix it? Thanks.

 

[NotHereToPlayGames]

Your screencap "looks like" XP.  So I tried to run r3d in XP and it doesn't work.  Is that XP?  Or something "made to look" like XP?

[Guest Gregg]

6 minutes ago, NotHereToPlayGames said:

Your screencap "looks like" XP.  So I tried to run r3d in XP and it doesn't work.  Is that XP?  Or something "made to look" like XP?

Sorry, forget to mention - Win7 SP3 with Luna XP Theme.

[NotHereToPlayGames]

I only tried in XP (failed) and 11.

In 11, when you right-click to customize, the "Title Bar" checkbox seems to do absolutely nothing.

Unsure if it did anything in previous versions.

 

edit:  just checked in previous versions and this checkbox DOES work in previous versions

Unsure if that is related to your issue or not, the Menu Bar looks the same to me in both versions.

Are you having this issue ONLY when using your Luna XP Theme inside of Win7 ???

Edited yesterday at 06:24 PM by NotHereToPlayGames

[Guest Gregg]

19 minutes ago, NotHereToPlayGames said:

Are you having this issue ONLY when using your Luna XP Theme inside of Win7 ???

The following is my current  r3d v.150.01 on the same computer with FFox Chrome classic theme:

And r3d 151.02 with the same Crome folder in the Profile:

That is a problem: wrong place for Menu Bar. 

[NotHereToPlayGames]

That (to me) DEFINITELY is tied to the "Title Bar" checkbox doing NOTHING in r3d 151.02.

It's as if the "Title Bar" HEIGHT is set to ZERO or something to that effect.

It appears CSS-related to me.