Closed
Bug 676315
Opened 14 years ago
Closed 14 years ago
ANGLE build problem: d3dx9.h not found unless $DXSDK_DIR points to it, since bug 641630 landed
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: bjacob, Unassigned)
Details
Attachments
(1 file)
|
1.78 KB,
patch
|
joe
:
review+
|
Details | Diff | Splinter Review |
As it turns out, our new ANGLE Makefiles only use DXSDK_DIR to look for headers.
Attachment #550431 -
Flags: review?(joe)
Comment 1•14 years ago
|
||
Comment on attachment 550431 [details] [diff] [review]
fix ANGLE build: find DXSDK headers
Review of attachment 550431 [details] [diff] [review]:
-----------------------------------------------------------------
Is MOZ_DIRECTX_SDK_PATH guaranteed to always be set?
::: gfx/angle/src/libEGL/Makefile.in
@@ +63,5 @@
> +LOCAL_INCLUDES = \
> + -I$(srcdir)/../../include \
> + -I$(srcdir)/.. \
> + -I"$(DXSDK_DIR)/include" \
> + -I"$(MOZ_DIRECTX_SDK_PATH)/include" \
These should be indented two spaces, I think.
::: gfx/angle/src/libGLESv2/Makefile.in
@@ +63,5 @@
> +LOCAL_INCLUDES = \
> + -I$(srcdir)/../../include \
> + -I$(srcdir)/.. \
> + -I"$(DXSDK_DIR)/include" \
> + -I"$(MOZ_DIRECTX_SDK_PATH)/include" \
Same here.
Attachment #550431 -
Flags: review?(joe) → review+
| Reporter | ||
Comment 2•14 years ago
|
||
(In reply to comment #1)
> Comment on attachment 550431 [details] [diff] [review] [diff] [details] [review]
> fix ANGLE build: find DXSDK headers
>
> Review of attachment 550431 [details] [diff] [review] [diff] [details] [review]:
> -----------------------------------------------------------------
>
> Is MOZ_DIRECTX_SDK_PATH guaranteed to always be set?
Yes. So actually I just realized that checking DXSDK_DIR here is useless and could even cause trouble in case of multiple DXSDKs installed. OK to remove DXSDK_DIR here?
>
> ::: gfx/angle/src/libEGL/Makefile.in
> @@ +63,5 @@
> > +LOCAL_INCLUDES = \
> > + -I$(srcdir)/../../include \
> > + -I$(srcdir)/.. \
> > + -I"$(DXSDK_DIR)/include" \
> > + -I"$(MOZ_DIRECTX_SDK_PATH)/include" \
>
> These should be indented two spaces, I think.
I was wondering. If I indent this with two spaces, will these two spaces end up in the command line? That's what I was trying to avoid.
| Reporter | ||
Comment 3•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•