wine-devel

wine-devel@winehq.org

9 participants
84457 discussions

I: Wine and SQl server.
by Carlo Pelini 24 Apr '03

24 Apr '03

> -----Messaggio originale----- > Da: Carlo Pelini > Inviato: giovedì 24 aprile 2003 17.42 > A: 'wine-users(a)Winehq.com' > Oggetto: Wine and SQl server. > > Hy. I am a computer science student, and I am studing wine for my degree > thesis. > I have succeded to run VisualFoxPro on wine and by VisualFoxPro i have > succeded to utilize the unixODBC and the ODBC windows. With the unixODBC I > have succeded to open a connession with a database SQL server, to execute > a interrogation and to visualize the result. > For to can to do there, I dont'have utilized directly the driver SQL > server, but I have utilzed easysoft ODBC-ODBC bridge > (http://www.easysoft.com/products/oob/main.phtml), a ODBCF driver, which > do precisely from bridge between the ODBC client and the ODBC server, and > allow the connession with a database SQL server. > Thank at there proceeding, I have succeded to run AD HOC REVOLUTION, a > managerial software, even if is slow. > Bye.

1 0

Server Crash
by Jeremy Newman 24 Apr '03

24 Apr '03

It's time for the annual server crash kids! Whee! Our server melted last night at about 3am or so after 2 days of solid high traffic (the load average was up over 100). I managed to get it up and running with some WD-40, Duct Tape, and some bubble gum. I can't guarantee uptime right now. I AM, however, scrambling to beef it up to handle the load. I apologize in advance for any further downtime. As you can imagine, with all this good press, I don't want the server do be down any longer than a few nanoseconds. If anyone has a quad processor Xeon they are not using, feel free to send it my way. :-D -- Jeremy Newman <jnewman(a)codeweavers.com> CodeWeavers, Inc.

1 0

WineHQ's CVS server performance..
by Lionel Ulmer 23 Apr '03

23 Apr '03

Hi all, Am I the only to find the current CVS performance abyssmal ? About 5 minutes for a CVS update and 10 for a CVS diff is not what I usually have on my connection... Let's hope it's Alexandre merging all the Crossover Office 2.0 patches <g>. Lionel -- Lionel Ulmer - http://www.bbrox.org/

3 2

CVS Character set (was: lostwages/templates/en documentation.template)
by Joerg Mayer 23 Apr '03

23 Apr '03

I'm noticing that during the last few weeks several mails have been sent to the cvs list that use 8-bit characters but do not specifiy an encoding in the mail header. Would it be possible to either add one (depends on whether cvs does recognize the encoding type) or remove those extra characters? On Tue, Apr 22, 2003 at 01:28:01PM -0500, Jeremy Newman wrote: > Log message: > ChangeLog > Â Â Â Dimitrie O. Paun <dpaun(a)rogers.com> > Â Â Â Remove references to no longer existing document. > > Patch: http://cvs.winehq.com/patch.py?id=7945 Thanks Jörg -- Joerg Mayer <jmayer(a)loplof.de> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.

1 0

RE: FoxPro & Wine :)
by Patrik Stridvall 23 Apr '03

23 Apr '03

> On Wed, 23 Apr 2003, Patrik Stridvall wrote: > > > While, I suppose, you can have a license the regulates this to, even > > if the LGPL doesn't, the problem is the doctrine of first sale means > > anybody that it can be distributed to can resell (or give) that copy > > to anybody that can't be distributed directly to. > > And that is in no contradiction with the (L)GPL, as it does not > restrict to whom we can redistribute, but rather under what > conditions a derived work can be distributed. But that is exactly what I said above. Should I interpret it as you agree? But please note that the last step meantioned above is not distribution, it is sale (or gift) on an invidual copy allowed by first sale. And as I said earlier, it makes the conditions for redistribution is rather meaningless, since anybody regardless or willingless or abillity to follow the redistribution conditional can indirectly for all intent and purposed have distributed to anybody your work, while seperately distributing anything that uses, modififies, adapts etc your work for his purposes on the end users computer. The situation for the Microsoft Visual FoxPro (MVFP) runtime is almost identical since you analagous to above can for all intent and purpose have it distributed seperately. Summary: Microsoft released the MVFP runtime for all intent an purpose for free since they thought that charging for it would be bad for their purposes. Some people release some work under the LGPL because they thought charging for it would be bad for their purposes... Nobody can both have the cake and eat it. Microsoft can't, I can't, you can't... And futher more, again, Copyright law is designed that way on purpose, not by accident.

1 0

odd message
by Robert Lunnon 23 Apr '03

23 Apr '03

I am debugging a shareware game my kids often play called little fighter 2 (It deadlocks after creating the third thread) But before I get to the deadloack I noticed I get the following two messages from wine, err:module:BUILTIN_LoadModule loaded .so but dll wineaudioio.drv still not found err:module:BUILTIN_LoadModule loaded .so but dll joystick.drv still not found from what I can see wine is loading the two shared libraries ok and __wine_dll_register gets properly called EG Breakpoint 2, __wine_dll_register (header=0xdcb82480, filename=0xdcb721f6 "wineaudioio.drv") at loader.c:327 Yet find_dll_descr( dllname ) in builtin.c fails to find the name ?? Any hints would be appreciated

1 1

Re: oleaut32 patch
by Alexandre Julliard 23 Apr '03

23 Apr '03

Ove Kaaven <ovek(a)arcticnet.no> writes: > The oaidl_p.c is almost unmodified MIDL output generated from Wine's > oaidl.idl (I only had to add an #undef __WINE__ at the top to get all > the Winelib definitions, perhaps this isn't needed under Wine anymore), > so it shouldn't be hard to maintain, and Alexandre once said MIDL output > is acceptable as a stopgap solution. I don't know if proper > InstallShield repaint support calls for stopgaps, though. One problem is that this code causes hundreds of warnings, and I don't think that's acceptable (it also fails to link but that could be fixed by adding a few stubs). We could fix the warnings manually but that will cause obvious maintenance problems. How far are we from being able to generate that with widl? -- Alexandre Julliard julliard(a)winehq.com

3 3

Wintab32 dll devlopment
by Robert North 23 Apr '03

23 Apr '03

I have just posted a status update on my wintab32 development to the following wine bug. http://bugs.winehq.com/show_bug.cgi?id=1160 And following on from that update there are a number of questions I need answered to guide my further development: 1. Cross over office and tablets. I heard somewhere that Crossover office had a tablet implementation. Does anyone know about this, and who to contact to find out more? If they've got an implementation of wintab, I wonder if it's worth continuing the development. 2. When to post patches I could start producing patches quite soon. For instance, I could post patches when the WTInfo function is working. Or, I could wait till the whole system is working fully with at least one app? 3. Size of the patches. Is it better to break patches into small (valid compile, but non-functioning) chunks, or to release large functioning patches? 4. Config files Wintab will need some config data. I assume the best place to put this is in the ~/.wine/config file, within a registry key named "wintab"? 5. Development notes. I have some notes on the design that other developers will probably find useful. Where in the wine project should they go? There seems to be no place for rough notes. 6. x11drv integration. Currently the code is implemented to connect to X11 in a similar way to directX. No additional code is placed in the x11drv dll. This X11 connection should be discarded. To this end I have a number of functions that I'd like to place in x11drv dll. The question is: Should I put them into x11drv before releasing any patches, or maintain the directX style connection in the initial wine patches? 7. Cross-platform abilities Is there any need to think about allowing alternatives to XInput to plug into the wintab dll? Yeah, I know that's a lot of questions, But I hope you guys can give me some guidance. Bye -Rob.

4 4

Re: Winelib CoolPlayer port
by Dimitrie O. Paun 23 Apr '03

23 Apr '03

On April 22, 2003 04:17 pm, Vincent Béron wrote: > Next is the actual Winelib stuff, which is very small. Just a few lines indeed! > The first part is an MFC header (thankfully, nothing else seems to be > needed from MFC). This is the: --- CoolPlayerCVS-20030421-2130-orig/afxres.h 1969-12-31 19:00:00.000000000 -0500 +++ CoolPlayerCVS-20030421-2130/afxres.h 2003-04-21 21:51:07.000000000 -0400 @@ -0,0 +1 @@ +#include "winres.h" right? > The second part is the only problematic thing. The current div > implementation works fine for binary compatibility on i386, but doesn't > work well for source level compatibility on the same platform. I would prefer if we fix this one in Wine, so we don't have to submit this part for inclusion in the CoolPlayer code. This would be _our_ benefit for the port, no? :) -- Dimi.

1 0

Re: Fix trackbar size
by Dimitrie O. Paun 23 Apr '03

23 Apr '03

On April 22, 2003 05:55 pm, Maxime Bellengé wrote: > + * Copyright 2003 Maxime Belleng�<maxime.bellenge(a)laposte.net> > * > * This library is free software; you can redistribute it and/or > * modify it under the terms of the GNU Lesser General Public > @@ -231,13 +232,13 @@ > channel->top = lpRect.top + offsetedge; > channel->bottom = lpRect.bottom - offsetedge; > channel->left = lpRect.left + offsetthumb; > - if (dwStyle & (TBS_BOTH | TBS_LEFT)) channel->left += 8; > + if (dwStyle & (TBS_BOTH | TBS_LEFT)) channel->left += > (lpRect.right-lpRect.left-offsetthumb-cyChannel)/2; Unfortunately, the patch seems to be wrapped, and your name did not show up properly in the copyright notice. -- Dimi.

1 0

Re: Fix Maskedit from Delphi - part 2 - Resend as attach to fix formatting
by Alexandre Julliard 23 Apr '03

23 Apr '03

Brad Campbell <brad(a)seme.com.au> writes: > EM_REPLACESTR was not respecting buffer_limit set > by EM_SETLIMITTEXT. Shouldn't the EDIT_MakeFit() call a few lines above already take care of that? Why doesn't it work? -- Alexandre Julliard julliard(a)winehq.com

2 1

RE: FoxPro & Wine :)
by Patrik Stridvall 22 Apr '03

22 Apr '03

> On Tue, 22 Apr 2003, Patrik Stridvall wrote: > > > EULAs tries to restrict, yes. However a copyright license > does as well, > > if it, like most copyleft licenses, tries to take back the rights > > you have already given up by allowing redistribution of the work > > in the first place. > > This is the source of the confusion. I don't take back anything, as > I don't allow limitless redistribution. Since you allow everybody that wants the work to legally get it for free, that is just meaningless game withs words. Even if not everybody can (re)distribute it, enough can to make it for all intent and purpose a meaningless distiction. See below. > I allow redistribution only > under certain condition. It's conditional: > A => B > You seem to think that one can not use conditionals. This is obviously > false. "You can do B IF condition A holds" is a very reasonable > statement. It's basic logic, no cake and no eating involved. [You don't really expect me to have missed something as trivial as that, do you?] The problem is that you with the LGPL only have conditionals on who can (re)distribute the work, but no conditional on whom it can be (re)distributed to. While, I suppose, you can have a license the regulates this to, even if the LGPL doesn't, the problem is the doctrine of first sale means anybody that it can be distributed to can resell (or give) that copy to anybody that can't be distributed directly to. Futhermore I would argue that first sale doctrine, for all intent and purpose, means that you as the copyright holder, can't regulate who ultimately a copy of your work, ends up with. So any such clause would be null and void, so no trickery would be needed. Note that copyright is designed that way on purpose, not as a freak accident. So now we are back to: 1. You can give your work away for free 2. You can sell your work for a fee But you can't control whom ultimately recieves and uses your work. So again: "You can't both have the cake and eat it"

3 2

RE: FoxPro & Wine :)
by Patrik Stridvall 22 Apr '03

22 Apr '03

> On Tue, 22 Apr 2003, Patrik Stridvall wrote: > > > Very, very simplified. You have basicly have two choices: > > 1. Distribute your work (or part of it) for free > > 2. Distribute your work (or part of it) for a fee. > > Says who? Says close to every business who uses copyright. Open sourse is not that large yet, you know. > Why would you think price is *the* fundamental feature? Because in the end there is really nothing else. If the work is useful to some extent, somebody will profit from directly or indirectly. Hopefully the author will as well... Futhermore, since if we are to have things like first sale, which we have, you really can't avoid that somebody converts each copy you have allowed the distribution of, to money. (Except by releasing more copies which will at least in theory drive the price to zero.) So unless you convert each copy you allow to distribute to money somebody else will. Note however this is not nessarily negative for you. Indirectly you might get more back that would have gotten through direct sale. > Copyright law gives you rights (by restricting other's rights) > so that you could use them, if you so desire, to get some money > for your work. Copyleft just says you give up some of your rights, > EULA restricts. Which is fine, but within limits -- it's much > harder (legally) to take from people than to give. EULAs tries to restrict, yes. However a copyright license does as well, if it, like most copyleft licenses, tries to take back the rights you have already given up by allowing redistribution of the work in the first place. That is what I mean by "trying to both have the cake and eat it". You have voluntary "eaten the cake" by allowing redistribution of the work and now you want it back... > As I said, why would we want to give the manufacturer of a TV set > the right to tell me what programs I'm allowed to watch on my TV? > Or what brand of gas to put in my car. Or what brand of detergent > in my washing machine? Agreed. However, your argument supports my position concerning LGPL, more than yours. > Having generally accepted interfaces (steering wheel, pedals, and > stick for a car, gas of certain octane, etc) is good because it > allows for multiple implementations == competition. But this works > as long as you can't restrict what *implementations* you're allowed > to use. Exactly, but again, it support my position more than yours. > I don't know my histroy right, but I believe this sort of > restrictions (among other things) allowed Rockefeller to build his > Standard Oil monopolistic empire, and is now illegal. IIRC the Standard Oil problem, was more a refusal to do business at all unless you cooperated more than anything else. Not really revelevent to this discussing. In the case above you have already done business by allowing redistribution ("eaten the cake") and later through legal wrangling wants to "have it" back.

2 1

Re: rpc exception
by Robert Shearman 22 Apr '03

22 Apr '03

> I see that Greg's exception stuff is not in Wine yet. Until that's > accepted, this'll have to do. [snip] This is just an idea, but would something like this work (obviously without Intel syntax): #define RpcExcept(expr) \ VOID * FuncPtr = GETEIP; \ if (__wine_in_exception_filter()) \ { \ int retval; \ switch( expr ) \ { \ case -1: \ retval = -1; \ break; \ case 0: \ retval = 0; \ break; \ case 1: \ retval = 1; \ break; \ } \ __asm \ { \ mov eax,retval \ ret 4 \ }; \ } \ __EXCEPT((__WINE_FILTER)FuncPtr) Rob

1 0

another wine apps database
by Dan Kegel 22 Apr '03

22 Apr '03

Anyone seen this one yet? http://thetechnozone.com/pcbuyersguide/software/system/TheWineList.html It seems good enough that perhaps there should be a link to it from http://www.winehq.com/?page=supported_applications We might want to nudge the author into disclosing the version number of the Wine he was using, so non-Knoppix users can compare versions. - Dan p.s. Here's its lead-in text: "The WINE List By Graeme Bennett Posted Aug. 6, 2002; updated Mar. 26, 2003 Introduction Wine (which, its authors say, stands for 'Wine is not an emulator') is a Windows-compatible application launching environment for Linux and several other non-Microsoft other operating systems in which users can run many programs designed for Windows. Since not every Windows program runs correctly under Wine, and many of the programs I tested successfully were not listed on the other Wine compatibility lists I found, I've put together this list of programs that work (or at least seem to work -- I didn't test every function of every program!) more or less as they do under Windows. For these tests, I used the Wine version built into Knoppix versions 3.1 and 3.2. Knoppix is a free Debian-based Linux distribution that requires no installation on or changes to your hard drive. It boots and runs its filesystem directly from a CD. Additionally, it write-protects your Windows hard drive(s) by default, making it an exceptionally safe way to test Wine and/or Linux. Zero Config Wine All programs tested were previously installed and no special setup, configuration or manual file copying under Wine was used. In other words, any program listed below works "as is." ..." -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

2 1

RE: FoxPro & Wine :)
by Patrik Stridvall 22 Apr '03

22 Apr '03

> > > And the question is: is this enforceable? > > > > And the answer is: if it isn't, neither is the (L)GPL. Why > would MS not > > be able to place restrictions on distribution of their own > copyrighted code? > > > > Not in the case of Microsoft. This should fall under the > sherman Anti-Trust Act. Probably true, but I would hate to use that argument in court, unless as the very last line of defence. > If I buy a copy > of MS Visual Studio and I have to redistribute files to > Windows 9x, NT, 2K, XP, Etc then I should > be able to also redistribute the same files to Linux or ReactOS. Also note that if you for example put it on a web site, you are not really redistributing to a special OS, in fact you are not really even redistributing to a special person or company, you are just redistributing it period....

1 0

Re: NTPL & pthreads locks
by Dan Kegel 22 Apr '03

22 Apr '03

Alexandre Julliard wrote: > I don't think we can implement Win32 primitives on top of pthreads, at > least not in a reasonable way. We may be able to do it on top of the > raw kernel futexes, but that's not exactly libc integration (and it > will most likely require new kernel features too). And the only reason > for doing that would be performance, it's certainly not going to make > things more intuitive or more solid. Somebody begs to differ. From http://downloads.transgaming.com/files/winex-3_0_releasenotes.txt : * The core threading model has moved to pthreads to decouple WineX from the continuing changes to certain core system libraries. If Gav can do it, why can't we? :-) - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

4 5

windres: -fo (fwd)
by Dimitrie O. Paun 22 Apr '03

22 Apr '03

---------- Forwarded message ---------- Date: Tue, 22 Apr 2003 14:07:11 -0400 (EDT) From: Dimitrie O. Paun <dimi(a)intelliware.ca> To: binutils(a)sources.redhat.com Subject: windres: -fo This one is the last (famous last words :)) patch in my series of compatibility patches. With this one in, we can hopefully get rid of the ugly ifdefs in Makefiles. You gotta hate MS for the ugly choice of option names... :( BTW, this is now also supported by wrc, so we get the tree way compatibility: windres, wrc, rc. 2003-04-22 Dimitrie O. Paun <dpaun(a)rogers.com> * windres.c: Support -fo for compatibility with rc. (main): Support the -fo option as a synonym for -o. * doc/binutils.texi: Added -fo to the list of options. Index: windres.c =================================================================== RCS file: /cvs/src/src/binutils/windres.c,v retrieving revision 1.17 diff -u -r1.17 windres.c --- windres.c 22 Apr 2003 17:31:08 -0000 1.17 +++ windres.c 22 Apr 2003 18:01:56 -0000 @@ -698,7 +698,7 @@ program_name); fprintf (stream, _(" The options are:\n\ -i --input=<file> Name input file\n\ - -o --output=<file> Name output file\n\ + -o -fo --output=<file> Name output file\n\ -J --input-format=<format> Specify input format\n\ -O --output-format=<format> Specify output format\n\ -F --target=<target> Specify COFF target\n\ @@ -813,7 +813,7 @@ language = 0x409; /* LANG_ENGLISH, SUBLANG_ENGLISH_US. */ use_temp_file = 0; - while ((c = getopt_long (argc, argv, "i:l:o:I:J:O:F:D:U:rhHvV", long_options, + while ((c = getopt_long (argc, argv, "f:i:l:o:I:J:O:F:D:U:rhHvV", long_options, (int *) 0)) != EOF) { switch (c) @@ -822,6 +822,10 @@ input_filename = optarg; break; + case 'f': + if (*optarg != 'o') fatal (_("Unknown option -f%s.\n"), optarg); + optarg++; + /* fall through */ case 'o': output_filename = optarg; break; Index: doc/binutils.texi =================================================================== RCS file: /cvs/src/src/binutils/doc/binutils.texi,v retrieving revision 1.37 diff -u -r1.37 binutils.texi --- doc/binutils.texi 22 Apr 2003 17:31:08 -0000 1.37 +++ doc/binutils.texi 22 Apr 2003 18:02:05 -0000 @@ -2570,6 +2570,7 @@ standard input. @item -o @var{filename} +@item -fo@var{filename} @itemx --output @var{filename} The name of the output file. If this option is not used, then @command{windres} will use the first non-option argument, after any used -- Dimi.

1 0

new script uses winedump
by David Miller 22 Apr '03

22 Apr '03

I have modified the script which cross references dll imports to use winedump instead of dumpbin. It runs in linux now so that more people are able to run it. It is available at http://home.ptd.net/~compsol Please send any questions or comments to me.

1 0

windres: -J -I (take 4)
by Dimitrie O. Paun 22 Apr '03

22 Apr '03

OK, I've received the copyright assignment notification on Apr 10, 2003. (I've forwarded a copy to the list, let me know if you did not get it). So I guess it's prime time for this little patch of mine. Please apply. I have one more patch in mind for windres, and I'm happy :) 2003-04-15 Dimitrie O. Paun <dpaun(a)rogers.com> * windres.c (format_from_name): make the exit on error behaviour optional. (main): Rename the -I option to -J. Introduce -I as synonym for --include-dir. For backwards compatibility also support the old -I behaviour, but issue a deprecation warning. * doc/binutils.texi: Rename -I to -J. Document the new behaviour of the -I option. * testsuite/binutils-all/windres/windres.exp: Add test for the new -J option. Index: windres.c =================================================================== RCS file: /cvs/src/src/binutils/windres.c,v retrieving revision 1.16 diff -u -r1.16 windres.c --- windres.c 5 Apr 2003 08:21:46 -0000 1.16 +++ windres.c 16 Apr 2003 03:14:37 -0000 @@ -106,8 +106,7 @@ /* 150 isn't special; it's just an arbitrary non-ASCII char value. */ -#define OPTION_INCLUDE_DIR 150 -#define OPTION_PREPROCESSOR (OPTION_INCLUDE_DIR + 1) +#define OPTION_PREPROCESSOR 150 #define OPTION_USE_TEMP_FILE (OPTION_PREPROCESSOR + 1) #define OPTION_NO_USE_TEMP_FILE (OPTION_USE_TEMP_FILE + 1) #define OPTION_YYDEBUG (OPTION_NO_USE_TEMP_FILE + 1) @@ -116,8 +115,8 @@ { {"define", required_argument, 0, 'D'}, {"help", no_argument, 0, 'h'}, - {"include-dir", required_argument, 0, OPTION_INCLUDE_DIR}, - {"input-format", required_argument, 0, 'I'}, + {"include-dir", required_argument, 0, 'I'}, + {"input-format", required_argument, 0, 'J'}, {"language", required_argument, 0, 'l'}, {"output-format", required_argument, 0, 'O'}, {"preprocessor", required_argument, 0, OPTION_PREPROCESSOR}, @@ -135,7 +134,7 @@ static void res_init PARAMS ((void)); static int extended_menuitems PARAMS ((const struct menuitem *)); -static enum res_format format_from_name PARAMS ((const char *)); +static enum res_format format_from_name PARAMS ((const char *, int)); static enum res_format format_from_filename PARAMS ((const char *, int)); static void usage PARAMS ((FILE *, int)); static int cmp_res_entry PARAMS ((const PTR, const PTR)); @@ -583,8 +582,9 @@ /* Convert a string to a format type, or exit if it can't be done. */ static enum res_format -format_from_name (name) +format_from_name (name, exit_on_error) const char *name; + int exit_on_error; { const struct format_map *m; @@ -592,7 +592,7 @@ if (strcasecmp (m->name, name) == 0) break; - if (m->name == NULL) + if (m->name == NULL && exit_on_error) { non_fatal (_("unknown format type `%s'"), name); fprintf (stderr, _("%s: supported formats:"), program_name); @@ -699,15 +699,15 @@ fprintf (stream, _(" The options are:\n\ -i --input=<file> Name input file\n\ -o --output=<file> Name output file\n\ - -I --input-format=<format> Specify input format\n\ + -J --input-format=<format> Specify input format\n\ -O --output-format=<format> Specify output format\n\ -F --target=<target> Specify COFF target\n\ --preprocessor=<program> Program to use to preprocess rc file\n\ - --include-dir=<dir> Include directory when preprocessing rc file\n\ + -I --include-dir=<dir> Include directory when preprocessing rc file\n\ -D --define <sym>[=<val>] Define SYM when preprocessing rc file\n\ -U --undefine <sym> Undefine SYM when preprocessing rc file\n\ -v --verbose Verbose - tells you what it's doing\n\ - --language=<val> Set language when reading rc file\n\ + -l --language=<val> Set language when reading rc file\n\ --use-temp-file Use a temporary file instead of popen to read\n\ the preprocessor output\n\ --no-use-temp-file Use popen (default)\n")); @@ -776,6 +776,7 @@ char *input_filename; char *output_filename; enum res_format input_format; + enum res_format input_format_tmp; enum res_format output_format; char *target; char *preprocessor; @@ -812,7 +813,7 @@ language = 0x409; /* LANG_ENGLISH, SUBLANG_ENGLISH_US. */ use_temp_file = 0; - while ((c = getopt_long (argc, argv, "i:l:o:I:O:F:D:U:rhHvV", long_options, + while ((c = getopt_long (argc, argv, "i:l:o:I:J:O:F:D:U:rhHvV", long_options, (int *) 0)) != EOF) { switch (c) @@ -825,12 +826,12 @@ output_filename = optarg; break; - case 'I': - input_format = format_from_name (optarg); + case 'J': + input_format = format_from_name (optarg, 1); break; case 'O': - output_format = format_from_name (optarg); + output_format = format_from_name (optarg, 1); break; case 'F': @@ -869,7 +870,16 @@ verbose ++; break; - case OPTION_INCLUDE_DIR: + case 'I': + /* for backward compatibility, should be removed in the future */ + input_format_tmp = format_from_name (optarg, 0); + if (input_format_tmp != RES_FORMAT_UNKNOWN) + { + fprintf (stderr, _("Option -I is deprecated for setting the input format, please use -J instead.\n")); + input_format = input_format_tmp; + break; + } + if (preprocargs == NULL) { quotedarg = quot (optarg); Index: doc/binutils.texi =================================================================== RCS file: /cvs/src/src/binutils/doc/binutils.texi,v retrieving revision 1.36 diff -u -r1.36 binutils.texi --- doc/binutils.texi 9 Apr 2003 09:55:13 -0000 1.36 +++ doc/binutils.texi 16 Apr 2003 03:14:42 -0000 @@ -2577,7 +2577,7 @@ non-option argument, then @command{windres} will write to standard output. @command{windres} can not write a COFF file to standard output. -@item -I @var{format} +@item -J @var{format} @itemx --input-format @var{format} The input format to read. @var{format} may be @samp{res}, @samp{rc}, or @samp{coff}. If no input format is specified, @command{windres} will @@ -2605,11 +2605,17 @@ to use, including any leading arguments. The default preprocessor argument is @code{gcc -E -xc-header -DRC_INVOKED}. +@item -I @var{directory} @item --include-dir @var{directory} Specify an include directory to use when reading an @code{rc} file. @command{windres} will pass this to the preprocessor as an @option{-I} option. @command{windres} will also search this directory when looking for -files named in the @code{rc} file. +files named in the @code{rc} file. If the argument passed to this command +matches any of the supported @var{formats} (as descrived in the @option{-J} +option), it will issue a deprecation warning, and behave just like the +@option{-J} option. New programs should not use this behaviour. If a +directory happens to match a @var{format}, simple prefix it with @samp{./} +to disable the backward compatibility. @item -D @var{target} @itemx --define @var{sym}[=@var{val}] Index: testsuite/binutils-all/windres/windres.exp =================================================================== RCS file: /cvs/src/src/binutils/testsuite/binutils-all/windres/windres.exp,v retrieving revision 1.3 diff -u -r1.3 windres.exp --- testsuite/binutils-all/windres/windres.exp 27 Jul 2001 16:16:07 -0000 1.3 +++ testsuite/binutils-all/windres/windres.exp 16 Apr 2003 03:14:43 -0000 @@ -81,6 +81,40 @@ setup_xfail *-* } + verbose "$wr -J rc -O res $res tmpdir/$broot.res" 1 + catch "exec $wr -J rc -O res $res tmpdir/$broot.res" err + + if ![string match "" $err] then { + send_log "$err\n" + verbose "$err" 1 + fail "windres/$broot (parse)" + continue; + } + pass "windres/$broot (parse)" + + set rc [open $res] + while { [gets $rc line] != -1 } { + if ![regexp "^(//|/\*|#)" $line] { + break + } + if [regexp "parse-only" $line] { + file delete "tmpdir/$broot.res" + set done 1 + break; + } + if [regexp "\[xc\]fail *(\[^ \]*)" $line junk sys] { + setup_xfail $sys + continue; + } + } + if { $done != 0 } { + continue; + } + + if { "$broot" != "bmpalign" && "$target_xfail" == "yes" } { + setup_xfail *-* + } + verbose "$wr -I rc -O res $res tmpdir/$broot.res" 1 catch "exec $wr -I rc -O res $res tmpdir/$broot.res" err -- Dimi.

2 1

vxd idea
by Vilppa Salt 22 Apr '03

22 Apr '03

Hi Could this Qemu emulator be used for running applications with vxd files on x86? If ring 0 is reserved so could it be emulated with qemu and mapped appropriately inside Wine? --- Vilppa- Sunpoint.net ilmoittaa: Sunpoint.net tarjoaa kaikille rekisteröityneille käyttäjilleen kuukausimaksuttoman Internet -yhteyden (pvm). http://www.sunpoint.net/SunAds/click.htm?mode=footer&id=71&jump=http%3A%2F%…

2 1

Re: named pipe patch
by Dan Kegel 22 Apr '03

22 Apr '03

Bill Medland wrote: >>Agreed. But blocking is hard. It may require the full rewrite of >>wine's named pipe support the other guy is working on. > > > It probably requires more than that; I reckon it may require a rewrite of the > general flushing code. Since it has to block, I don't know where the waiting > is supposed to happen (in the server or in the client) I had an idea on this -- might not be so hard after all. >>My guess is that the data loss you were running into is the >>main real-world issue, and the fact we don't blocking on pipe flush >>won't be a showstopper. Please do try my patch, and >>let me know what you see in practice. I'd like to know if >>what I'm doing is even close. > > > Doesn't seem to work, I'm afraid. OK, I'll chuck that part of my patch then. > Don't bother trying to hack it on my behalf, just do it for yourself. I get > around it by sticking a 50ms sleep in the server before the flush; it's long > enough to force a process switch and for the client to read the pipe. It'll > do for a few months while I am developing and hopefully the proper fix will > be out then. I bet I can stick in a test on bytes in the pipe and loop appropriately. My need has vanished -- now I'm just trying to achieve win32 compliance. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

1 0

RE: FoxPro & Wine :)
by Patrik Stridvall 22 Apr '03

22 Apr '03

> Dimitrie O. Paun wrote: > > On April 22, 2003 01:17 am, Dan Kegel wrote: > > > >>It may not be, but at least it brings it into the realm > >>of Microsoft moves we've seen before. (cf. MFC dlls, which are > >>never distributed with Windows itself, and may legally > >>tie all MFC apps to run on Windows alone, if the MFC EULA > >>holds. Or so I recall.) > > > > > > And the question is: is this enforceable? > > And the answer is: if it isn't, neither is the (L)GPL. Why > would MS not > be able to place restrictions on distribution of their own > copyrighted code? With risk of rekindling the LGPL debate, I have to agree. Both the Wine LGPL issue and the Microsoft "DLL" redistribution issue above have one thing in common: "Somebody is both trying to have the cake and eat it." I have a long time, invain it seems, been trying to argue that copyright law neither: 1. Should (from a sane public policy point of view) 2. Intends (from what copyright traditionally is meant for) 3. Does (from a strict, by the letter, analysis on the law) support the view that it is allowed to both "have the cake and eat it". Very, very simplified. You have basicly have two choices: 1. Distribute your work (or part of it) for free 2. Distribute your work (or part of it) for a fee. if you choose (1) because you for some reason doesn't think (2) is to your advantages you have no right to complain that things didn't work out as you hoped. In the Microsoft Visual FoxPro it is quite obvious that demanding a fee for the "runtime" would reduce the number of developers using the product, so they didn't. Now they have to live with the consequences...

2 1

re: FoxPro & Wine :)
by Dan Kegel 22 Apr '03

22 Apr '03

Dimi wrote: > Summary: Microsoft threatens developers for running > Visual FoxPro on Linux using Wine. > > http://yro.slashdot.org/yro/03/04/21/2045200.shtml?tid=109&tid=125 > > I still don't get it how it is legal to tie a product to the OS. It's the redistributable files. See http://www.linuxtransfer.com/h/misc_vfplinuxjackofhearts.htm for the details. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

7 8

getopt_long not found, even though it is present
by Gerald Pfeifer 22 Apr '03

22 Apr '03

Assume we are on a system which does have /usr/local/include/getopt.h, and support for getopt_long, but where getopt_long is _not_ in libc. Our configure then diagnoses #define HAVE_GETOPT_H 1 /* #undef HAVE_GETOPT_LONG */ which leads a compilation error for tools/wrc/wrc.c which includes "wine/port.h" and <getopt.h>, for _both_ define struct option. As far as I can see, the problem here is that in tools/wrc/wrc.c we check for the presence of HAVE_GETOPT_H, while in wine/port.h we check for HAVE_GETOPT_LONG. The patch below is one way to fix this problem, another way would be to move the #inclusion of <getopt.h> from individual files to wine/port.h. Yet another option would be the hack autoconf to try linking libgnugetopt when looking for getopt_long, but I don't know how to hack this into configure. How should we resolve this? Gerald Index: wrc.c =================================================================== RCS file: /home/wine/wine/tools/wrc/wrc.c,v retrieving revision 1.33 diff -u -3 -p -r1.33 wrc.c --- wrc.c 28 Mar 2003 19:31:49 -0000 1.33 +++ wrc.c 17 Apr 2003 10:18:18 -0000 @@ -32,7 +32,9 @@ #include <ctype.h> #include <signal.h> #ifdef HAVE_GETOPT_H -# include <getopt.h> +# ifdef HAVE_GETOPT_LONG +# include <getopt.h> +# endif #endif #include "wrc.h"

1 1

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