[haiku-commits] Re: BRANCH mmadia-github.separate-build-environment - in headers/build: config_target os/support os_target/support

  • From: "Ingo Weinhold" <ingo_weinhold@xxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Fri, 03 Aug 2012 23:38:51 +0200

Matt Madia wrote:
> On 8/3/12, mmadia-github.separate-build-environment
> <community@xxxxxxxxxxxx> wrote:
> > added 3 changesets to branch
> > 'refs/remotes/mmadia-github/separate-build-environment'
> > old head: a996bce5a0b98a1c11c3e7d5bbffdf4eb1298eba
> > new head: 22142d098b60014995cebad90ce85ef48ce34e09
> >
> > diff --git a/headers/build/os_target/support/target_SupportDefs.h
> > b/headers/build/os_target/support/target_SupportDefs.h
> > new file mode 100644
> > index 0000000..ef5398d
> > --- /dev/null
> > +++ b/headers/build/os_target/support/target_SupportDefs.h
> 
> > +typedef volatile long _haiku_build_vlong;
> > +typedef volatile int _haiku_build_vint;
> > +typedef volatile short _haiku_build_vshort;
> > +typedef volatile char _haiku_build_vchar;
> > +
> > +typedef volatile unsigned long _haiku_build_vulong;
> > +typedef volatile unsigned int _haiku_build_vuint;
> > +typedef volatile unsigned short _haiku_build_vushort;
> > +typedef volatile unsigned char _haiku_build_vuchar;
> > +
> > +typedef unsigned char _haiku_build_uchar;
> > +typedef unsigned short _haiku_build_unichar;
> 
> Hrmm, were these supposed to be prefixed as well? e.g.,
> 
> typedef volatile _haiku_build_long _haiku_build_vlong;
> typedef volatile _haiku_build_int _haiku_build_vint;
> ...

No, not the built-in types. Just like the stuff provided by compiler headers.

CU, Ingo

Other related posts: