[ofw] RE: [PATCH 9/8] [ib-diag] ibping: add support for WinOF

Sean Hefty sean.hefty at intel.com
Wed Feb 18 09:50:21 PST 2009


>Guess it is about report() function. Why to not make everything cdecl
>(by using compiler/linker flag or some super-#pragma in config.h or so)?

The WDK build environment uses stdcall by default.  Visual Studio uses cdecl.  I
have not yet figured out how to override the WDK using stdcall.  Simply adding a
switch (/Gd or whatever it is) doesn't work, nor did the other 50 things that I
tried.

Top personnel are working on the issue.  Please stand by.  Thank you for your
continued patience.  We apologize for any inconvenience.  *cue hold music*

>Ugh, I really fail to understand why WinOF cannot evaluate an option of
>using less "special" build tools for WDK insensitive code (such as
>user-space programs ported from linux) - it would solve all those issues
>just magically. And we are not entered yet a more complicated porting
>areas such as pthreads...

I have no problem with it.  But it does require two build environments.  The
current WinOF setup uses a single build environment to build the drivers and
related userspace libraries and applications.  This is a fairly common practice.
I don't know that this is all that different than how OFED packages everything
together.

My plan for more complicated porting areas is to use complib, and fix any issues
that arise.  That's what it was designed for.

- Sean




More information about the ofw mailing list