Summary: | WebKit GTK include and lib directory is in qt4-named directory | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | KIMURA Masaru <hiyuh.root> | ||||
Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | ||||||
Priority: | P2 | ||||||
Version: | 523.x (Safari 3) | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Attachments: |
|
Description
KIMURA Masaru
2007-11-04 04:41:23 PST
Created attachment 17030 [details]
Use sane default install paths for the gtk port
This patch defaults to /usr/local and /usr/local/include/WebKitGtk respectively. I don't think we want to install GtkLauncher.
At #webkit, bdash tells why gtk port was installed into that weird location. He said http://live.gnome.org/WebKitGtk mentioned to use --qmakearg. I've updated my ebuild[1] (was linked my previous post) to make it install into correct location /usr/include/WebKit and /usr/lib64 already. Because Gentoo won't install to /usr/local via portage. But to merge this fix to upstream would be better, I think. Note, to reproduce this weird install result is only do w/o --qmakearg which is mentioned at http://live.gnome.org/WebKitGtk. (In reply to comment #1) > Created an attachment (id=17030) [edit] > Use sane default install paths for the gtk port > > This patch defaults to /usr/local and /usr/local/include/WebKitGtk > respectively. I don't think we want to install GtkLauncher. The patch should get a positive review. Yes we should not install the GtkLauncher as it is using rpath for linking because we/I currently don't want it to be installed. Comment on attachment 17030 [details]
Use sane default install paths for the gtk port
r=me
|