compiling for 64bit: types and format strings

Hi,

While I have no 64bit system, I recently submitted a compilation
job to WTB and saw dozens of warnings unknown to me so far,
mostly about printf format strings.  The reason for the warnings
is that WTB compiles in 64 bit mode, while I only know 32bit systems.

Is there anything us 32bit users can do to prevent such warnings
or shall we patiently wait until AJ checks in 64bit fixes?
(BTW, thank you for the recent winmm one).
Or compile every patch on WTB first?

More specifically, regarding format strings, I'm unsure
whether it's actually possible to find %d/%ld formats that work
on both systems for all types one comes across (UINT, MMRESULT etc.)
What's the receipe?

Thank you,
 Jörg Höhle

[Alexandre Julliard]

 writes:
> More specifically, regarding format strings, I'm unsure
> whether it's actually possible to find %d/%ld formats that work
> on both systems for all types one comes across (UINT, MMRESULT etc.)
> What's the receipe?

All Win32 types are the same across platforms and can be printed without
issues (except on Mingw but we don't care). Standard C types like size_t
vary across platforms and should be avoided in traces.

[Michael Stefaniuc]

On 02/17/2010 05:06 PM, Alexandre Julliard wrote:
>   writes:
> > More specifically, regarding format strings, I'm unsure
> > whether it's actually possible to find %d/%ld formats that work
> > on both systems for all types one comes across (UINT, MMRESULT etc.)
> > What's the receipe?
>
> All Win32 types are the same across platforms and can be printed without
> issues (except on Mingw but we don't care). Standard C types like size_t
> vary across platforms and should be avoided in traces.

More to Jörg's question the WTB uses Mingw to build the tests and thus 
those warnings should be ignored.

bye
    michael