[Webkit-unassigned] [Bug 17006] New: [GTK] Header path should be webkit/webkit.h
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Jan 25 07:17:32 PST 2008
http://bugs.webkit.org/show_bug.cgi?id=17006
Summary: [GTK] Header path should be webkit/webkit.h
Product: WebKit
Version: 525+ (Nightly build)
Platform: All
OS/Version: All
Status: NEW
Keywords: Gtk
Severity: Normal
Priority: P2
Component: WebKit Gtk
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: alp at atoker.com
CC: mrowe at apple.com
Right now, GTK+ API headers get installed into the top level include directory,
eg. /usr/include/WebKitGtk/*.h
This means that developers do this in applications:
#include <webkit.h>
Our own webkit.h looks like this:
#ifndef __WEBKIT_H__
#define __WEBKIT_H__
#include <webkitdefines.h>
#include <webkitnetworkrequest.h>
#include <webkitwebframe.h>
#include <webkitwebsettings.h>
#include <webkitwebview.h>
#endif /* __WEBKIT_H__ */
I propose that we rename WebKit/gtk/WebView to WebKit/gtk/webkit to allow:
#include <webkit/webkit.h>
This matches GTK+ module conventions.
The alternative is to use ForwardingHeaders, which would help avoid the
renaming in SVN, but the benefits of this aren't too clear for non-Apple APIs,
and it would add maintenance overhead.
All in favour of renaming this directory and updating the necessary build
systems and headers?
--
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list