The HW specific driver depends on "-lXfixes -lXdamage" to do correct display under rotation mode, but a issue is found that after vaTerminate, XCloseDisplay will meet a SIGSEGV, and debuging shows libXdamage is unloaded from application address space after vaTerminate, and keeping libXdamage all along can workaround this issue. So always link libva with libXdamage here
The HW specific driver depends on "-lXfixes -lXdamage" to do correct display
under rotation mode, but a issue is found that after vaTerminate, XCloseDisplay
will meet a SIGSEGV, and debuging shows libXdamage is unloaded from application
address space after vaTerminate, and keeping libXdamage all along can workaround
this issue. So always link libva with libXdamage here

01org/libva-cros,pma1/libva,chenxianqin/vaapi-libva,CyanogenMod/android_hardware_intel_libva,01org/iotg-lin-gfx-libva,gbeauchesne/libva,zzhhui/libva,zzhhui/libva,pma1/libva,Distrotech/libva,halleyzhao/libva-fdo,CyanogenMod/android_hardware_intel_libva,Distrotech/libva,halleyzhao/libva-fdo,01org/libva-cros,01org/iotg-lin-gfx-libva,halleyzhao/libva-fdo,gbeauchesne/libva,01org/libva-cros,android-ia/hardware_intel_libva,01org/iotg-lin-gfx-libva,chenxianqin/vaapi-libva,gbeauchesne/libva,zzhhui/libva,android-ia/hardware_intel_libva,CyanogenMod/android_hardware_intel_libva,Distrotech/libva,android-ia/hardware_intel_libva,pma1/libva,chenxianqin/vaapi-libva