[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] byteswap.h

From: Alois Schlögl
Subject: Re: [Mingw-cross-env-list] byteswap.h
Date: Mon, 30 May 2011 09:59:49 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110505 Iceowl/1.0b1 Icedove/3.0.11

On 05/29/11 11:36, Volker Grabsch wrote:
Alois Schloegl schrieb:
The biosig project supports over 40 different data formats, some of these
data formats are big endian.
To handle these data formats, I'm using on linux/gcc,

It seems that byteswap.h is currently not available within mingw-cross-env.
Therefore, I'm wondering whether byteswap.h could be included in
mingw-cross-env, too?
These are actually two questions.

First: Why is byteswap.h not part of MinGW? Note that this question is
off-topic here. It has been answered on the MinGW Users list years ago:


Second: Can we include an alternative implementation of byteswap.h
in mingw-cross-env? Of course we could, for instance by providing
a package for that. For instance, we could take it from Gnulib:


However, I don't think this is the "right" way to do it, because
the Gnulib says:

"Gnulib takes a different approach. Its components are intended
  to be shared at the source level, rather than being a library
  that gets built, installed, and linked against. Thus, there is
  no distribution tarball; the idea is to copy files from Gnulib
  into your own source tree."

So I recommend that you copy Gnulib's byteswap.h into your source
tree, and to handle it as some kind of compatibility layer. Also,
you might want to include other Gnulib files you are interested in.

(As always, feel free to disagree with me. If you have compelling
  reasons not to go that route, just complain and we'll talk about
  alternative approaches such as providing some kind of "byteswap"
  or "gnulib" package.


No, I do not disagree. I was just wondering what the recommend approach to such a situation is.
Thanks for the detailed background information and your recommendation.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]