WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
Bug 178878
[WPE] Use proper shared object versioning for libWPEWebKit.so
https://bugs.webkit.org/show_bug.cgi?id=178878
Summary
[WPE] Use proper shared object versioning for libWPEWebKit.so
Adrian Perez
Reported
2017-10-26 11:03:29 PDT
We should be using “CALCULATE_LIBRARY_VERSIONS_FROM_LIBTOOL_TRIPLE()” to give “libWPEWebKit.so” a proper shared object version. There's a macro for this in “Source/cmake/OptionsGTK.cmake” which could be moved to a common location and then used by both the GTK+ and WPE ports.
Attachments
Patch
(3.95 KB, patch)
2017-10-26 11:10 PDT
,
Adrian Perez
no flags
Details
Formatted Diff
Diff
Patch for landing
(3.95 KB, patch)
2017-10-26 13:25 PDT
,
Adrian Perez
no flags
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Adrian Perez
Comment 1
2017-10-26 11:10:49 PDT
Created
attachment 325032
[details]
Patch
Michael Catanzaro
Comment 2
2017-10-26 11:25:28 PDT
Comment on
attachment 325032
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=325032&action=review
> Source/cmake/OptionsWPE.cmake:4 > +SET_PROJECT_VERSION(2 19 0)
Please use 0 19 0 for WPE, like we discussed internally today. We can always raise the first version later, and I absolutely plan to do that, but for now keeping a leading 0 would be nice to indicate it's still unstable. Alternatively, if you prefer, you could add an optional nano version (that would not be used for WebKitGTK+) and make it 0 2 19 0. Maybe that would be the least-confusing option.
Adrian Perez
Comment 3
2017-10-26 13:23:45 PDT
(In reply to Michael Catanzaro from
comment #2
)
> Comment on
attachment 325032
[details]
> Patch > > View in context: >
https://bugs.webkit.org/attachment.cgi?id=325032&action=review
> > > Source/cmake/OptionsWPE.cmake:4 > > +SET_PROJECT_VERSION(2 19 0) > > Please use 0 19 0 for WPE, like we discussed internally today. We can always > raise the first version later, and I absolutely plan to do that, but for now > keeping a leading 0 would be nice to indicate it's still unstable.
Oh, this slipped out from the patch. I'll fix and re-upload.
> Alternatively, if you prefer, you could add an optional nano version (that > would not be used for WebKitGTK+) and make it 0 2 19 0. Maybe that would be > the least-confusing option.
I think three version numbers are more than enough. It's fine having zero as major for now, because in the longer term we'll make them converge.
Adrian Perez
Comment 4
2017-10-26 13:25:21 PDT
Created
attachment 325048
[details]
Patch for landing
WebKit Commit Bot
Comment 5
2017-10-26 13:57:12 PDT
Comment on
attachment 325048
[details]
Patch for landing Clearing flags on attachment: 325048 Committed
r224047
: <
https://trac.webkit.org/changeset/224047
>
WebKit Commit Bot
Comment 6
2017-10-26 13:57:14 PDT
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug