On Sun, Jan 31, 2010 at 9:59 PM, David Cleaver <[email protected]> wrote: > Hello, thank you all for your replies. I seem to be having some trouble > getting > __MINGW64_VERSION_MAJOR to work for me. Perhaps I have set up my environment > wrong? I've downloaded mingw-w64-bin_x86_64-mingw_20100123_sezero.zip and > extracted it to its own folder, at c:\mingw64-20100123\ (which has bin, lib, > lib64, etc in it). Then I have created a command prompt, that when I start > it, > it sets the PATH to: PATH C:\mingw64-20100123\bin;C:\msys\1.0\bin;%PATH% > Does this look reasonable so for?
Perfect start. > I was wondering, how does it know where the correct *.h or *.a files are? I > see > that most of them are not in \include or \lib, but are under > \x86_64-w64-mingw32\include and \x86_64-w64-mingw32\lib. Does the gcc.exe in > \bin know where to look for these files. It typically finds failes relative to itself, along with several hard coded directories. You can use the option "-print-search-dirs" or something similar (I forget exactly what it is offhand) to gcc to see where it looks. You can also use gcc -v to see all the options it passes to ld. ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
