On 6/12/2010 14:19, Michael Adams wrote: > I heartily thank the developers for putting together this project: it > allowed me to port several pieces of software to 64-bit that I regularly > use. > > http://unquietwiki.blogspot.com/2010/06/evening-spent-cranking-out-windows-x64.html >
Hi, To clear up some confusion: > * Make a copy of "mingw32-make.exe" as "make.exe" for easier compiling. You shouldn't do this as make.exe is for msys make. msys make can understand UNIX paths that are used with autotools based packages. For make command under plain cmd, use mingw32-make instead. This is a deliberate decision by the msys/mingw.org developers. > * The x64 toolchain uses filenames prefixed with "x86_64-w64-mingw32-": > lengthy, but it keeps them distinct from the 32-bit toolchain and you can > quickly change commands in Makefiles to reflect its usage. Prefixed filenames are used because they are really setup as cross compilers, but from Window's point of view, they behave similarly. > * I did learn that it may be useful to copy other 64-bit .lib files as .la or > .a files to the x64 toolchain's lib folder true, the folder layout differs from traditional mingw.org layout, so installing libs will be more involved. Hope that helped. ------------------------------------------------------------------------------ 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 _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
