- Wine-Devel - list.winehq.org

Re: WineLib and DLLs
by Jon Griffiths Sept. 12, 2002

Sept. 12, 2002

Hi, >I'm writing a WineLib DLL that makes calls in my own Windows DLLs >(not Wine's DLLs). I have the header files for those DLLs, and the >Windows binaries for them. How do I link to them? Do I need to wrap >them in spec files? What do I need to put into my Makefile.in? look at tools/winedump. In spec mode it will generate everything you need to link to this dll - a makefile and dummy implementation, spec file and a script to insert it into your existing WINE tree (to link with). The README gives instructions for exactly this case (and some other more advanced ones). Cheers, Jon ===== "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live jon_p_griffiths(a)yahoo.com __________________________________________________ Do you Yahoo!? Yahoo! News - Today's headlines http://news.yahoo.com

1 0

Re: SHLWAPI merging #4
by Alexandre Julliard Sept. 12, 2002

Sept. 12, 2002

Jon <jon_p_griffiths(a)yahoo.com> writes: > Does anyone object to my moving SHLWAPI_1 & 2 into url.c and moving out the > definitions from ordinal.h in there as well? > > I want to tidy this up because at some point in the not too distant future the > ordinal code will get a lot bigger. So it makes sense to me to implement > ordinals that are related in the same files (like the MIME ord. functions in > url.c), and to split out other ord. groups (gdi/windows/com/ie/perfmon etc) > into their own files as well. OK? Actually there's no reason at all to group ordinal functions together, the fact that they are exported by ordinal is just a detail that doesn't matter for understanding what's going on. It's much better to group ordinal string functions with other string functions, ordinal URL functions with other URL stuff etc. -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: WineLib and DLLs
by steve.lustbader＠philips.com Sept. 12, 2002

Sept. 12, 2002

I also have the .lib and .pdb files for the DLLs, if that helps. I'm writing a WineLib DLL that makes calls in my own Windows DLLs (not Wine's DLLs). I have the header files for those DLLs, and the Windows binaries for them. How do I link to them? Do I need to wrap them in spec files? What do I need to put into my Makefile.in? There are instructions in the WineLib docs about binary DLLs, but they seem to be talking about pretending a Linux library is a DLL, which is not what I want to do. -Steve

1 0

WineLib and DLLs
by steve.lustbader＠philips.com Sept. 12, 2002

Sept. 12, 2002

I'm writing a WineLib DLL that makes calls in my own Windows DLLs (not Wine's DLLs). I have the header files for those DLLs, and the Windows binaries for them. How do I link to them? Do I need to wrap them in spec files? What do I need to put into my Makefile.in? There are instructions in the WineLib docs about binary DLLs, but they seem to be talking about pretending a Linux library is a DLL, which is not what I want to do. -Steve

1 0

Re: Unicode functions
by steve.lustbader＠philips.com Sept. 12, 2002

Sept. 12, 2002

Thanks, that worked! Do you think you could update the Unicode section in the WineLib user's guide (section 2.2)? It doesn't even mention WINE_UNICODE_NATIVE (not like the rest of the guide is that current, but every little bit helps for new developers). -Steve On Thu, 12 Sep 2002 steve.lustbader(a)philips.com wrote: > I think there is issue with _T(x). I have this line in my Windows app > that I'm compiling with WineLib (I'm using -fshort-wchar): > > const TCHAR *Name() const { return _T("my_name"); }; > > The compiler gives me an error of: > > cannot convert `const __wchar_t *' to `const > TCHAR *' in return If you are using --fshort-wchar you should also use WINE_UNICODE_NATIVE so that WCHAR gets defined to wchar_t. From winnt.h: #ifdef WINE_UNICODE_NATIVE typedef wchar_t WCHAR, *PWCHAR; #else typedef unsigned short WCHAR, *PWCHAR; #endif and further down: /* Define WINE_UNICODE_NATIVE if: * - your compiler provides a 16bit wchar_t type, e.g. gcc >= 2.96 with * -fshort-wchar option * - or if you decide to use the native 32bit Unix wchar_t type. Be aware * though that the Wine APIs only support 16bit WCHAR characters for * binary compatibility reasons. * - or define nothing at all if you don't use Unicode, and blissfully * ignore the issue :-) */ Does that help? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ May your Tongue stick to the Roof of your Mouth with the Force of a Thousand Caramels

1 0

shlwapi failes to build on windows
by Steven Edwards Sept. 12, 2002

Sept. 12, 2002

shlwapi.exp(.edata+0x34):fake: undefined reference to `AssocCreate(a)12' C:\mingw\bin\dllwrap.exe: C:\mingw\bin\gcc exited with status 1 make: *** [shlwapi.dll] Error 1 The def should contain AssocCreate(a)24 I do not know what is needed in the *.spec though Thanks Steven __________________________________________________ Do you Yahoo!? Yahoo! News - Today's headlines http://news.yahoo.com

1 0

Re: Unicode functions
by steve.lustbader＠philips.com Sept. 12, 2002

Sept. 12, 2002

I think there is issue with _T(x). I have this line in my Windows app that I'm compiling with WineLib (I'm using -fshort-wchar): const TCHAR *Name() const { return _T("my_name"); }; The compiler gives me an error of: cannot convert `const __wchar_t *' to `const TCHAR *' in return It similarly complains about converting _T("foo") to a const WCHAR *. Both of these things work under Windows. Changing the definition of _T(x) from L##x to (TCHAR *) L##x avoids these problems, but then something like _T("foo") _T("bar") doesn't concatenate those strings like it does in Windows. -Steve --- steve.lustbader(a)philips.com wrote: > Are _tprintf and it's related functions (_ftprintf, > _stprintf) implemented? I found a tchar.h in the > source tree that defines these functions, but it > wasn't in my /usr/local/include/wine directory. I'm fixing the build process to install the header. For now you can copy it manually to the /usr/local/include/wine directory. Actually _ftprintf and _stprintf are not functions, but macros which are mapped in tchar.h to corresponding ASCII or Unicode function. The underlying functions should be implemented. > These functions aren't important for wine, since > they're simply defined as the ASCII or Unicode > version, but they are important for WineLib. > > What is the overall status of using Unicode with > WineLib? What needs to be defined and what headers > need to be included to get the functionality from > Windows' tchar.h (_T(), TCHAR, the above functions, > etc)? Unicode is supported relatively well in Wine. Please report if you have any issues with it. Andriy __________________________________________________ Do you Yahoo!? Yahoo! News - Today's headlines http://news.yahoo.com

3 2

RE: wstr vs ptr in spec files
by Patrik Stridvall Sept. 12, 2002

Sept. 12, 2002

> When should I use wstr and when ptr for wide strings > in the spec files functions specification? > > Looking at existing files I see that LPCWSTR type is > usually mapped to wstr, It should almost always map to wstr. > but LPWSTR is sometimes mapped > to ptr, sometimes to wstr. As the general rule it depends on whether the parameter is IN, OUT or IN/OUT. IN: wstr OUT: ptr IN/OUT: wstr PS. It is for debug messages. If the parameter is OUT it might not be initialized as thus it should not be printed as a string (in this case a wide string).

1 0

Unicode functions
by steve.lustbader＠philips.com Sept. 12, 2002

Sept. 12, 2002

Are _tprintf and it's related functions (_ftprintf, _stprintf) implemented? I found a tchar.h in the source tree that defines these functions, but it wasn't in my /usr/local/include/wine directory. These functions aren't important for wine, since they're simply defined as the ASCII or Unicode version, but they are important for WineLib. What is the overall status of using Unicode with WineLib? What needs to be defined and what headers need to be included to get the functionality from Windows' tchar.h (_T(), TCHAR, the above functions, etc)? -Steve

3 2

wstr vs ptr in spec files
by Andriy Palamarchuk Sept. 12, 2002

Sept. 12, 2002

When should I use wstr and when ptr for wide strings in the spec files functions specification? Looking at existing files I see that LPCWSTR type is usually mapped to wstr, but LPWSTR is sometimes mapped to ptr, sometimes to wstr. Andriy Boston, MA, USA As an employee of an oil company, let me assure you that nothing, and I mean NOTHING scares a big company more than a noisy, smelly, obnoxious, disaffected pressure group. Now go away and chain yourself to someone important's front door. TheRegister. Unknown __________________________________________________ Do you Yahoo!? Yahoo! News - Today's headlines http://news.yahoo.com

1 0