- Wine-Devel - list.winehq.org

Compiling problem
by winedevel＠007mundo.com Dec. 17, 2002

Dec. 17, 2002

Hello, i have this compiling problem (sorry if this isn't the correct list, if yes, please let me know) make[2]: *** [ppy.tab.c] core dumped .. make[1]: *** [wrc/__depend__] Error 2 .. make: *** [tools/__depend__] Error 2 and what? Thanks ----------------------------------------------------- Obtenga su mail gratis con 007 Mundo www.007mundo.com -----------------------------------------------------

1 0

stub handling
by Dimitrie O. Paun Dec. 17, 2002

Dec. 17, 2002

Alexandre, In the past functions that were declared stubs in the .spec file got a dummy definition, so programs using them could link. This doesn't seem to be the case anymore: mingwrap -mwindows -mno-cygwin -s -o putty.exe be_all.o cmdline.o ldisc.o \ ldiscucs.o logging.o misc.o noise.o pageantc.o portfwd.o \ printing.o proxy.o raw.o rlogin.o settings.o sizetip.o ssh.o \ sshaes.o sshblowf.o sshbn.o sshcrc.o sshcrcda.o sshdes.o \ sshdh.o sshdss.o sshmd5.o sshpubk.o sshrand.o sshrsa.o \ sshsh512.o sshsha.o sshzlib.o telnet.o terminal.o tree234.o \ unicode.o version.o wcwidth.o wildcard.o win_res.res.o \ winctrls.o windlg.o window.o winnet.o winstore.o winutils.o \ x11fwd.o -ladvapi32 -lcomctl32 -lcomdlg32 -lgdi32 -limm32 \ -lshell32 -luser32 -lwinmm -lwinspool -lwsock32 printing.o: In function `printer_start_job': printing.o(.text+0x1fa): undefined reference to `EndDocPrinter' printing.o(.text+0x20a): undefined reference to `EndPagePrinter' printing.o(.text+0x237): undefined reference to `StartDocPrinterA' printing.o(.text+0x24a): undefined reference to `StartPagePrinter' printing.o: In function `printer_finish_job': printing.o(.text+0x2b6): undefined reference to `EndPagePrinter' printing.o(.text+0x2bd): undefined reference to `EndDocPrinter' collect2: ld returned 1 exit status How shall we proceed? -- Dimi.

2 2

wrc options
by Dimitrie O. Paun Dec. 17, 2002

Dec. 17, 2002

Hello people, I was looking at wrc a little bit, and I am curious to know if we really need all these options. They just pollute the command line namespace, and add confusion. windres has none of these options, and it's doing just fine. Let me be more explicit: " -a n Alignment of resource (win16 only, default is 4)\n" Do we really need this? Shouldn't this be hardcoded to some standard values? " -A Auto register resources (only with gcc 2.7 and better)\n" " -b Create an assembly array from a binary .res file\n" Do we still want to create the assembly output? Do we still use that? " -B x Set output byte-order x={n[ative], l[ittle], b[ig]}\n" " (win32 only; default is n[ative] which equals " Again, shouldn't this be hardcoded to some standard value, that we expect in Wine when we read the resources? " -c Add 'const' prefix to C constants\n" What's this good for? " -e Disable recognition of win32 keywords in 16bit compile\n" Shouldn't this be on be default? Should we even support 16bit compiles anymore? " -E Preprocess only\n" ??? What for? " -g Add symbols to the global c namespace\n" Is this choice useful? " -h Also generate a .h file\n" " -H file Same as -h but written to file\n" I would personally collapse this one into the type of output to be generated. " -L Leave case of embedded filenames as is\n" Shouldn't this one be on by default? Why do we need this option? " -m Do not remap numerical resource IDs\n" What is this one used for? " -n Do not generate .s file\n" Should we still generate .s files in the first place? " -p prefix Give a prefix for the generated names\n" Why? " -r Create binary .res file (compile only)\n" I would make this default behavior. " -s Add structure with win32/16 (PE/NE) resource directory\n" I'd guess if we need it, it should be generated, if not, just don't do it. Why do we have an option? " -t Generate indirect loadable resource tables\n" " -T Generate only indirect loadable resources tables\n" What are these used for? " -w 16|32 Select win16 or win32 output (default is win32)\n" Should we care about win16 in the first place? We clearly never going to support win16 in Winelib, so why have this option? -- Dimi.

4 6

linking between wine books
by Bill Medland Dec. 17, 2002

Dec. 17, 2002

What to people think? Should we be linking between different books in the wine-doc set? I had put a link from wine-user to a section in wine-devel. The pdf was happy enough with it but the sgm-to-html choked on it. Easiest solution is to drop the link. Otherwise can someone point me at an example where it works? -- Bill Medland

2 1

Re: include msvcrt/ fix (take 2)
by Dimitrie O. Paun Dec. 17, 2002

Dec. 17, 2002

On December 14, 2002 02:10 pm, Dimitrie O. Paun wrote: > ChangeLog > Do not explicitly include msvcrt files from msvcrt headers. > Include windef.h instead of winnt.h to get all appropriate types. Alexandre, What about this one? Currently {ming,wine}wrap are badly broken. I hope this one is rather uncontroversial, but it does depend on that bit from crtdll, and I think that is the problem. -- Dimi.

2 1

regression - 'wine notepad.exe' now has fixme
by Dan Kegel Dec. 17, 2002

Dec. 17, 2002

With today's cvs, I see fixme:win:SetWindowTextA cannot set text "Notepad - (untitled)" of other process window (nil) when I run notepad.exe. This also happens with wine20021125, but not with wine20020904. Should I narrow it down to a specific patch so it can be fixed, or is this a known problem? - Dan

3 2

Re: winmm test extension
by Paul Millar Dec. 16, 2002

Dec. 16, 2002

On Mon, 16 Dec 2002, Francois Gouget wrote: > How to make it play a sound? > Simple. Just pass the 'play' parameter to the test. Playing a sound is a nice idea, but perhaps there's a more general way of choosing to hear it. In the future, there might be many interactive tests: or at least, ones that require someone to sit in front of the computer. These could all be turned off by default, but could be turned on through an option to runtest, or via an environment variable (WINETEST_INTERACTIVE). Does this sound reasonable? (no pun intended ;) ---- Paul Millar

2 1

Re: fdopen behaviour correction
by Uwe Bonnes Dec. 16, 2002

Dec. 16, 2002

>>>>> "Bill" == Bill Currie <bill(a)taniwha.org> writes: Bill> fdopen is not supposed to rewind the file descriptor being given a Bill> FILE *. Proof of this comes from quakeforge working in windows Bill> natively but not in wine without the attatched patch. Bill> ChangeLog * dlls/msvcrt/file.c don't rewind the file after Bill> creating the FILE* handle It is good to have a test case for such cases in wine/dlls/msvcrt/tests. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

1 0

Re: resend: ConvertThreadToFiber stub
by Greg Turner Dec. 16, 2002

Dec. 16, 2002

On Monday 16 December 2002 01:08 pm, Rein Klazes wrote: > Use this one, the previous patch wasn't clean > > > Changelog: > > dlls/kernel : kernel32.spec > scheduler : thread.c > > Add a stub for ConvertThreadToFiber > > Rein. funny, I recently implemented same but never submitted. using HTML Help by any chance? -- gmt

2 1

Re: winmm test extension
by Dan Kegel Dec. 16, 2002

Dec. 16, 2002

Francois Gouget wrote: > This test extends the winmm test and makes it possible to play actual > sound. Of course the test will not do that unless you specifically ask > for it: > * I doubt anyone would be happy to do 'make test' in Wine's main > directory and to get annoying long beeps comming out of their computer > * tests are usually run unattended and there is not much point playing > the sounds if no-one listens to them to make sure they got played > correctly. > > So what does it do? > For each supported format it plays the international 'LA', i.e. a 440Hz > sinusoid. It is expected that on some sound cards and for some formats > the signal will have to be converted from 8 to 16 bit or from mono to > stereo, or even resampled. Normally this should not affect the sound > being played so you should keep hearing the same tone. If that's not the > case then something went wrong during th I may have a counterexample. The patch I submitted recently was to fix a hang in playing sound. So if you add a timeout to your test, it would at least verify that sounds played in the proper amount of time, and didn't hang wine. - Dan

2 1