Opened 2 years ago

Closed 2 years ago

#17536 closed bug (fixed)

HaikuWebKit 614.1.1 build fails on 64 bit

Reported by: vidrep Owned by: pulkomandy
Priority: normal Milestone: Unscheduled
Component: Applications/WebPositive Version: R1/beta3
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

hrev55788 x86_64

HaikuWebKit 614.1.1 build fails on 64 bit

HaikuWebKit build log attached

Attachments (1)

HaikuWebKit.log (12.8 KB ) - added by vidrep 2 years ago.

Download all attachments as: .zip

Change History (7)

by vidrep, 2 years ago

Attachment: HaikuWebKit.log added

comment:1 by diver, 2 years ago

Seems to be related to hrev55770.

comment:2 by pulkomandy, 2 years ago

Yes, I have not updated my Haiku install yet so I didn't get that problem.

@waddlesplash I think the very fast deprecation of the old APIs makes it impossible to provide a WebKit that builds on both nightlies and beta? This makes it difficult to ship a WebKit update for beta from me.

Not really a problem because I need to do some changes to BBitmap::LockBits as well anyway...

comment:3 by waddlesplash, 2 years ago

Yeah, maybe it wasn't such a good idea to hard-deprecate the APIs so quickly.

comment:4 by nephele, 2 years ago

Do we have a deprecation policy?

In any case, it would be fine if we do this, if haikuports had a branch, atleast for some ports. That is for applications that have specific code for severall haiku versions they be compiled for those aswell, we could do a compile time switch then.

comment:5 by pulkomandy, 2 years ago

Do we have a deprecation policy?

The strict/official policy is that only the part of the API/ABI that was in BeOS is currently guaranteed to be stable. These functions are Haiku extensions.

That is a bit unrealistic, no one (almost) is going to write code that still runs on BeOS. But to change that policy we would need to make an R1 release and clearly define what is or isn't part of its stable ABI/API.

comment:6 by pulkomandy, 2 years ago

Resolution: fixed
Status: newclosed

The change in WebKit is only in the testing tools (DumpRenderTree) so we can manage to ship a version of the libs that works on both beta and nightlies.

For now the code has been changed to build correctly on nightlies.

Note: See TracTickets for help on using tickets.