-
Notifications
You must be signed in to change notification settings - Fork 162
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
Comments
Hello I've just come across this too, configuring explicitly with the following...
... yields ...
Best |
As a 'quick fix' you can edit Makefile.am as follows... Original
Modified
Make sure to run Best |
Hi guys, stumbled upon this bug too. Can this get fixed please? |
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. |
Is #159 a better fix? |
Hmmm... maybe not. |
AFAICT, sfcsample does not use X11 anywhere... so the inclusion of X11 headers is cruft. |
Fixes intel#150 Signed-off-by: kanghuaz <kanghua.zhu@intel.com>
X11 is never used, so don't include the headers. Fixes intel#150 Signed-off-by: kanghuaz <kanghua.zhu@intel.com>
The sfc sample added in 2.4.0 doesn't build when USE_X11 is false. It should have skipped compiling this sample.
The text was updated successfully, but these errors were encountered: