Under Android building environment, the data type "enum" is defined as a byte.
But our kernel is built with another toolchain, which defines "enum" as int. And this affect all data structures through IO control. To use our kernel driver, the related module must be compiled with a cflag "-fno-short-enums". But if this module's API also involve "enum" type data, other modules will be affected too. Anyone could give me a suggestion? Shall I build my kernel with android tool chain to make sure "enum" type is same between kernel and user space? Or build a adapter module with "-fno-short-enums" for the kernel driver, and let this module never use "enum" in its API? Many thanks! Jasperr --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
