I would suggest divide and conquer next. This is a classic approach to debuggging.
First get something working in C, solely on Windows. Can you build a pure C host and pure C DLL that loads and shows your window? I note that I never had much luck cross-compiling to windows, so I would recommend, initially, building and running your C host and C DLL on windows exclusively. This will also cut down on the number of moving parts. Also, I would not use rundll32.exe to test, since it is 32 bit only and its docs say that it can only be used with DLLs that were specifically built for it: "Rundll32 can only call functions from a DLL explicitly written to be called by Rundll32." Rather build your own host/main C program that imports your DLL. The I would incrementally move towards your end goal. If you haven't realized the issue yet, then move to cross compilation without Go. If that works, then add in the Go code. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/36c9137c-b1c3-4f29-b291-6a373501ed5bn%40googlegroups.com.
