On 15:49 Wed 21 Sep , Hefty, Sean wrote:
What is your end goal? To have one code base for OpenSM that would be able
to
be compiled on both Linux and Windows based on __WIN__ definition?
My end goal is to decrease the maintenance cost porting opensm to Windows.
Ideally, I'd like to
On 14:23 Tue 20 Sep , Hefty, Sean wrote:
Why to test for __WIN__ instead of _WIN32 (defined both when building
32-bit and 64-bit code -- see also
http://msdn.microsoft.com/en-us/library/b0084kay%28v=vs.80%29.aspx) ?
I have no idea. This is just what's currently in the code. I can
); o...@lists.openfabrics.org
Subject: Re: creating common ib_types.h for linux and windows
On 14:23 Tue 20 Sep , Hefty, Sean wrote:
Why to test for __WIN__ instead of _WIN32 (defined both when building
32-bit and 64-bit code -- see also
http://msdn.microsoft.com/en-us/library/b0084kay%28v
What is your end goal? To have one code base for OpenSM that would be able to
be compiled on both Linux and Windows based on __WIN__ definition?
My end goal is to decrease the maintenance cost porting opensm to Windows.
Ideally, I'd like to have a common code base for opensm, similar to what
On Mon, Sep 19, 2011 at 11:20 PM, Hefty, Sean sean.he...@intel.com wrote:
It would be easier to maintain opensm on windows if it truly shared the same
code base. For now, I'd just like to start with a common ib_types.h file.
(There are currently hundreds, if not thousands, of lines that
It would be easier to maintain opensm on windows if it truly shared the same
code base. For now, I'd just like to start with a common ib_types.h file.
(There are currently hundreds, if not thousands, of lines that differ.)
ib_types.h uses #if defined(__WIN__) to separate linux from windows
