wine-20031212 defaults to Thai ui?!
This is hilarious... I just built wine-20031212 from source (using tools/wineinstall), and... all the menus are in Thai. Even if I run winefile, or a real copy of notepad.exe. Even if I set LANG=C before running. WTF? - Dan
Re: Easy IE installer script
On Wed, 24 Dec 2003 08:29, Ivan Leo Murray-Smith wrote: >[explanation of why using the install script is probably illegal] I agree. I'm pretty sure these are only redistributable under a license that limits their use to Windows. Even if the limitation is illegal under competition laws, this doesn't make it legal to distribute the files without a license in terms that allow distribution in the particular circumstances. It may be that installing IE under Wine at all is outside the IE license. The situation may be different if it was originally installed under Windows and the original Windows partition merely mounted to use it under Wine. Of course I couldn't be bothered looking into this more closely because I'd rather not invite all the security issues that come with running IE.
Re: Problems with Ultima Online: Age of Shadows [Textbox glitch + out of memory error]
On Tuesday 23 December 2003 23:54, Andreas Mohr wrote: > Edit box problem. Use --debugmsg +edit and try to fix the positioning > problem in our code. Thanks. > As we all know (or maybe not ;), an Out Of Memory is NEVER an Out Of > Memory, but instead a problematic or unimplemented function. > --debugmsg +relay to find out what fails. Yes, I was suspecting this, because I have a lot of memory ;) Thanks for the hint, I'll investigate on this to find out the problem. -- Flameeyes <[EMAIL PROTECTED]> You can find LIRC for 2.6 kernels at http://flameeyes.web.ctonet.it/
Re: Problems with Ultima Online: Age of Shadows [Textbox glitch + out of memory error]
Hi, On Wed, Dec 24, 2003 at 12:40:38AM +, Flameeyes wrote: > Hi all! > I was trying to run Ultima Online: Age of Shadows (latest patchlevel after > autopatch), but I have some problems. > > The first problem is actually a glitch, in autopatcher, when the textbox is > moved at end, the text is hide, because it moves as first character of the > textbox the after-the-last character of the text in it. Edit box problem. Use --debugmsg +edit and try to fix the positioning problem in our code. > The second is a big problem: when starting the client, it gives an out of > memory error. I can't find where the problem is because I don't know for sure > which trace channel has the functions for memory statistics. As we all know (or maybe not ;), an Out Of Memory is NEVER an Out Of Memory, but instead a problematic or unimplemented function. --debugmsg +relay to find out what fails. Andreas Mohr
Problems with Ultima Online: Age of Shadows [Textbox glitch + out of memory error]
Hi all! I was trying to run Ultima Online: Age of Shadows (latest patchlevel after autopatch), but I have some problems. The first problem is actually a glitch, in autopatcher, when the textbox is moved at end, the text is hide, because it moves as first character of the textbox the after-the-last character of the text in it. The second is a big problem: when starting the client, it gives an out of memory error. I can't find where the problem is because I don't know for sure which trace channel has the functions for memory statistics. If someone has an hint for me, I'll investigate better and try to fix it. -- Flameeyes <[EMAIL PROTECTED]> You can find LIRC for 2.6 kernels at http://flameeyes.web.ctonet.it/
Re: Easy IE installer script
> What about people who redistribute those apps in turn? But they aren't using them in there own app, so they aren't creating a derivate work. Only the vendor (In the case of the script you) needs a license. In any case you can't just take the dlls from an app, you must find one that allows you to distribute them in a derivate product. > I seriously doubt you have to write every piece of your code in a > project using MS tools in order to be able to redistribute a DLL. Even > if the license did say such a preposterous thing, it could certainly be > ignored. certainly not, but you must at least partially write it with a M$ tool that allows you to distribute the dlls, and again I remember reading that you must develop for windows. dll-files stays illegal, I think the best option is to use the users windows cd. Also it will make the install a little bit faster, as it won't have to download anything. Ivan.
Re: Easy IE installer script
On Tue, 2003-12-23 at 21:29, Ivan Leo Murray-Smith wrote: > They come with apps because the vendors of those apps have a license from M$ to > redistribute them. You need such a license before you can redistribute them. What about people who redistribute those apps in turn? For instance, if I write a public domain program that uses the MFCs, and include MFC40.DLL and upload it, then somebody else emails it to a friend - are they redistributing without a license? I don't know. > As I don't think you developed the > script with a M$ tool that comes with a license that allows you to distribute M$ > dlls for whatever platform, this is irrelevant. I seriously doubt you have to write every piece of your code in a project using MS tools in order to be able to redistribute a DLL. Even if the license did say such a preposterous thing, it could certainly be ignored. > The antitrust case about this is not over, actually Bill testified at it > recently, and maybe D.C. and the ten suing states will win. If they do, there > may be builds of windows without OE/IE/MSN, but I don't think there will be > OE/IE/MSN that can legally run without a windows license. They can't tie MSN to Windows, regardless of how it's shipped, MSN doesn't have a monopoly. > dll-files is a illegal site, M$ doesn't do anything about it but it stays > illegal, so it may be a problem because I think the DMCA says you can't link > illegal software (I suppose that's why nobody in the US links to linux dvd > players with decks) No, the DMCA does not say that (as far as I understand), it says you may not distribute (and maybe link to) code that breaks encryption for the purposes of circumventing copy protection. IANAL etc. YMMV :) thanks -mike
Re: Easy IE installer script
> MSVCRT40/MFC40 aren't components of windows though, they are > redistributable DLLs that come with apps. They come with apps because the vendors of those apps have a license from M$ to redistribute them. You need such a license before you can redistribute them. > Well, I'm pretty sure that sort of clause would be illegal, they can't > say "such and such can only be run on Windows", as that'd be tying a > product to a monopoly. I'm sure it's illegal, but that's how things are. Anybody (DOJ?) could sue them on that point, are you going to have a go? As I don't think you developed the script with a M$ tool that comes with a license that allows you to distribute M$ dlls for whatever platform, this is irrelevant. > If they start claiming that the MFC DLL can only be used on genuine > Windows, then we have much bigger problems than having to pull a > convenience script - that would make many programs unrunnable on Wine > (but of course they cannot say this, so that's not a problem). No, if an app is developed for windows using M$ tools/sdk/compiler, but a user runs the app on wine, it is perfectly legal. Well, technically some M$ lawyer may say it isn't, but nobody would be liable. > Well this is what Microsoft claim, but the distinction has never really > been spelled out. MSN Messenger comes with Windows too - does that make > it an OS component? I'm not sure. The antitrust case about this is not over, actually Bill testified at it recently, and maybe D.C. and the ten suing states will win. If they do, there may be builds of windows without OE/IE/MSN, but I don't think there will be OE/IE/MSN that can legally run without a windows license. > I have an old copy of MSVC++ lying around here somewhere anyway, so I > guess I do have a license. If I can't find it then buying a new one from > ebay or something is not too hard. Have a look at the license and see what it says. > The easiest solution is to simply use wget to fetch the files from > dll-files.com : a very silly getout clause that probably wouldn't make > much difference in a court of law, but hopefully we will never have to > find out. dll-files is a illegal site, M$ doesn't do anything about it but it stays illegal, so it may be a problem because I think the DMCA says you can't link illegal software (I suppose that's why nobody in the US links to linux dvd players with decks) Ivan.
Re: newbie wine developer question
On Tue, 2003-12-23 at 21:02, Zimler Attila wrote: > fixme:xvidmode:X11DRV_XF86VM_SetCurrentMode Need to update SYSMETRICS > after resizing display (now 640x480) I was going to suggest this one, but it seems a patch to remove it was already submitted by Alex a while back (but not committed) so I'd ignore it, hopefully Alex will get to it soon. fixme:ddraw:Main_DirectDrawClipper_Initialize (0x403afce8)->(0x4036cb84,0x),stub! If you want a big project, implementing the DDraw clipper could be it - I don't know much about this component but it's used in some games and apps to restrict drawing to the screen. thanks -mike
Re: Easy IE installer script
On Tue, 2003-12-23 at 20:24, Ivan Leo Murray-Smith wrote: > > I'd like to see the legal text that says they are > > not redistributable, > The microsoft windows (Favourite version of 32-bit windows here) license MSVCRT40/MFC40 aren't components of windows though, they are redistributable DLLs that come with apps. > IIRC you need a M$ development tool to obtain a license that allows you to do > that. Also, such license only allows use for applications designed for microsoft > windows. AFAIK wine is not a windows app. Well, I'm pretty sure that sort of clause would be illegal, they can't say "such and such can only be run on Windows", as that'd be tying a product to a monopoly. If they start claiming that the MFC DLL can only be used on genuine Windows, then we have much bigger problems than having to pull a convenience script - that would make many programs unrunnable on Wine (but of course they cannot say this, so that's not a problem). > It is, IE is not an app but a OS component, so there are a lot more restrictions > on IE than on anything else. A solution would be to ask the user to insert his > windows CD, and just get the files needed for IE installation from there. Well this is what Microsoft claim, but the distinction has never really been spelled out. MSN Messenger comes with Windows too - does that make it an OS component? I'm not sure. I'm not even sure if a Windows CD has these dlls, as they are intended to be distributed by apps. It might do, and then yes inserting the CD would be one solution. > BTW they already CAN sue you. Sure, they can sue me anytime for practically anything and I'd probably be instantly bankrupt just getting to court, so this whole discussion is somewhat academic. > No, it would be very easy for them to prove that all vendors that ship MSVCRT > with there apps have a license from microsoft to do so. I have an old copy of MSVC++ lying around here somewhere anyway, so I guess I do have a license. If I can't find it then buying a new one from ebay or something is not too hard. The easiest solution is to simply use wget to fetch the files from dll-files.com : a very silly getout clause that probably wouldn't make much difference in a court of law, but hopefully we will never have to find out. thanks -mike
Re: newbie wine developer question
Zimler Attila wrote: 2) I would like to fix some fixme (which I can reproduce), but I don't understand a lot of thins. (I'm new to wine, but not new to C). Could somebody help me to start involved in the development process? The best way to get started is: 1. pick some repeatable bug 2. write a small C program that detects the bug 3. turn the C program into a standard wine testcase (pretty easy) 4. verify that the testcase passes on real windows and fails on Wine 5. submit the testcase as a patch Optionally, you can go on: 6. fix the bug, and verify that the test passes 7. submit the fix as a patch For instance, I noticed last year that the named pipe win32 api calls were busted, so I wrote a test case and submitted it. Even though I didn't go on to fix the bug, my work was appreciated, and it helped the guy who did actually fix the bug. - Dan
Re: Easy IE installer script
> Why do you say that? Because of how copyright works, if a file isn't yours, you need a written permission to prove that you have the right to use it/redistribute it, or the copyright holder can claim that the use/redistribution of the file is unauthorized. > I'd like to see the legal text that says they are > not redistributable, The microsoft windows (Favourite version of 32-bit windows here) license > as they are intended to be shipped alongside > applications IIRC you need a M$ development tool to obtain a license that allows you to do that. Also, such license only allows use for applications designed for microsoft windows. AFAIK wine is not a windows app. > and can be freely downloaded from the net M$ is free to sue anybody that violates it's copyright, and claiming that other people have violated M$ copyright has never (And will never) save anybody in court. They can choose to sue you and not dll-files. > (ie the situation > is no different to the current one). It is, IE is not an app but a OS component, so there are a lot more restrictions on IE than on anything else. A solution would be to ask the user to insert his windows CD, and just get the files needed for IE installation from there. > Maybe, but they'd have to sue me. Given that there are people running > websites that ship practically every DLL on a windows system, that would > not make much sense. Those websites are online to help windows users, winehq is online to get windows users to unix+wine BTW they already CAN sue you. > They'd also have a hard time arguing that the MSVC > Runtime is not meant to be redistributed when many apps do so. No, it would be very easy for them to prove that all vendors that ship MSVCRT with there apps have a license from microsoft to do so. Ivan.
Re: Re: winemine2 winelib example
> Doh, I meant bin2res. After making clean I need to > extract them like: > ../../tools/bin2res -o faces.bmp ./rsrc.rc > > Otherwise they aren't available when wrc runs on rc.rc. > Seems odd that wrc can't pull the data out of the src.rc > file itself though. Actually it can, but it's the other resource compilers that can't (MS' rc, and windres). So for compatibility with those, we use the current scheme. -- Dimi.
Re: winemine2 winelib example
On Tuesday 23 December 2003 02:38 pm, Dimitrie O. Paun wrote: > > Should we modify the winelib documentation? The docs > > make it sound like its an easy two step process. > > Yes, we should. We should also modify winemaker to: > 1. Generate MinGW compatible Makefiles > 2. Use winegcc to achive (1) > 3. Drop the configure script altogether. With winegcc > there's no need for a configure script anymore, and > besides, using autoconf is project policy, not > something we should force down people's throats. > > > Also, is there a way to get wrc to extract all of the > > objects in an rc file? > > What do you mean by this? > Doh, I meant bin2res. After making clean I need to extract them like: ../../tools/bin2res -o faces.bmp ./rsrc.rc Otherwise they aren't available when wrc runs on rsrc.rc. Seems odd that wrc can't pull the data out of the rsrc.rc file itself though. Chris
Re: Easy IE installer script
On Tue, 2003-12-23 at 19:47, hatky wrote: > I tried it out, seems ie6 setup fails with current > CVS, says something on low mem or lack of space. Well, maybe it is correct? Did you check disk space/memory? > Mandrake Linux 9.2 with all patches and latest CVS > wine, How latest is latest? There was a bug that was free disk space related up until recently. Otherwise, I don't know sorry, it installs fine here - could you debug it?
Re: newbie wine developer question
Andreas Mohr wrote: Hi, On Tue, Dec 23, 2003 at 06:31:40PM +, Zimler Attila wrote: 2) I would like to fix some fixme (which I can reproduce), but I don't understand a lot of thins. (I'm new to wine, but not new to C). Could somebody help me to start involved in the development process? Please mention several specific FIXMEs that you'd like to work on. That's the best way to help you get started. Andreas Mohr Hi, In first run I can reproduce the following fixme's: fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x4036cb78)->(00010021,0051) fixme:xvidmode:X11DRV_XF86VM_SetCurrentMode Cannot change screen BPP from 32 to 16 fixme:xvidmode:X11DRV_XF86VM_SetCurrentMode Need to update SYSMETRICS after resizing display (now 640x480) fixme:xvidmode:X11DRV_XF86VM_SetCurrentMode Cannot change screen BPP from 32 to 16 fixme:xvidmode:X11DRV_XF86VM_SetCurrentMode Need to update SYSMETRICS after resizing display (now 640x480) fixme:x11drv:X11DRV_DDHAL_CreatePalette stub fixme:ddraw:DIB_DirectDrawSurface_Blt dwFlags DDBLT_WAIT and/or DDBLT_ASYNC: can't handle right now. fixme:dsound:IDirectSoundImpl_SetCooperativeLevel level=DSSCL_PRIORITY not fully supported fixme:ddraw:Main_DirectDrawClipper_Initialize (0x403afce8)->(0x4036cb84,0x),stub! fixme:winmm:MMDRV_Exit Closing while ll-driver open which one is the most easiest to fix? (i will gladly fix any of them, if i get help to learning wine code, and the philosophy behind it) I also looked in the code for the last fixme, but i dont understand what is the type of the handle. I guess the code between #if 0 and #endif is not correct, on the first run, I thought a solution like that code:) Attila ZIMLER
Re: Easy IE installer script
On Tue, 2003-12-23 at 19:48, Ivan Leo Murray-Smith wrote: > You can't redistribute them, unless you have some sort of special license from > m$. There is a simple trick to get round this. Why do you say that? I'd like to see the legal text that says they are not redistributable, as they are intended to be shipped alongside applications and can be freely downloaded from the net (ie the situation is no different to the current one). > I suppose it would be a good thing to warn the user that > he must have a windows license to use IE4,5 or 6. Yes, I intend to put a notice to that effect in a future version. > >Do people think this should be linked to from WineHQ? > Not as it is now, M$ could sue for copyright violation, it wouldn't be a nice > experience. Maybe, but they'd have to sue me. Given that there are people running websites that ship practically every DLL on a windows system, that would not make much sense. They'd also have a hard time arguing that the MSVC Runtime is not meant to be redistributed when many apps do so.
Re: Easy IE installer script
I tried it out, seems ie6 setup fails with current CVS, says something on low mem or lack of space. Mandrake Linux 9.2 with all patches and latest CVS wine, Hatky. __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
Re: Easy IE installer script
>The installer program contains a few things that may or may not be >redistributable - for instance, it contains MSVCRT40.DLL and MFC40.DLL, >both of which are available for free from dll-files.com so it seemed to >make sense to include them. You can't redistribute them, unless you have some sort of special license from m$. There is a simple trick to get round this. You can usually find m$ dlls like mfc, msvcrt and so on in microsoft trial game installers. So, to do this legally, you would have to ask the if he wants to accept the license conditions of the trial game that contains the needed dll, then download the demo from the net (You can even point to download.microsoft.com), extract and install the dll (Installing the game may be necessary if you can't get the dlls out of the installer), and then do whatever else the script does. I suppose it would be a good thing to warn the user that he must have a windows license to use IE4,5 or 6. >Do people think this should be linked to from WineHQ? Not as it is now, M$ could sue for copyright violation, it wouldn't be a nice experience. Ivan.
Re: Re: winemine2 winelib example
> Should we modify the winelib documentation? The docs > make it sound like its an easy two step process. Yes, we should. We should also modify winemaker to: 1. Generate MinGW compatible Makefiles 2. Use winegcc to achive (1) 3. Drop the configure script altogether. With winegcc there's no need for a configure script anymore, and besides, using autoconf is project policy, not something we should force down people's throats. > Also, is there a way to get wrc to extract all of the > objects in an rc file? What do you mean by this? -- Dimi.
Re: newbie wine developer question
> "Zimler" == Zimler Attila <[EMAIL PROTECTED]> writes: Zimler> Hi, Since I'm new in developing wine please forgive me if I ask Zimler> a question that is answered earlier (I tried to search an answer Zimler> for my questions, but I did not found.) Zimler> 1) Should I report fixme's in bugzilla? (I guess, not, but I'm Zimler> not sure). No , FIXMEs shouldn't be reported. Zimler> 2) I would like to fix some fixme (which I can Zimler> reproduce), but I don't understand a lot of thins. (I'm new to Zimler> wine, but not new to C). Could somebody help me to start Zimler> involved in the development process? Read the API description, ask specific question, send patches for inclusion to wine-patches or put them to discussion on wine-devel. Don't get frustrated if nobody reacts, try again. It is a good habit and helps to understand the problem when you write test cases for our test suite, test them against wine and windows and submitt them too. Bye -- Uwe Bonnes[EMAIL PROTECTED] Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt - Tel. 06151 162516 Fax. 06151 164321 --
Re: winemine2 winelib example
Should we modify the winelib documentation? The docs make it sound like its an easy two step process. Also, is there a way to get wrc to extract all of the objects in an rc file? That would make the rc processing step easier and probably a couple line makefile edit would make the example work. Chris On Tuesday 23 December 2003 10:37 am, Steven Edwards wrote: > --- "Dimitrie O. Paun" <[EMAIL PROTECTED]> wrote: > > On December 23, 2003 09:03 am, Vincent Béron wrote: > > > Not really. The problem in that case is that winemaker thinks every > > > resource file needs to be compiled independantly, when there's > > > > really > > > > > only one to compile in that case (as it includes the other ones). > > > > Fundamental problem is that winemaker just can't be so smart to > > guess a perfect Makefile. I suggest you just write one manually, > > and use winegcc to build, this way your Makefile is portable > > between Wine and MinGW. > > If you want to adapt Winamp3 to Winelib it might be better to do like > Dimi suggests and use Mingw first. Jose Francesca (I butcher'd his > name) wrote a script called dsw2mak.awk that will create Mingw > makefiles from MS_VC projects. If you can get Winamp to build under > Mingw then converting the makefile to Winelib should be a short > process. > > Thanks > Steven > > > __ > Do you Yahoo!? > New Yahoo! Photos - easier uploading and sharing. > http://photos.yahoo.com/
Re: newbie wine developer question
Hi, On Tue, Dec 23, 2003 at 06:31:40PM +, Zimler Attila wrote: > 2) I would like to fix some fixme (which I can reproduce), but I don't > understand a lot of thins. (I'm new to wine, but not new to C). Could > somebody help me to start involved in the development process? Please mention several specific FIXMEs that you'd like to work on. That's the best way to help you get started. Andreas Mohr
Easy IE installer script
Hi everyone, I thought I'd let the list know that I wrote an easy IE installer program, for those times when only explorer will do. On a Wine CVS build, no windows install, it installs pretty much perfectly, and it does run (stability is so so :). It'll also put a nice menu entry in your menus if your desktop uses the standard mechanism. The installer program contains a few things that may or may not be redistributable - for instance, it contains MSVCRT40.DLL and MFC40.DLL, both of which are available for free from dll-files.com so it seemed to make sense to include them. It also includes the Tahoma font, which IE installs anyway, but I install it first because current Wine seems to enjoy picking BitStream Vera Mono which doesn't look too good and causes UI layout problems. You can get it from here: http://bylands.dur.ac.uk/~mh/install-ie6.run Just download and run it, like so: sh install-ie6.run It contains a Linux Winelib DSO program (for figuring out your linux windows drive path), so may or may not work on other platforms. Do people think this should be linked to from WineHQ? It's a pretty common question in #winehq. enjoy, thanks -mike
Re: newbie wine developer question
> 1) Should I report fixme's in bugzilla? (I guess, not, > but I'm not sure). That's correct, please don't. It would polute Bugzilla, and they are much easily accessible via grep :) > 2) I would like to fix some fixme (which I can > reproduce), but I don't understand a lot of thins. The simplest way is to send patches, ask specific questions, resend patches, ... etc. We'll be glad to help. -- Dimi.
newbie wine developer question
Hi, Since I'm new in developing wine please forgive me if I ask a question that is answered earlier (I tried to search an answer for my questions, but I did not found.) 1) Should I report fixme's in bugzilla? (I guess, not, but I'm not sure). 2) I would like to fix some fixme (which I can reproduce), but I don't understand a lot of thins. (I'm new to wine, but not new to C). Could somebody help me to start involved in the development process? Attila ZIMLER
Re: Console problem
Michael Stefaniuc wrote: Hi, On Mon, Dec 22, 2003 at 08:11:28PM +0100, Peter Oberndorfer wrote: I'm trying to get the freeware version of IDA (console) working, but if you mean ida37fw? My experience is based on that one. I tried freeware version 4.1 It was previously avaliable at http://www.datarescue.be/downloadfreeware.htm but they stopped distributing it. It still can easily be found on the web as idafree.zip i run it in wine it just hangs. If i run it with winedbg it works fine. I found out that the problem is that AllocConsole is never called for the application if it is being run from wine. You can run it like this: wineconsole -- --backend=user IDA.EXE This will create the initial console too. If you want to change the settings of the wineconsole just right click on it. This will bring you IDA up and running (the time displayed in the upper right corner gets updated every second) but keyboard/mouse input does NOT work. This seems to be due to the emulated hardware interrupts not being dispatched. After some minutes i get err:int:TIMER_TimerProc DOS timer has been stuck for 60 seconds... The timer interrupt being int0 and having the highest priority it's blocking the processing of int1 (keyboard). From the trace i see that DOSVM_QueueEvent never signals the VM86 thread because there are always pending request with higher priority. As i didn't had too much time lately and my DOS skills aren't that good i didn't got to dig deeper into the problem. Using wineconsole -- --backend=user idaw.exe works perfectly beside special charachters used to draw frames appear as rectangles. Thanks for this tip. Maybe the problem you are experiencing only occours with the older version of IDA. bye michael greetings Peter
Re: Winelib Program with DLL problem
"Boaz Harrosh" <[EMAIL PROTECTED]> wrote:
> } imports = {
> {
>.
> /* foo.dll */
> "\001\000fnFooC",
> "\002\000fnFooSTD",
> 0,
>
>
>
> change to :
>
>
>.
> /* foo.dll */
> "\001\000fnFooC",
> "[EMAIL PROTECTED]",
> 0,
>
>
>
> than compilation and runtime succeeds.
> So the fault is at winebuild (when doing the Import, since the .def file
> had it right) . Or is there a switch missing?
No, that's not a winebuild problem. You have fixed names directly in the
imports, that means that your dll is broken, i.e. it has decorated (@xx)
API names in the exports.
> I have at hand the most simple dll compiled by VC6 (+sources) and the
> winelib app any one wants to have a look?
Yes, please send it here if it really small, otherwise send it to me directly.
(Comress with 'bzip -9' before sending).
--
Dmitry.
Re: winemine2 winelib example
--- "Dimitrie O. Paun" <[EMAIL PROTECTED]> wrote: > On December 23, 2003 09:03 am, Vincent Béron wrote: > > Not really. The problem in that case is that winemaker thinks every > > resource file needs to be compiled independantly, when there's > really > > only one to compile in that case (as it includes the other ones). > > Fundamental problem is that winemaker just can't be so smart to > guess a perfect Makefile. I suggest you just write one manually, > and use winegcc to build, this way your Makefile is portable > between Wine and MinGW. If you want to adapt Winamp3 to Winelib it might be better to do like Dimi suggests and use Mingw first. Jose Francesca (I butcher'd his name) wrote a script called dsw2mak.awk that will create Mingw makefiles from MS_VC projects. If you can get Winamp to build under Mingw then converting the makefile to Winelib should be a short process. Thanks Steven __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
Re: Winelib Program with DLL problem
Kevin is right on all accounts. I can reproduce his problems here.
If I go to the foo.spec.c file produced by winebuild for the user
application and manually change, at the big "import" structure, all the
stdcall functions than it works. An example is do.
What was produced by winebuild:
static struct {
struct {
void*OriginalFirstThunk;
unsigned int TimeDateStamp;
unsigned int ForwarderChain;
const char *Name;
void*FirstThunk;
} imp[11];
const char *data[109];
} imports = {
{
.
/* foo.dll */
"\001\000fnFooC",
"\002\000fnFooSTD",
0,
change to :
.
/* foo.dll */
"\001\000fnFooC",
"[EMAIL PROTECTED]",
0,
than compilation and runtime succeeds.
So the fault is at winebuild (when doing the Import, since the .def file
had it right) . Or is there a switch missing?
If I understood correctly the process that is done on windows. Than all
the searching and converting of Names is done by the VC linker. Hence
the fix should be done at winebuild.
In windows an: " int __stdcall fnFooSTD(long ,long) declaration linked
against an import-lib of a DLL. Will look and successfully link both
fnFooSTD (in-case a .DEF file was used in compilation of the DLL) or
[EMAIL PROTECTED] (Needless to say that an ordinal will replace a name if
Flagged by the import-lib). winebuild successfully understood that an
[EMAIL PROTECTED] should make an fnFooSTD symbol for GCC (at the
"asm(".data\n) section) but forgot to keep the real [EMAIL PROTECTED] name for
the import-table. Any one with a quick hand at the winebuild?
I have at hand the most simple dll compiled by VC6 (+sources) and the
winelib app any one wants to have a look?
Please forgive me if this was already fixed since I have an old Wine (2
month old)
Free Life
Boaz
Kevin Atkinson wrote:
On Mon, 22 Dec 2003, Kevin Atkinson wrote:
On Mon, 22 Dec 2003, Boaz Harrosh wrote:
I have stdcall working fine here.
There is something wrong with your DLL the fact that "pexports" dumped
"_" before symbol names is a clue to those functions been exported as
cdecl. In stdcall (or PASCAL) no under-scored is perpended. (and you
should see the @number at end of names). check to see how this DLL was
compiled on windows (or wine). Was it compiled with a .DEF file?
The DLL was compiled with Visual C++ without the .def file. Um, if it is
cdecl why is the @ at the end of the names. The DLL works just fine when
linked with a mingw compiled executable.
Also, when I make it cdecl there is NO underscore.
Recombining the DLL with gcc is NOT an option.
Re: winemine2 winelib example
On December 23, 2003 09:03 am, Vincent Béron wrote: > Not really. The problem in that case is that winemaker thinks every > resource file needs to be compiled independantly, when there's really > only one to compile in that case (as it includes the other ones). Fundamental problem is that winemaker just can't be so smart to guess a perfect Makefile. I suggest you just write one manually, and use winegcc to build, this way your Makefile is portable between Wine and MinGW. -- Dimi.
Re: winemine2 winelib example
Le mar 23/12/2003 à 08:34, Steven Edwards a écrit : > --- Chris Morgan <[EMAIL PROTECTED]> wrote: > > I'm not sure what the issue is with En.rc, I've compared it against > > other > > resource files and it looks quite similar. > > There are a few bugs in the resource handling of wrc. If you check > wine-patches from about a week ago I sent in a few patches for comdlg32 > and winmm to be compatible with windres and RC from MSVC. It is > possible the problems you are seeing are related. Not really. The problem in that case is that winemaker thinks every resource file needs to be compiled independantly, when there's really only one to compile in that case (as it includes the other ones). Vincent
Re: winemine2 winelib example
--- Chris Morgan <[EMAIL PROTECTED]> wrote: > I'm not sure what the issue is with En.rc, I've compared it against > other > resource files and it looks quite similar. There are a few bugs in the resource handling of wrc. If you check wine-patches from about a week ago I sent in a few patches for comdlg32 and winmm to be compatible with windres and RC from MSVC. It is possible the problems you are seeing are related. Thanks Steven __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
Re: wine bugs in win.c
> "kscho" == kscho <[EMAIL PROTECTED]> writes: kscho> Hi~ I'm interested in wine. and find some bug... window's kscho> caption is optional, but current is not. kscho> wine/windows/win.c kscho> line 1087 /* Correct the window style - stage 2 */ Your contribution is appreciated. But better read http://www.winehq.com/site/sending_patches It make's the patch easier to integrate. Bye -- Uwe Bonnes[EMAIL PROTECTED] Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt - Tel. 06151 162516 Fax. 06151 164321 --
Re: MinGW cross compilation enviroment setup
Just a side note, if we are at the subject. One can download the full package of "MinGW Developer Studio" (http://www.parinya.ca) It comes complete with a compiled tool chain. The Installer runs flawlessly under wine. And so is the Dev-Studio and the compiler. (1:0) for wine. The only thing that does not work is MinGW-gdb. One day I intend to check this code out and fix this area on wine. Michael Stefaniuc wrote: Hello! Here are the steps needed to setup a MinGW on a Red Hat Linux like rpm based system (Fedora Core, Mandrake Linux, ... should probably work even on a SuSE Linux) * Download the mingw-binutils and mingw-gcc srpm's from http://ftp.redhat.com/pub/contrib/libc6/SRPMS/ * Download the mingw-3.0-1.src.rpm srpm from http://ftp.redhat.com/pub/contrib/libc6/noarch/SRPMS/ * Build the mingw and mingw-binutils rpm's (rpmbuild --rebuild $SRPM) and install them. * After the above step you can build the mingw-gcc rpm too. Install it. * That's almost everything: you need this patch for wine's configure to make it find your mingw binaries. * For instructions how to build the Wine tests for Windows see the Wine Documentation. You may want to try your local Red Hat mirror for the above srpm's. This info can be found also on http://people.redhat.com/mstefani/wine/ Hope this helps bye michael
