From: Arjen M. <arj...@de...> - 2010-06-21 10:02:44
|
Hi Rob, On 2010-06-21 11:48, Sisyphus wrote: > > Yep, that's fine. > However, I think you should find that both GCLP_HCURSOR and > GWLP_USERDATA *are* defined for 32-bit compilers (and to the same values > as their "P"-less counterparts). It's just that GCL_HCURSOR and > GWL_USERDATA are not defined for Win64. > Hm, I founded my comment on this piece of code (from c:\program files\microsoft sdks\windows\v6.0A\include\winuser.h): #ifdef _WIN64 #undef GCL_MENUNAME #undef GCL_HBRBACKGROUND #undef GCL_HCURSOR #undef GCL_HICON #undef GCL_HMODULE #undef GCL_WNDPROC #undef GCL_HICONSM #endif /* _WIN64 */ #define GCLP_MENUNAME (-8) #define GCLP_HBRBACKGROUND (-10) #define GCLP_HCURSOR (-12) #define GCLP_HICON (-14) #define GCLP_HMODULE (-16) #define GCLP_WNDPROC (-24) #define GCLP_HICONSM (-34) #endif /* !NOWINOFFSETS */ As you can see, it undefines the GCL_* macros before redefining them when _WIN64 exists. This may be peculiar to this version and to the MicroSoft Visual Studio version it comes with. The header file that comes with the GCC compiler does not undefine the GCL_* macros. That is the difference. > >> As I have no way to test this in the absence of a Windows 64 bits system >> that I can easily use, I would like to ask you to check these changes. > > Just checked out revision 11081. Builds fine using MinGW64, except for > the other issues I raised in my original post (and worked around): > Excellent. > 1) I need to tell the build process that CC=x86_64-w64-mingw32-gcc, > C++=x86_64-w64-mingw32-g++ and AR=x86_64-w64-mingw32-ar instead of the > usual gcc, g++ and ar. > I notice there's some output at the start of the cmake process that > looks very much like './configure' output, so hopefully there's a way of > passing those values along (as there is with ./configure). > > 2) libgdi32.a and libcomdlg32.a can't be found because of changes to the > directory structure in the mingw64 compiler. > > I'll try to work out how those issues can be addressed - any pointers > are welcome, as I'm not at all familiar with the cmake process, I'm > hopeless at tracking down relevant documentation, I'm not very good with > Makefiles, and I'm generally a bit dim anyway. > Hm, you have solved (or tracked down the solution to) those issues, so the dimness seems to be wearing off. I guess Windows 64 bits is a relatively new platform as far as PLplot is concerned. We are bound to run into more such issues. > Btw, by chance, I happened to notice that x17c.exe (strip chart demo) > works correctly in the svn version. Whenever I've looked at it before, > the graphs have just super-imposed over each other, resulting in quite a > mess. Now we get one chart after another - which I'm assuming is what's > intended. Nice ! > Yes, that was actually a small correction by me and great improvement to the demo (the wingcc was lying about it cleaning up the window - it said it would but did not). Regards, Arjen |