On Tue, Jun 15, 2010 at 11:13 PM, Xiaofan Chen wrote: > On Wed, Jun 16, 2010 at 10:43 AM, Mike Frysinger wrote: >>> If you look into the different between cygwin and mingw. >>> you will find mingw have some excited features, the big one is >>> the result build out just can run in windows, not depend on any >>> third-party DLL or environment. >> >> and it works fine cross-compiling from Linux for mingw > > Yes it probably works well under Linux using Cross-Compiling. > However, not all users have access to Linux or want to use > Linux. > > If a project is strives to be cross-platfrom, then it is good > to support different compilers and different OS, within > certain limit.
also, let me clarify some misconceptions you seem to have about open source and cross platform projects. people working on open source projects (like urjtag) do it for fun. they work on things they find interesting. support for many platforms exist only because someone did the work to get it going. it does not mean the developers of said project care about any specific target (like mingw) or that they're "supposed" to work on it. someone did the work and they merged the support (often times without ever testing it directly themselves). (yes, in general some people might be paid for their work with open source projects, but the money flow there tends to be aligned with the interests of the party paying said developer, and i highly doubt anyone has interests aligned with "make it compile natively under Windows via mingw") i also find it a bit ironic that you talk about not wanting to be forced to work with Linux while turning around and expecting other people who could care less about building under Windows to investigate/fix/workaround their problems. the problem you have appears to be a bug in your (and perhaps general mingw) Windows setup which means its on you and/or people who are interested in working on it to research. if it turns out to be a bug in the urjtag's m4 code, then it would be on my head to fix it and/or talk with the m4 developers. fortunately for me though, many people have shown it to work fine on *nix, *bsd, and cygwin systems. if it does turn out to be a bug in mingw's m4/autoconf/automake, i'm not terribly interested in contorting the code in odd ways to try and figure out how to make it work on all platforms. this too would be on the head of anyone who is interested in making it work natively under mingw make it work. and then it'd be up to someone like me to approve/reject that workaround based on how crazy it is. if the result is ugly and unmaintainable, then the answer is "upgrade your broken Windows setup". if it perhaps a minor whitespace tweak, then i can live with it. maybe some urjtag developer would find it interesting to more directly assist/research your problem. but at this point in time, that does not seem to be the case. -mike ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ UrJTAG-development mailing list UrJTAG-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/urjtag-development
