RESOLVED FIXED 177273
REGRESSION(r222194) [WPE] Library and executable output names broken
https://bugs.webkit.org/show_bug.cgi?id=177273
Summary REGRESSION(r222194) [WPE] Library and executable output names broken
Carlos Alberto Lopez Perez
Reported 2017-09-20 14:43:50 PDT
Not sure what caused this but it was something recent. $ Tools/Scripts/run-minibrowser --wpe Can't find built framework at "/home/clopez/webkit/wpe/WebKitBuild/Release/lib/libWPEWebKit.so". And if I try this patch --- a/Tools/Scripts/webkitdirs.pm +++ b/Tools/Scripts/webkitdirs.pm @@ -959,7 +959,7 @@ sub builtDylibPathForName } } if (isWPE()) { - return "$configurationProductDir/lib/libWPEWebKit.so"; + return "$configurationProductDir/lib/libWebKit.so"; } die "Unsupported platform, can't determine built library locations.\nTry `build-webkit --help` for more information.\n"; Then i get: $ Tools/Scripts/run-minibrowser --wpe Starting dyz lib/wpe.lua:3: libWPEWebKit.so: cannot open shared object file: No such file or directory
Attachments
Patch (2.67 KB, patch)
2017-09-20 15:10 PDT, Michael Catanzaro
no flags
Carlos Alberto Lopez Perez
Comment 1 2017-09-20 14:51:48 PDT
This was caused by r222194 <https://trac.webkit.org/r222194> I reverted it locally, triggered a clean build and now I get libWPEWebKit.so generated correctly and the minibrowser works back as expected. BTW.. I have just triggered clean builds on the WPE bots, as I suspect they were running all this time using the old libWPEWebKit.so (from <r222194)
Michael Catanzaro
Comment 2 2017-09-20 15:10:06 PDT
Carlos Alberto Lopez Perez
Comment 3 2017-09-20 15:35:47 PDT
Comment on attachment 321379 [details] Patch Tested. it works ok. Thanks!
WebKit Commit Bot
Comment 4 2017-09-20 16:05:27 PDT
Comment on attachment 321379 [details] Patch Clearing flags on attachment: 321379 Committed r222296: <http://trac.webkit.org/changeset/222296>
WebKit Commit Bot
Comment 5 2017-09-20 16:05:30 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.