Re: msys-autoconf 2.69-2
waterlan <waterlan-qWit8jRvyhVmR6Xm/[email protected]>
| Newsgroups | gmane.comp.gnu.mingw.devel |
|---|---|
| Message-ID | <[email protected]> |
Earnie Boyd schreef op 2013-03-05 17:11: > On Tue, Mar 5, 2013 at 10:23 AM, waterlan wrote: >> >> In msys-autoconf 2.68-1 I only find some patches which came straight >> from Debian. I don't see what is msys specific about that. >> Msys uses the standard default prefix /usr, like Linux. >> >> I can imagine that mingw32-autoconf needs specific patches, because >> mingw32 requires a non-standard default prefix /mingw/. So I expect >> that >> the difference with upstream autoconf is in mingw32-autoconf, not >> msys-autoconf. I did not look into mingw32-autoconf. >> > > I think the idea was that msys-autoconf was to be thought of an MSYS > developer tool. Yes, when you develop msys programs, you must use msys-autoconf. Msys uses Cygwin installation paths, which tries to be "same as Linux". Alexey works on MSYS. He proposed new msys packages. mingw32 is not in question here. > I certainly don't use it that way and avoid the > mingw32-autoconf releases. When you build mingw32 programs you must use mingw32-autoconf. That's the point. If you develop only for msys, then you can ignore mingw32-autoconf. regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb