Re: RFC: Compiling as 16 bit

2010-09-02 Thread Alexandre Julliard
Morten Rønne writes: > That struct is already defined in wine/winbase16.h as PDB16. > > So I would like to do this in my test program: > #include > PDB16 *psp; > > In a perfect world this would be enough to have full access to the > PDB16 struct in the test program. > But alas, the world is

Re: RFC: Compiling as 16 bit

2010-09-02 Thread Morten Rønne
On 02-09-2010 21:21, Alexandre Julliard wrote: Morten Rønne writes: I am looking for a way to change windef.h so that it will create the correct base types for both 16 and 32 bit compile. Openwatcom defines the symbol __I86__ while compiling for 16 bit, is it acceptable that I use that to

Re: RFC: Compiling as 16 bit

2010-09-02 Thread Morten Rønne
On 02-09-2010 21:21, Alexandre Julliard wrote: Morten Rønne writes: I am looking for a way to change windef.h so that it will create the correct base types for both 16 and 32 bit compile. Openwatcom defines the symbol __I86__ while compiling for 16 bit, is it acceptable that I use that to

Re: RFC: Compiling as 16 bit

2010-09-02 Thread Alexandre Julliard
Morten Rønne writes: > I am looking for a way to change windef.h so that it will create the > correct base types for both 16 and 32 bit compile. > > Openwatcom defines the symbol __I86__ while compiling for 16 bit, is > it acceptable that I use that to create 16 bit types? > It seems that _MSC_VE

RFC: Compiling as 16 bit

2010-09-02 Thread Morten Rønne
This is related to the creation of the DOS test programs for which I have sent another mail. But this is a more generic question relating to the fact that openwatcom is a 16 bit compiler while gcc (of course) is a 32 bit compiler. Currently this have lead me to drop the inclusion of the files