Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build failure when x11 support is disabled #150

Closed
anujm1 opened this issue Feb 8, 2019 · 8 comments
Closed

build failure when x11 support is disabled #150

anujm1 opened this issue Feb 8, 2019 · 8 comments

Comments

@anujm1
Copy link

anujm1 commented Feb 8, 2019

The sfc sample added in 2.4.0 doesn't build when USE_X11 is false. It should have skipped compiling this sample.

@solabc16
Copy link

solabc16 commented Feb 9, 2019

Hello

I've just come across this too, configuring explicitly with the following...

./configure             \
    --prefix=<somepath> \
    --enable-shared     \
    --disable-static    \
    --disable-x11       \
    --disable-wayland   \
    --disable-tests

... yields ...

VDecAccelVA.h:42:10: fatal error: X11/Xlib.h: No such file or directory
 #include <X11/Xlib.h>
          ^~~~~~~~~~~~
compilation terminated.

Best
-James

@solabc16
Copy link

solabc16 commented Feb 9, 2019

As a 'quick fix' you can edit Makefile.am as follows...

Original

SUBDIRS = common decode encode vainfo videoprocess vendor/intel vendor/intel/sfcsample

if USE_X11
SUBDIRS += putsurface
else
if USE_WAYLAND
SUBDIRS += putsurface
endif
endif

Modified

SUBDIRS = common decode encode vainfo videoprocess vendor/intel

if USE_X11
SUBDIRS += putsurface vendor/intel/sfcsample
else
if USE_WAYLAND
SUBDIRS += putsurface
endif
endif

Make sure to run autoreconf -fiv before you run configure.

Best
- James

@driesmp
Copy link

driesmp commented Mar 7, 2019

Hi guys, stumbled upon this bug too. Can this get fixed please?

@jonozzz
Copy link

jonozzz commented Apr 18, 2019

The fix, translated into a patch would be:

--- Makefile.am.orig    2019-04-18 06:40:11.621443043 +0000
+++ Makefile.am 2019-04-18 06:40:26.605537495 +0000
@@ -24,10 +24,10 @@

 AUTOMAKE_OPTIONS = foreign

-SUBDIRS = common decode encode vainfo videoprocess vendor/intel vendor/intel/sfcsample
+SUBDIRS = common decode encode vainfo videoprocess vendor/intel

 if USE_X11
-SUBDIRS += putsurface
+SUBDIRS += putsurface vendor/intel/sfcsample
 else
 if USE_WAYLAND
 SUBDIRS += putsurface

Thanks @solabc16 for figuring it out.

@uartie
Copy link
Contributor

uartie commented May 7, 2019

Is #159 a better fix?

@uartie
Copy link
Contributor

uartie commented May 7, 2019

Is #159 a better fix?

Hmmm... maybe not. #include <X11/Xlib.h> is still in the header file.

@uartie
Copy link
Contributor

uartie commented May 7, 2019

AFAICT, sfcsample does not use X11 anywhere... so the inclusion of X11 headers is cruft.

@uartie
Copy link
Contributor

uartie commented May 7, 2019

@kanghuaz

kanghuaz added a commit to kanghuaz/libva-utils that referenced this issue May 10, 2019
Fixes intel#150

Signed-off-by: kanghuaz <kanghua.zhu@intel.com>
kanghuaz added a commit to kanghuaz/libva-utils that referenced this issue May 10, 2019
X11 is never used, so don't include the headers.

Fixes intel#150

Signed-off-by: kanghuaz <kanghua.zhu@intel.com>
@uartie uartie closed this as completed in 7be46f0 May 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants