Hi,
As some of you might remember I'm the lead developer of the Odin project. (project for OS/2 with the same goals as Wine). Odin is partly based on Wine code. The core dlls (gdi32, user32, kernel32) + some special dlls (winmm, directx, winsock) use some Wine code, but is basically incompatible with Wine for obvious reasons. Most of the remaining dlls are based entirely on Wine code.
The last few years there has been little cooperation between both projects for several reasons. One of them is that we have far fewer active developers and cooperation sometimes proved to be difficult. Some source files of the two project had grown apart since changes were never merged back into Wine.
Now, I'm trying to change this situation, but am wondering how to proceed. I can post bug fixes to this list, but it will be difficult for me to actually test these changes in Wine itself. (too time consuming) Posting diff files is not always possible due to the major differences between source files.
Merging changes from Wine into our source tree is no problem. We can do that ourselves. However, it would be nice if compiler incompatibilites (we use IBM VisualAge C++, not GCC) could be resolved. There aren't many, but the IBM compiler is not always as flexible as GCC and of course doesn't understand any GCC extensions. It would be a big help if incompatible code could be changed. Switching compilers is not an option for us. I can post a (small) list of changes we had to make.
The license of our project is not compatible with Wine, but the dlls that are largely based on Wine (such as comctl32, shell32, ole) are an exception to the project license. The sources of those dlls are released under the Wine license. In case there is ever interest in the other sources, then you can just ask me. I'd be happy to 'donate' them to Wine.
For more information about Odin you can visit http://odin.netlabs.org (some information is outdated though). There you can find out where to download the sources (cvs).
The next post from me will contains some patches for bugs in Wine that I've recently found.
Sander
On Wed, 26 Dec 2001 12:28:09 +0100 (CET), you wrote:
For more information about Odin you can visit http://odin.netlabs.org (some information is outdated though). There you can find out where to download the sources (cvs).
I have one silly question about this. The cvs server address is guest@www.netlabs.org:d:/netlabs.src/odin32, but the current version of the linux cvs client is rejecting the DOS drivespec in it:
| cvs login: CVSROOT (":pserver:guest@www.netlabs.org:d:/netlabs.src/odin32") | cvs login: may only specify a positive, non-zero, integer port (not "d:"). | cvs login: perhaps you entered a relative pathname?
and I have not been able to find a way to make it accept it. Is there a way to use linux cvs client with Odin's server?
Rein.
On Wed, 26 Dec 2001 17:25:50 +0100, Rein Klazes wrote:
For more information about Odin you can visit http://odin.netlabs.org (some information is outdated though). There you can find out where to download the sources (cvs).
I have one silly question about this. The cvs server address is guest@www.netlabs.org:d:/netlabs.src/odin32, but the current version of the linux cvs client is rejecting the DOS drivespec in it:
First of all, the path is incorrect. I thought this was updated, but apparently not. The current path is e:/netlabs.cvs/odin32
| cvs login: CVSROOT (":pserver:guest@www.netlabs.org:d:/netlabs.src/odin32") | cvs login: may only specify a positive, non-zero, integer port (not "d:"). | cvs login: perhaps you entered a relative pathname?
and I have not been able to find a way to make it accept it. Is there a way to use linux cvs client with Odin's server?
Sorry, I can't help you with that. I never tried this with a linux cvs client.
Sander