Re: Script to compile Wine programs on Windows

2003-09-30 Thread Dimitrie O. Paun
On September 29, 2003 03:33 pm, Alexandre Julliard wrote: No it won't, that's why we need to change bin2res to generate only a single file at a time, otherwise it breaks parallel makes. OK, how about this: ChangeLog Teach bin2res to deal with one file at a time. Index: tools/bin2res.c

Re: Script to compile Wine programs on Windows

2003-09-29 Thread Alexandre Julliard
Dimitrie O. Paun [EMAIL PROTECTED] writes: The only complication here is the .extract file which allows us to split the dependencies from the rules. The complicated stuff are the dependencies, but you need those anyway. A simple marker file is a small price to pay for the convenience... If

Re: Script to compile Wine programs on Windows

2003-09-29 Thread Alexandre Julliard
Dimitrie O. Paun [EMAIL PROTECTED] writes: All that to avoid a dummy file?!? But anyway, you did not answer my question :) Can you describe what you have in mind, like giving an example of how you want to handle it, so I can better understand where you're comming from? To take comctl32 as an

Re: Script to compile Wine programs on Windows

2003-09-29 Thread Dimitrie O. Paun
On Mon, 29 Sep 2003, Alexandre Julliard wrote: We need a way for bin2res to extract a single file for this to work right. And yes, it only works if all the binaries are in a single rc file which happens to be the main rc file, otherwise you need to write multiple rules manually. Right, this

Re: Script to compile Wine programs on Windows

2003-09-29 Thread Steven Edwards
I am still lacking the need to have this script. If someone really wants to build parts of WINE on Windows we should really only support MSYS+Mingw or MS_VC. I dont think there are that many people that want to build WINE programs that need extra help. I can try to write better documentation for

Re: Script to compile Wine programs on Windows

2003-09-28 Thread Martin Fuchs
On Sun 28. September 2003 04:23, Alexandre Julliard wrote: Martin Fuchs [EMAIL PROTECTED] writes: I tried to compile my explorer as winelib application, and got to this problem: How to compile a resource file, which has no problems with RC or WINDRES with WRC? If it compiles with rc and

Re: Script to compile Wine programs on Windows

2003-09-28 Thread Alexandre Julliard
Martin Fuchs [EMAIL PROTECTED] writes: I was not aware of that because I always got WRC error messages like explorer_intres.rc:337:58: Error: Cannot handle UNICODE filenames when using IDI_EXPLORERICONDISCARDABLE res/explorer.ico Now I tried once more and found this

Re: Script to compile Wine programs on Windows

2003-09-27 Thread Martin Fuchs
On Wed 24. September 2003 06:08, Dimitrie O. Paun wrote: Some resource files refer to icons if __WINE__ is not defined. The icons are missing. Perhaps those references can be removed. Alternatively, icon resources should be converted to the binary format in Wine. I don't know if the

Re: Script to compile Wine programs on Windows

2003-09-27 Thread Alexandre Julliard
Martin Fuchs [EMAIL PROTECTED] writes: I tried to compile my explorer as winelib application, and got to this problem: How to compile a resource file, which has no problems with RC or WINDRES with WRC? If it compiles with rc and windres then it should compile with wrc too. The inline stuff

Re: Script to compile Wine programs on Windows

2003-09-24 Thread Dimitrie O. Paun
On September 24, 2003 03:47 am, Pavel Roskin wrote: I have looked at winegcc source and it seems it will greatly improve portability. I think it's a good idea to switch to winegcc first. Thoose who compile large projects with Wine are not likely to abandon the Windows version, so it's

Re: Script to compile Wine programs on Windows

2003-09-24 Thread Richard Cohen
Pavel Roskin wrote: I have looked at winegcc source and it seems it will greatly improve portability. I think it's a good idea to switch to winegcc first. Provided you don't care about delay-loading libraries, you can already compile the programs with winegcc. Here's the patch -- Richard diff

Re: Script to compile Wine programs on Windows

2003-09-24 Thread Alexandre Julliard
Dimitrie O. Paun [EMAIL PROTECTED] writes: I'm not sure why we had those defines in there. In general, we try to avoid defines like the plague in the Wine tree, so your patch is much appreciated. It seems that was some code the initial developers had in there for their own testing, and

Re: Script to compile Wine programs on Windows

2003-09-24 Thread Dimitrie O. Paun
On Wed, 24 Sep 2003, Alexandre Julliard wrote: No, it's here so that you can compile with other resource compilers that don't support having binary data inline. It could be changed to #ifdef __WRC__ though. Are there such beasts? I didn't know this is a Wine extension... But even if it is,

Re: Script to compile Wine programs on Windows

2003-09-24 Thread Pavel Roskin
On Wed, 24 Sep 2003, Steven Edwards wrote: Most of it should already build under Cygwin as cygwin1b apps. just $ ./configure make tools cd dlls make The difference is that I'm compiling Wine programs without Wine libraries, let alone DLLs. Only a very limited set of libraries is compiled

Re: Script to compile Wine programs on Windows

2003-09-24 Thread Alexandre Julliard
Dimitrie O. Paun [EMAIL PROTECTED] writes: Are there such beasts? I didn't know this is a Wine extension... But even if it is, one thing we can do is to integrate the bin2res into the build process. We can place the embedded data inside comments, and run bin2res before compiling an .rc file.

Re: Script to compile Wine programs on Windows

2003-09-24 Thread Alexandre Julliard
Dimitrie O. Paun [EMAIL PROTECTED] writes: Well, dependencies are not a problem: I can modify bin2res to output the name of the dependencies, and then 'make depend' can include them just like it does with the others... I don't really see how you would do that, especially not to make it do the

Re: Script to compile Wine programs on Windows

2003-09-23 Thread Dimitrie O. Paun
On September 23, 2003 11:02 pm, Pavel Roskin wrote: The attached script makes it possible to compile many programs from Wine under Windows. The only software needed on Windows is Cygwin with MinGW libraries and some other utilities (flex, bison). Simply run setup.exe from www.cygwin.com and

Re: Script to compile Wine programs on Windows

2003-09-23 Thread Pavel Roskin
On Tue, 23 Sep 2003, Dimitrie O. Paun wrote: On September 23, 2003 11:02 pm, Pavel Roskin wrote: The attached script makes it possible to compile many programs from Wine under Windows. The only software needed on Windows is Cygwin with MinGW libraries and some other utilities (flex,

Re: Script to compile Wine programs on Windows

2003-09-23 Thread Dimitrie O. Paun
On September 23, 2003 11:59 pm, Pavel Roskin wrote: For example, winefile.exe needs -luuid in MinGW because it provides IID_IDataObject. In Wine, IID_IDataObject is defined in include/objidl.h and a constant number. Wine doesn't have uuid library. We have one, and it's called wine_uuid