This is the mail archive of the
mailing list for the Cygwin project.
Re: Adding MSYS functionality to Cygwin
- From: "Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>
- To: cygwin at cygwin dot com
- Date: Wed, 19 Jun 2013 13:38:06 -0500
- Subject: Re: Adding MSYS functionality to Cygwin
- References: <CABEPuQJDLjtbcLig1isTUJgb6RBCD8LNShbm9mTPcb9WM5S5fw at mail dot gmail dot com> <51C0B08E dot 8080900 at etr-usa dot com> <CABEPuQJJpRfPKSwZ7M0eTOdp1HxDcmvuy1=qXFHBw-8kLkZ1ZQ at mail dot gmail dot com> <51C0D956 dot 4090905 at etr-usa dot com> <51C1B299 dot 1000701 at cwilson dot fastmail dot fm> <51C1F0F9 dot 70601 at etr-usa dot com>
On 2013-06-19 12:57, Warren Young wrote:
Not all packages are cross-compiler-compatible.
Is that another way of saying that not all packages use autotools? :)
autotools can certainly make cross-compiling easier than most other
build systems, but it's not a guarantee either. For instance, anything
that requires in-tree compiled executables to run (e.g. AC_RUN_IFELSE
configure tests, GObject Introspection generation, etc.) requires either
workarounds, or simply cannot be cross-compiled.
You're not talking about anything different than the sort of thing
Cygwin package maintainers go through, sometimes needing to arm-twist
odd build systems to behave according to cygport's expectations?
I think you mean Cygwin's expectations?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple