From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Cc: bug-guile@gnu.org
Subject: Re: Portability fixes for win32 cross compiling
Date: Fri, 28 May 2010 15:15:01 +0200 [thread overview]
Message-ID: <87bpc0f9re.fsf@gnu.org> (raw)
In-Reply-To: 20100415005116.GB28615@flap
Hi!
Volker Grabsch <vog@notjusthosting.com> writes:
> The "gen-scmconfig" script includes a mix of native and
> cross headers, which goes horribly wrong when performing
> win32 cross compiling.
What happens exactly?
> Is it really necessary to #include
> the "uniconv.h" from the cross system and to provide corresponding
> SCM_ICONVEH_* constants?
The idea is to avoid including libunistring headers in public Guile
headers, so that the dependency on libunistring isn’t visible from the
outside.
Perhaps we could extract the values in some other way, but I’d like to
make sure I understand the problem before attempting something.
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-05-28 13:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 0:51 Portability fixes for win32 cross compiling Volker Grabsch
2010-04-15 14:12 ` Mike Gran
2010-04-15 20:58 ` Volker Grabsch
2010-04-21 20:22 ` Volker Grabsch
2010-05-03 9:17 ` Volker Grabsch
2010-05-03 12:31 ` Greg Troxel
2010-05-21 10:09 ` Andy Wingo
2010-05-22 13:44 ` Ludovic Courtès
2010-05-24 20:30 ` Volker Grabsch
2010-05-28 13:10 ` Ludovic Courtès
2010-05-28 14:56 ` Volker Grabsch
2010-06-08 22:01 ` Ludovic Courtès
2010-06-08 22:12 ` No Itisnt
2010-06-09 6:42 ` Andy Wingo
2010-07-28 12:40 ` Volker Grabsch
2010-05-28 13:15 ` Ludovic Courtès [this message]
2010-05-28 14:44 ` Volker Grabsch
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bpc0f9re.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guile@gnu.org \
--cc=guile-devel@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).