> Similarly, I think we should make driver-specific options more explicit.
Seems like a good idea. I would go for:
--driver mesa-kms|android|... --driver-opts mesa-kms:mesa-kms-opt=1,android:android-opt=2,all-platforms-opt=3
Where driver-opts can be used even without an explicit driver setting. The reason is to allow invocations to work across platforms without change. So a script that wants to run everywhere, but wants to use VT 1 on mesa-kms can just use:
unity-system-compositor --driver-opts mesa-kms:vt=1
« Back to merge proposal
> Similarly, I think we should make driver-specific options more explicit.
Seems like a good idea. I would go for:
--driver mesa-kms| android| ... mesa-kms- opt=1,android: android- opt=2,all- platforms- opt=3
--driver-opts mesa-kms:
Where driver-opts can be used even without an explicit driver setting. The reason is to allow invocations to work across platforms without change. So a script that wants to run everywhere, but wants to use VT 1 on mesa-kms can just use:
unity-system- compositor --driver-opts mesa-kms:vt=1