From: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>,
"linux-rdma
(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Hal Rosenstock
(hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org)"
<hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"ofw-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org"
<ofw-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>
Subject: Re: creating common ib_types.h for linux and windows
Date: Sun, 25 Sep 2011 13:39:29 +0300 [thread overview]
Message-ID: <20110925103929.GB2372@calypso.mtl.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A8237316E66732-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
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 have a common code base for opensm, similar to what we have for ibmad and ib-diags. Whether we achieve that using #ifdef's, OS specific header files, some other means (such as a windows specific patches to complete the conversion), or a combination of these, I don't really care.
I guess in case of ib_types.h that includes lots of #ifdef's, it would be
better to use a separate file. But for other files such as osm_base.h, it
would be much overhead to separate Windows related stuff to a different file.
-- Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-09-25 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 21:20 creating common ib_types.h for linux and windows Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237316E65191-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-09-20 6:06 ` Bart Van Assche
[not found] ` <CAO+b5-p0O5N6ZZacYGNjz4+H=W3hX6O7kw5pO=XqXSdh3FEdhA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-20 14:23 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237316E6526F-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-09-21 13:29 ` Alex Netes
[not found] ` <20110921132945.GA3767-iQai9MGU/dze+A/uUDamNg@public.gmane.org>
2011-09-21 14:15 ` Smith, Stan
2011-09-21 15:49 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237316E66732-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-09-25 10:39 ` Alex Netes [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110925103929.GB2372@calypso.mtl.com \
--to=alexne-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=bvanassche-HInyCGIudOg@public.gmane.org \
--cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ofw-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox