Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
52 user(s) are online (37 user(s) are browsing Forums)

Members: 1
Guests: 51

sailor, more...

Support us!

Headlines

 
  Register To Post  

« 1 2 (3)
Re: Anyone Tried Compiling the latest WebKit?
Home away from home
Home away from home


See User information
@rjd324

If gcc11.3 is the latest release then yes, using it since some time now with scummvm (newlib here though)

Go to top
Re: Anyone Tried Compiling the latest WebKit?
Home away from home
Home away from home


See User information
@walkero

Quote:
If you guys are interested, I could create a GCC version for AmigaOS 4 working with that clib2. But that won't happen yet, because afxgroup is on vacation and unavailable to provide some necessary changes for using shared objects. As soon as he is back, I can do those changes.

A docker container that's ready to go with his clib2 would be useful.

Ideally, we'd be able to build WebKit with a standard AmigaOS SDK, but I don't see that happening any time soon. My attempt to get the C stdlibs expanded fell flat last time.

Hans

Join Kea Campus' Amiga Corner and support Amiga content creation
https://keasigmadelta.com/ - see more of my work
Go to top
Re: Anyone Tried Compiling the latest WebKit?
Site Builder
Site Builder


See User information
@Hans
I am working to create those docker images for cross-compiling and GCC 8 for native development so anyone can use them.

I believe I will have something ready next week.

Follow me on
Ko-fi, Twitter, YouTube, Twitch
Go to top
Re: Anyone Tried Compiling the latest WebKit?
Home away from home
Home away from home


See User information
@walkero
Gcc 8 outdated already, and the more time passed the less hope recent webkit will be able to dealt with.

And, with gcc8 you will have even errors and warnings when will try Andreas's clib2. Some weeks ago i annoy Andrea to fix things so it will be gcc8 bug-free, but testing yesterday and its again throw those errors in new places, so complete switch to recent gcc is must. You can forget gcc8 long ago as we told in betalist :)


@Hans
Standart sdk in our case mean the same adtools on which the same devs on. I mean Andrea's clib2 is the same standard sdk, just not included in Hyperion's archive. But quality of the original clib2 and his are the same, both have issues and bugs with which devs live, just Andreas one actively works on, which is what we need when some massive work tobe done

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Anyone Tried Compiling the latest WebKit?
Amigans Defender
Amigans Defender


See User information
From Saturday I'll be back if you need help

i'm really tired...
Go to top
Re: Anyone Tried Compiling the latest WebKit?
Site Builder
Site Builder


See User information
@kas1e
I chose gcc 8 so to work only on one of them, but if you suggest going with GCC 11, will go with that. Thanks for your suggestion.

@afxgroup
Take your time, and have fun... And I will need your help for sure.


Edited by walkero on 2022/9/14 10:55:58
Follow me on
Ko-fi, Twitter, YouTube, Twitch
Go to top
Re: Anyone Tried Compiling the latest WebKit?
Just popping in
Just popping in


See User information
Could that be any option...?

https://awesomekling.github.io/Ladybir ... platform-browser-project/

If I correctly understand it, it is all written in C...?!


Edited by Primax on 2022/9/14 7:20:42
AmigaOne X5000 @ 2GHz / 4GB RAM / Radeon RX 550 / AmigaOS 4.1 Final Edition / MorphOS 3.17
Amiga1200 / Blizzard 1230 IV PiStorm32-lite / AmigaOS 3.9
Go to top
Re: Anyone Tried Compiling the latest WebKit?
Home away from home
Home away from home


See User information
@Primax

It require Qt

Go to top
Re: Anyone Tried Compiling the latest WebKit?
Just popping in
Just popping in


See User information
@samo79

...for GUI and networking, but:
"The browser and libraries are all written in C++".

Go to top

  Register To Post
« 1 2 (3)

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project