July 2010 - Wine-Devel - list.winehq.org

Re: (Resent) Documentation - Reference to MSDN?

by Jeff Zaroyko

On Fri, Jul 2, 2010 at 7:35 AM, Octavian Voicu <octavian.voicu(a)gmail.com> wrote: > > PS: there are other resources except MSDN; for example, osronline.com > has very good documentation for windows driver developers, including > some undocumented APIs. > I don't know if this is worth mentioning or not, Geoff Chappell maintains a website with some in depth information covering Windows internals, granted the methods used to discover the information may not be in line with what a Wine contributor is allowed to do, but in the same spirit of quality information he has proposed an initiative "producing an Opened Windows Library (OWL) as an alternative to Microsoft’s MSDN Library". Maybe this could be what you're looking for. http://geoffchappell.com/viewer.htm?doc=index.htm http://www.soared.org/ http://www.soared.org/plan/index.htm http://www.soared.org/plan/faq.htm PS. The idea of publishing this information to a wiki seems a little ad-hoc, wouldn't it be better to put things under a dvcs (like git) and then publish based on that?

July 1, 2010

Changing sizes of templates in comdlg32

by Gustavo

I've found the following warning the the file comdlg32: /* * WARNING: DO NOT CHANGE THE SIZE OF THE STANDARD DIALOG TEMPLATES. */ Does that mean that I can't correct the size of the buttons or strings that are wrong in the Portuguese template file? Or is that only a warning for the English file? The "Find" and "Replace" dialogs are specially ugly in Portuguese, I would appreciate to be able to change that.

July 1, 2010

Re: (Resent) Documentation - Reference to MSDN?

by Octavian Voicu

On Thu, Jul 1, 2010 at 8:06 PM, Erich Hoover <ehoover(a)mines.edu> wrote: > 3) Provide unchanging URLs that can legitimately be used in the source > code without fear of them changing every week (or being lost forever > in the case of some older functions) > 4) Document the ever-growing list of unexpected behaviors that MSDN > will never tell you about Why would we want to help Micro$oft with that? How did they ever contribute to the open source community to deserve that? As I see it, Wine's primary goal is to aid in the migration from Windows, a closed platform, to an open platform like Linux. There is enough to do already (kernel, system dlls, many many libraries, installer, directx, command line tools, various programs and tools, testing infrastructure, translations, etc), if we spread ourselves too thin we won't get anywhere with anything. Imho there are very few cases in which better documentation would benefit our cause, but I'm pretty sure that devoting that time to writing wine code instead of winapi documentation would have a much greater impact. Octavian PS: there are other resources except MSDN; for example, osronline.com has very good documentation for windows driver developers, including some undocumented APIs.

July 1, 2010

Re: Creating tests with additional binary modules

by André Hentschel

Am 01.07.2010 21:55, schrieb Alexandre Julliard: > None of that, of course. The resources are built at compile time, at run > time you create a PE header and copy the needed resource data. You may > even be able to use UpdateResource to make things easier. Do we have existing tests creating PE header? -- Best Regards, André Hentschel

July 1, 2010

Re: Creating tests with additional binary modules

by Mariusz Pluciński

W dniu 1 lipca 2010 21:55 użytkownik Alexandre Julliard <julliard(a)winehq.org> napisał: > Mariusz Pluciński <vshader(a)gmail.com> writes: > >> W dniu 1 lipca 2010 21:27 użytkownik Alexandre Julliard >> <julliard(a)winehq.org> napisał: >>> You can't do that in the Makefile, you need to generate the files at run >>> time. >> >> Huh, so while executing the test, I need to run at least resources >> compiler and linker, right? It looks really more complicated way, and >> I admit that I completely don't know how to do it. Which tools >> should I use? Can I use Mingw? Can I assume that these tools are >> installed on system where test is running? Or maybe I should use >> some tools provided by wine? And, of course, how to make it working >> on Windows? > > None of that, of course. The resources are built at compile time, at run > time you create a PE header and copy the needed resource data. You may > even be able to use UpdateResource to make things easier. > All right, now it's more clear for me. I'm not so familiar with working on resources, and I didn't know there's API call which can modify resources in existing binary. I'll try to make it this way, thanks.

July 1, 2010

Re: Creating tests with additional binary modules

by Alexandre Julliard

Mariusz Pluciński <vshader(a)gmail.com> writes: > W dniu 1 lipca 2010 21:27 użytkownik Alexandre Julliard > <julliard(a)winehq.org> napisał: >> You can't do that in the Makefile, you need to generate the files at run >> time. > > Huh, so while executing the test, I need to run at least resources > compiler and linker, right? It looks really more complicated way, and > I admit that I completely don't know how to do it. Which tools > should I use? Can I use Mingw? Can I assume that these tools are > installed on system where test is running? Or maybe I should use > some tools provided by wine? And, of course, how to make it working > on Windows? None of that, of course. The resources are built at compile time, at run time you create a PE header and copy the needed resource data. You may even be able to use UpdateResource to make things easier. -- Alexandre Julliard julliard(a)winehq.org

July 1, 2010

Re: Creating tests with additional binary modules

by Mariusz Pluciński

W dniu 1 lipca 2010 21:27 użytkownik Alexandre Julliard <julliard(a)winehq.org> napisał: > You can't do that in the Makefile, you need to generate the files at run > time. Huh, so while executing the test, I need to run at least resources compiler and linker, right? It looks really more complicated way, and I admit that I completely don't know how to do it. Which tools should I use? Can I use Mingw? Can I assume that these tools are installed on system where test is running? Or maybe I should use some tools provided by wine? And, of course, how to make it working on Windows?

July 1, 2010

Re: Creating tests with additional binary modules

by Alexandre Julliard

Mariusz Pluciński <vshader(a)gmail.com> writes: > That's true on Wine, but I also want to make my tests runnable > under Windows, so in this case I need to create native PE modules. > > And as I said, my main problem is that I don't know how to > write rules in Makefile.in to build what I need. You can't do that in the Makefile, you need to generate the files at run time. -- Alexandre Julliard julliard(a)winehq.org

July 1, 2010

Re: [PATCH][kernel32.dll] quick and dirty implementation of GetVolumePathNamesForVolumeNameA (try 2)

by James Mckenzie

Tuomo Mattila <tuomom(a)ee.oulu.fi> wrote: Why not just do the check and then pass it as a Wide to the 'W' function? Simpler and less code to maintain/update? >+ >+ >+ FIXME("(%s, %p, %d, %p), stub!\n", debugstr_a(volumename), volumepathname, buflen, returnlen); If this is not a full implementation, you need to state so, otherwise this goes.... >+ >+ if (volumename == 0 || volumepathname == 0 || returnlen == 0) >+ { >+ SetLastError(RPC_X_NULL_REF_POINTER); >+ return FALSE; >+ } At this point you should convert to Wide/UNICODE and pass to the W function. Pass the return from the W call back to the caller. >+ >+ return TRUE; >+} >+ >+/*********************************************************************** > * GetVolumePathNamesForVolumeNameW (KERNEL32.@) > */ > BOOL WINAPI GetVolumePathNamesForVolumeNameW(LPCWSTR volumename, LPWSTR volumepathname, DWORD buflen, PDWORD returnlen) >-- >1.7.1 > > >

July 1, 2010

Re: Creating tests with additional binary modules

by Mariusz Pluciński

> Do they really need to be separate binaries? Unfortunately yes. To the function I pass only the path to binary, and it unpacks data internally, so I cannot select actual resource. One binary can contain multiple GDFs only if they are translations of the same file in few languages. And I don't know is there any way to force library to load specified language version (and it is, in my opinion, not "clean" way of testing). > And no, it doesn't have to be a pure win-pe binary. Wine can load > and parse resources just from winelib (dll.so/exe.so) binaries. That's true on Wine, but I also want to make my tests runnable under Windows, so in this case I need to create native PE modules. And as I said, my main problem is that I don't know how to write rules in Makefile.in to build what I need.

July 1, 2010