Bug 52887 - GraphicsContext3D.h: No such file or directory
Summary: GraphicsContext3D.h: No such file or directory
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-21 05:33 PST by Alexey Shabalin
Modified: 2011-03-10 12:47 PST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Shabalin 2011-01-21 05:33:14 PST
if build release webkit-1.3.10 with --enable-3D-canvas
then have error:

In file included from Source/WebCore/bindings/js/JSCanvasRenderingContextCustom.cpp:32:0:
./Source/WebCore/html/canvas/WebGLRenderingContext.h:32:31: fatal error: GraphicsContext3D.h: No such file or directory
compilation terminated.

Why GraphicsContext3D.h not included in release tar.gz?
Comment 1 Patrick R. Gansterer 2011-01-23 14:22:14 PST
which port do you use?
which tar.gz are you using?
does the build wok with with the current trunk?
Comment 2 Alexey Shabalin 2011-01-25 03:37:33 PST
I download from http://webkitgtk.org/webkit-1.3.10.tar.gz
I know that this files exist in svn, but why not included release?
Who is release manager?
Comment 3 Martin Robinson 2011-01-25 08:45:26 PST
(In reply to comment #2)
> I download from http://webkitgtk.org/webkit-1.3.10.tar.gz
> I know that this files exist in svn, but why not included release?
> Who is release manager?

Hey Alexey, the WebGL flag probably shouldn't have been advertised. It's still at a very early stage. Hopefully in the next release it will be functional, but for the moment it isn't. Thanks for reporting this bug. I'm going to close it in favor of bugs tracking specific pieces of WebGL support.
Comment 4 Alexey Shabalin 2011-01-27 11:07:46 PST
ok.
what about my other bugs? (50948, 50954, 52889).
I think that files must exist in release tar.gz.
Clone the git or svn repository is very expensive - more than 1G of traffic.
Comment 5 Alexey Shabalin 2011-03-10 05:04:49 PST
> Hey Alexey, the WebGL flag probably shouldn't have been advertised. It's still at a very early stage. Hopefully in the next release it will be functional, but for the moment it isn't. Thanks for reporting this bug. I'm going to close it in favor of bugs tracking specific pieces of WebGL support.

If webgl is a very early stage, why i see in configure default enable? :

[enable support for (WebGL [default=yes]]),

webkit-1.3.12
Comment 6 Martin Robinson 2011-03-10 12:47:42 PST
(In reply to comment #5)
> > Hey Alexey, the WebGL flag probably shouldn't have been advertised. It's still at a very early stage. Hopefully in the next release it will be functional, but for the moment it isn't. Thanks for reporting this bug. I'm going to close it in favor of bugs tracking specific pieces of WebGL support.
> 
> If webgl is a very early stage, why i see in configure default enable? :
> 
> [enable support for (WebGL [default=yes]]),
> 
> webkit-1.3.12

It seems that the help message in this case was just inaccurate. Thanks for pointing that out. I've updated it here:  http://trac.webkit.org/changeset/80747