C emum types representation inconsistency

[cheblin]

for C enum

typedef enum
{
	PROCESS_CHANNEL_REQEST = 0x7fffffff,
	PROCESS_HOST_REQEST = 0x7fffffff - 1,
	PROCESS_RECEIVED_PACKS = 0x7fffffff - 2,
} PROCESS;

on MACOS rust-bindgen generate

pub const PROCESS_PROCESS_CHANNEL_REQEST: PROCESS = 2147483647;
pub const PROCESS_PROCESS_HOST_REQEST: PROCESS = 2147483646;
pub const PROCESS_PROCESS_RECEIVED_PACKS: PROCESS = 2147483645;

pub type PROCESS    = u32;

on Windows

pub const PROCESS_PROCESS_CHANNEL_REQEST: PROCESS = 2147483647;
pub const PROCESS_PROCESS_HOST_REQEST: PROCESS = 2147483646;
pub const PROCESS_PROCESS_RECEIVED_PACKS: PROCESS = 2147483645;

pub type PROCESS      = i32;

[emilio]

This is the type the underlying platform uses, so bindgen is doing the right thing.

This is a duplicate of #1244.