|
From: LRN <lr...@gm...> - 2011-05-06 11:47:31
|
On 06.05.2011 13:15, tal - טל hadad - חדד wrote: > Thank you for all your support, sorry for being a noob. > It's configuring well now, but still one more problem- it can't recognize /usr/lib/libiconv.la. Why? Because I install libtool via "mingw-get install libtoo". > The file does exist, but it is under C:\MinGW(because of using mingw-get), and my MSYS is under C:\MinGW\msys\1.0. > So if I'm kinda in troubles right now... > How can I solve this correctly? Can I re-install both minGW(+minGW-get) and MSYS to the same directory? Is it recommended? > Does MSYSGit will solve it to one directory, and could I install minGW-get in it? "DOING IT WRONG". MinGW and Msys MUST be located in different directories. Anything that does not depend on msys-1.0.dll (that is, anything you build with MinGW) should NOT go into /usr. MinGW must live in a separate directory, and is usually mounted to /mingw (but that is not required). Msys' /etc/profile will add /mingw/bin to PATH BEFORE /bin, which is why Msys will use MinGW toolchain and MinGW tools, even if you have toolchain and tools with the same names in /usr/bin. If you don't mount MinGW directory as /mingw, you'd have to edit /etc/profile. If you build something with MinGW toolchain, you should put it into /mingw by configuring with --prefix=/mingw Never ever put anything MinGW-related into /usr/lib, /usr/bin or /usr/include, these are for Msys only. You MIGHT put something in /usr/local (this is usually the default prefix), but MinGW will NOT find anything there by itself. If you do that, you'd have to pass CPPFLAGS="-I/usr/local/include" and LDFLAGS="-L/usr/local/lib" to configure/make (although configuring with --prefix=/usr/local might take care of that - but that is up to configure script, not MinGW tools). |