|
From: Gauthier F. <gau...@gm...> - 2011-01-07 23:51:16
|
On Fri, Jan 7, 2011 at 5:02 PM, Keith Marshall <kei...@us...> wrote: > > On 7 January 2011 14:29, Greg Chicares wrote: > > On 2011-01-07 12:00Z, Gauthier Fleutot wrote: > >> ... > >> Apparently, I got two definitions and declarations of the function, > >> one in mingw and one in msys. Both pathes are in my PATH envvar. > > > > It looks like more than one copy of the compiler has been installed. > > It's probably best to remove all of this and perform a fresh install. > > It looks like the OP has installed both the MinGW compiler, (which is > the one he should be using for day-to-day work), and the special version > which is intended for building MSYS itself, (and for no other purpose). > If the OP doesn't understand this distinction, then he really shouldn't > have installed the MSYS special compiler in the first place; a fresh > install, *without* the MSYS development tools, (as opposed to the MinGW > development tools of a normal user's MSYS installation), may well be his > best practicable remedy, to avoid further confusion. You are correct, my installation was strange, thanks for pointing it out. I have now reinstalled from scratch, without the MSYS special compiler. > in the case of MoveWindow(), > that is provided by the system's own user32.dll. In the 'lib' directory > there should be a libuser32.a *import* library, which simply redirects > the function call to the appropriate system DLL entry point. I understand now that MinGW's role in MoveWindow() is only to link to the system's DLL. Still, MoveWindow() freezes on me, and I don't know where things go wrong. I don't know where to look either. How can I check if libuser32.a is doing its job as intended, if my user32.dll is working fine, and anything in between? Could someone perhaps provide a basic sample source code using MoveWindow(),so I can check that my problem is not with OpenCV? |