From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: rfc/rfh: i686-w64-mingw32 cross target
Date: Sat, 02 Apr 2016 09:30:08 +0200 [thread overview]
Message-ID: <87d1q8lb7j.fsf@drakenvlieg.flower> (raw)
In-Reply-To: <8760w2nzl4.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 31 Mar 2016 22:48:23 +0200")
Ricardo Wurmus writes:
> I think these are the only patches I needed. Could you give an example
> of what things need to be patched for mingw?
The two top commits here are for ncurses and readline
https://github.com/janneke/guix/tree/wip-hurd+mingw
(work in progress). Typically: configure flags, adding gnulib modules,
gnulib updates, dealing with non-posix or mingw-specific libc stuff.
Many more examples here
https://github.com/janneke/gub/tree/master/patches
Greetings,
Jan
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
next prev parent reply other threads:[~2016-04-02 7:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 17:38 rfc/rfh: i686-w64-mingw32 cross target Jan Nieuwenhuizen
2016-03-27 14:20 ` [RFCv2] build: i686-w64-mingw32: new " Jan Nieuwenhuizen
2016-03-27 16:17 ` Pjotr Prins
2016-03-31 20:16 ` rfc/rfh: i686-w64-mingw32 " Ricardo Wurmus
2016-03-31 20:26 ` Jan Nieuwenhuizen
2016-03-31 20:48 ` Ricardo Wurmus
2016-04-02 7:30 ` Jan Nieuwenhuizen [this message]
2016-04-07 21:12 ` Ludovic Courtès
2016-04-14 6:30 ` Jan Nieuwenhuizen
2016-04-19 14:54 ` Ludovic Courtès
2016-04-24 21:40 ` [PATCH v4 1/9] gnu: cross: Use CROSS_*_INCLUDE_PATH for system headers Jan Nieuwenhuizen
2016-04-25 10:38 ` Andy Wingo
2016-04-25 11:28 ` Jan Nieuwenhuizen
2016-04-26 8:00 ` Andy Wingo
2016-04-26 8:37 ` Jan Nieuwenhuizen
2016-04-26 9:03 ` Jan Nieuwenhuizen
2016-04-25 22:06 ` Jan Nieuwenhuizen
2016-04-26 9:02 ` Andy Wingo
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=87d1q8lb7j.fsf@drakenvlieg.flower \
--to=janneke@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.