How to tell winemaker and winebuild what I want to tell it

[Bill Medland]

Anyone able to tell me what I am doing wrong here before I spend days trying
to figure it out?

My winelib wrapper wants to call MultiByteToWideChar and DOSFS_GetFullName.
As far as I am aware they are available from ntdll.dll (ntdll.dll.so)

So I want to to get the build to "link" to ntdll.dll

I thought it should simply require "-intdll" in the argument to winemaker,
but during the link I still get complaints about not finding those two
functions.

What am I doing wrong?

Bill

p.s. Thanks to Francois for the fixes to Winemaker

[Alexandre Julliard]

"Bill Medland" <billmedland(a)look.ca> writes:
> My winelib wrapper wants to call MultiByteToWideChar and DOSFS_GetFullName.
> As far as I am aware they are available from ntdll.dll (ntdll.dll.so)

MultiByteToWideChar is exported from kernel32, not ntdll.
DOSFS_GetFullName is not exported and you can't use it from a winelib
app; you may be able to use wine_get_unix_file_name() instead.

-- 
Alexandre Julliard
julliard(a)winehq.com

[Bill Medland]

----- Original Message -----
From: "Alexandre Julliard" <julliard(a)winehq.com>
To: "Bill Medland" <billmedland(a)look.ca>
Cc: "wine-devel" <wine-devel(a)winehq.org>
Sent: Thursday, September 26, 2002 6:20 PM
Subject: Re: How to tell winemaker and winebuild what I want to tell it
> "Bill Medland" <billmedland(a)look.ca> writes:
> > My winelib wrapper wants to call MultiByteToWideChar and
> > DOSFS_GetFullName.
> > As far as I am aware they are available from ntdll.dll (ntdll.dll.so)
>
> MultiByteToWideChar is exported from kernel32, not ntdll.
> DOSFS_GetFullName is not exported and you can't use it from a winelib
> app; you may be able to use wine_get_unix_file_name() instead.

So I guess I am doing something dangerous in adding -lntdll.dll to the link
(which does the trick very nicely).
> --
> Alexandre Julliard
> julliard(a)winehq.com

[Alexandre Julliard]

"Bill Medland" <billmedland(a)look.ca> writes:
> So I guess I am doing something dangerous in adding -lntdll.dll to the link
> (which does the trick very nicely).

Yes, this is asking for trouble. It happens to work now but this will
likely change in the near future.

-- 
Alexandre Julliard
julliard(a)winehq.com

[Bill Medland]

----- Original Message -----
From: "Alexandre Julliard" <julliard(a)winehq.com>
To: "Bill Medland" <billmedland(a)look.ca>
Cc: "wine-devel" <wine-devel(a)winehq.org>
Sent: Friday, September 27, 2002 9:56 AM
Subject: Re: How to tell winemaker and winebuild what I want to tell it
> "Bill Medland" <billmedland(a)look.ca> writes:
> > So I guess I am doing something dangerous in adding -lntdll.dll to the
> > link
> > (which does the trick very nicely).
>
> Yes, this is asking for trouble. It happens to work now but this will
> likely change in the near future.

Agreed.  (I suddenly realised it only works because there is the
libntdll.dll.so link and I don't even know if that is just lying around from
the past).

And of course wine_get_unix_file_name obviates the need for the
MultiByteToWideChar.

A propos.  Why is wine_get_unix_file_name nice and exposed (e.g. it is in
winbase.h) yet the wine_dlopen etc aren't?
Are there any other useful wine_* functions that are particularly useful and
ought to be mentioned in the winelib manual?

Bill

[Alexandre Julliard]

"Bill Medland" <billmedland(a)look.ca> writes:
> A propos.  Why is wine_get_unix_file_name nice and exposed (e.g. it is in
> winbase.h) yet the wine_dlopen etc aren't?

wine_dlopen etc. are in libwine, they are not exported APIs but normal
Unix functions. So they are declared in include/wine/library.h.

-- 
Alexandre Julliard
julliard(a)winehq.com