wine-devel

wine-devel@winehq.org

84463 discussions

Winelib and documentation
by steve_lustbader＠hsgmed.com 23 Jul '02

23 Jul '02

I've been having some trouble using winelib (with spec files) following the documentation on the web site. A few people in the IRC channel were under the impression that winelib had changed and the docs aren't really relevant anymore. Is the documentation going to be updated to the current status of the source? ****************************** Steve Lustbader Philips Medical Systems E-mail: steve_lustbader(a)hsgmed.com 3000 Minuteman Road, MS 0105 Voice: 978 659 3713 Andover, MA 01810

3 2

Re: Configure.in
by Gregg Mattinson 23 Jul '02

23 Jul '02

Same thing is defined on my system, so I think it is correct. LD_PATH is used to add paths infront of LD_LIBRARY_PATH for when wrc and winebuild are run. On my system, before the line you mentioned, LD_PATH is set to $wine/library:$wine/dlls. Then, it is changed to prepend itself to the environment variable LD_LIBRARY_PATH. Gregg Mattinson Co-op Developer Sun Microsystems of Canada >From: steve_lustbader(a)hsgmed.com >To: wine-devel(a)winehq.com >Subject: Configure.in >Date: Tue, 23 Jul 2002 14:20:53 -0600 > >In the configure.in that winemaker generates for me, LD_PATH gets defined as LD_PATH="LD_LIBRARY_PATH=\"$LD_PATH:\$\$LD_LIBRARY_PATH\"" It seems like it's missing a linebreak, or it's doing something very weird. Is this right? > >****************************** >Steve Lustbader > >Philips Medical Systems E-mail: steve_lustbader(a)hsgmed.com >3000 Minuteman Road, MS 0105 Voice: 978 659 3713 >Andover, MA 01810 >

1 0

Re: PATCH: [Bug 19] - font enumeration problems for aliased gdi fonts
by Huw D M Davies 23 Jul '02

23 Jul '02

On Tue, Jul 23, 2002 at 01:00:59PM -0700, Rafael Kitover wrote: > This patch fixes the "Invalid Property Value" message box that pops up > in older visual basic programs on startup when they try to call > ENUMFONTS on the default "MS Sans Serif" font for example. > > (reference: http://www.winehq.com/hypermail/wine-bugs/2002/05/0116.html) > > License: LGPL, X11 > > Changelog: > Rafael Kitover <caelum(a)debian.org> > Fix ENUMFONTS on aliased gdi fonts What's exactly the problem here? Is it lack of support of 16bit EnumFonts ? Huw.

1 0

Configure.in
by steve_lustbader＠hsgmed.com 23 Jul '02

23 Jul '02

In the configure.in that winemaker generates for me, LD_PATH gets defined as LD_PATH="LD_LIBRARY_PATH=\"$LD_PATH:\$\$LD_LIBRARY_PATH\"" It seems like it's missing a linebreak, or it's doing something very weird. Is this right? ****************************** Steve Lustbader Philips Medical Systems E-mail: steve_lustbader(a)hsgmed.com 3000 Minuteman Road, MS 0105 Voice: 978 659 3713 Andover, MA 01810

1 0

RE: wine/dlls crtdll/crtdll.spec crtdll/crtdll_mai ...
by Patrik Stridvall 23 Jul '02

23 Jul '02

> Modified files: > dlls/crtdll : crtdll.spec crtdll_main.c > dlls/msvcrt20 : msvcrt20.spec > dlls/shell32 : shell32.spec > > Log message: > Fixed broken forwards reported by Patrik Stridvall. Much better. No broken forwards reported by winapi_check any longer. However I don't think your fix was 100% correct. winapi_check now says dlls/msvcrt/string.c:52: <>: char * _strdec(char *,char *): documentation: _strdec (MSVCRT.@) wrong dlls/msvcrt/string.c:75: <>: char * _strinc(char *): documentation: _strinc (MSVCRT.@) wrong dlls/msvcrt/string.c:83: <>: unsigned int _strnextc(char *): documentation: _strnextc (MSVCRT.@) wrong dlls/msvcrt/string.c:93: <>: char * _strninc(char *,unsigned int): documentation: _strninc (MSVCRT.@) wrong dlls/msvcrt/string.c:143: <>: unsigned int _strncnt(char *,unsigned int): documentation: _strncnt (MSVCRT.@) wrong dlls/msvcrt/string.c:152: <>: char * _strspnp(char *,char *): documentation: _strspnp (MSVCRT.@) wrong The problem is not what the error messages suggest though, winapi_check is far from prefect. :-) Anyway, the real problem seems to be that the the functions you implemented in crtdll_main.c were already implemented in msvcrt. However they were not exported. Examining the msvcrt.dll on my Windows 98 computer indicates that this is correct they shouldn't be exported. crtdll.dll does exactly as Wine does though. So I guess the implementation of the functions above should only be in CRTDLL and not in MSVCRT. Will you fix it or should I?

2 1

Re: PATCH: SetParent optimization
by Ann and Jason Edmeades 23 Jul '02

23 Jul '02

> Probably SetWindowLong(GWL_HWNDPARENT) should not do a full SetParent, > but just set the window owner. Looks like this needs more testing > under Windows to find out exactly what it's supposed to do. Interestingly I took out that SetParent call as a hack to get beyond bug#825 which is exactly what VB is doing for 'modal' windows (setting GWL_HWNDPARENT) which basically means modal windows become unusable. Jason

1 0

RE: Winelib and documentation
by Andriy Palamarchuk 23 Jul '02

23 Jul '02

Steve, if you don't mind lets continue the discussion in public. --- "LUSTBADER,STEVE (Non-A-hsgAndover,ex1)" <steve_lustbader(a)hsgmed.com> wrote: > > > Is the > > > documentation going to be updated to the current > > > status of the source? > > > > Yes, but I do not know when. As far as I know > nobody > > is working on the guide right now. > > If you provide information which part of the guide > is > > outdated somebody may want to fix it. > > > > The problem I was specifically having was with spec > files and import statements - it seems like imports > don't belong in specs anymore. Yes, you are right here. Now it is done by the following definition in Makefile.in file: ... IMPORTS = advapi32 kernel32 ... As an example of using Winelib I advise you to look into Wine programs (see programs subdirectory of the Wine source tree). These programs are compiled as Winelib programs, you probably will want to do something similiar. Andriy __________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com

1 0

Problem with wineconsole
by DanteAliegri 23 Jul '02

23 Jul '02

I'd suggest the following patch as an easy way to tell that something in wineconsole is going wrong. All I was getting was that the backend had failed - no indication of why. --Dante --- user.c Tue Jul 23 09:29:23 2002 +++ newuser.c Tue Jul 23 09:29:54 2002 @@ -550,7 +550,7 @@ fc.data = data; fc.done = 0; EnumFontFamilies(PRIVATE(data)->hMemDC, NULL, get_first_font_enum, (LPARAM)&fc); - if (!fc.done) WINE_WARN("Couldn't find a decent font, aborting\n"); + if (!fc.done) WINE_ERR("Couldn't find a decent font, aborting\n"); return fc.done; }

1 0

Re: Threading on Solaris
by Gregg Mattinson 23 Jul '02

23 Jul '02

Threads on Solaris are a big issue for Sun, so I will start tackling this problem today. Thanks for telling me all the issues Francois. I have a hack-ish version implemented, and now I can create a real solution to the problem. Gregg Mattinson Co-op Developer Sun Microsystems of Canada >From: Francois Gouget <fgouget(a)codeweavers.com> >To: wine-devel(a)winehq.com >CC: Gregg Mattinson <gm138242(a)opcom-mail.canada.sun.com> >Subject: Threading on Solaris >Date: Tue, 23 Jul 2002 00:35:09 -0700 > >Hi, > > >Some time ago I did some tests of Wine on Solaris x86 and found that >there is a problem with the way we handle threads due to the differences >between the Linux and Solaris threading models. These differences are >also relevant for Solaris Sparc and probably many other Unices. > >Unfortunately I don't have time to work on it anymore so I created a bug >report in Bugzilla where I tried to dump the relevant information, >including a patch to illustrate the issues and the start of a fix. I >hope it will be useful to someone... maybe Gregg who has been doing a >lot of Solaris work recently. > >http://bugs.winehq.com/show_bug.cgi?id=904 > > >-- >Francois Gouget >fgouget(a)codeweavers.com

1 0

Re: [Q] CreateProcess for Batch files
by us＠the-edmeades.demon.co.uk 23 Jul '02

23 Jul '02

>I don't think we want to check extensions this way. We should simply >hand off all command lines we cannot execute another way to the >command interpreter (which could be made configurable so you can use >native cmd.exe if you have it). Isnt this what Windows uses the COMSPEC env var for? Surely we should (by default) set the COMSPEC env var to wcmd, and if someone wants to change it to the real cmd.exe then they can. If I remember rightly, a simple C pgm which issues system("fred.bat") fails, (cant remember what happens if you system a .exe though). This would then leave a change to the CreateProcess and varients to recognize bat pgms to launch the program defined in comspec by. Interestingly windows2000 seems to honour comspec, and .bat extensions are registered as 'batfile' (in registry) which in turn has a default handler of %1 %* which means internally it must recognize .bat extensions itself. Jason

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel