wine-devel December 2004

wine-devel@winehq.org

127 participants
276 discussions

Wine book
by Brian Vincent 04 Dec '04

04 Dec '04

Just wanted to give everyone a heads up.. I followed up with Jeremy's email a few months ago about a publisher wanting to put together a book on Wine. Yep, I have no life and 400 pages can't be that hard to write. Well, we started the ball rolling and now it looks like it's going to happen. I should be signing the contract in a few days. There's lots of details I thought you guys might be interested in. You'll find the chapter outlines[1] at the bottom of this email. This book is oriented at users and Winelib developers. It's not a book about how to hack Wine internals. One thing I'll try to keep in mind as I'm writing is how to entice people to get involved with development. I think it's important to try to get people involved in the community. I'm not going to be writing this alone. Ira Krakow, a Boston native, will be writing the Winelib parts. I didn't feel comfortable doing those and Ira had approached the publisher separately about doing a book on porting Windows apps. We've chatted a few times and I'm confident that given his experience he'll do well. I'm cc:ing him on this email by way of introduction and I'm sure at some point in the future he'll have a question or two (or 50.) The publisher is Prentice-Hall. Thus far they've been excellent to work with and they really seem to just "get it" when it comes to open source projects. Specifically, this book will fall into their Bruce Perens' Open Source Series [2]. After the book is published, it will be available for a short time only in a dead tree version. After a few months it will be available under the Open Publication License [3]. It's a good license and contains many things I think are important. Also, I'd like to thank everyone who reviewed the initial proposal. That process happened really fast and I wasn't even aware it had been sent out for review until after you guys got the emails. There was lots of good feedback in there and I incorporated a lot of it in the final proposal that got approved (you may even notice some changes in the chapters below as a result.) Some other things you guys mentioned aren't specifically in this chapter outline, but I made some notes as to what needs to be addressed. Thanks again. Anyone who didn't see that proposal, you didn't miss much. It was lots of marketspeak. The key is the chapter outline below, so if you have any comments about what I'm overlooking, _please_ let me know. [1] Chapter outlines: Title: "Wine: Running Windows Applications on Linux" [4] 1. Wine Introduction[15 pages] What is Wine? How Can Wine Help You? An Introduction to Windows Components Overview of Wine's Components Recent Changes to Wine A History of the Wine Project How Can You Get Wine? 2. Installing Wine [20 pages] System Requirements Bundled Versions Downloading Packaged Versions Accessing CVS Compiling and Installing Wine Uninstalling Wine 3. Configuring Wine [35 pages] Introduction to Winecfg Windows Versions Libraries: Native vs. Builtin Application Settings Drive Configuration Serial and Parallel Ports Network Shares Fonts Printing Database Access 4. Installing Applications [35 pages] Basic Installation Common Installation Pitfalls Resources to Help With Installation Adding Native Libraries Installing Games Copy Protection Pitfalls Using Native DirectX 5. Installing Common Programs [35 pages] Microsoft Office Adobe Photoshop File Utilities Peer-to-Peer Applications Further Help: The Wine Application Database 6. Linux, Wine, and Windows Integration [40 pages] Integrating with Desktop Environments KDE and GNOME Integration Wine Tools Introduction Wineshelllink Wineprefixcreate Regedit Understanding the Wine Registry Changing the Registry Importing an Existing Registry Using an Existing Windows Partition 7. Enterprise Deployment [30 pages] Licensing Considerations Understanding Windows and Wine Security Automating Deployment of Applications Scripting Wine Citrix Killer: Wine and the Linux Terminal Server Project Performance Tweaks Reporting Bugs and Working with Developers 8. Commercial Alternatives: CodeWeaver's CrossOver Office [25 pages] Introduction to CrossOver Office Downloading and Installing CrossOver Configuring CrossOver Installing Applications with CrossOver 9. Commercial Alternatives: TransGaming's Cedega [25 pages] Introduction to Cedega Downloading and Installing Cedega Configuring Cedega Installing Games with Cedega 10. Introduction to Winelib [20 pages] Introduction to Winelib Licensing Considerations Portability Considerations Getting Started Understanding the Winelib toolkit A Roadmap for Porting Installation of the MinGW Compiler 11. Using Winelib for Porting [45 pages] Installation of the MinGW compiler Moving From Visual Studio to MinGW Tips and Tricks for Changing Compilers Moving Development to Linux Using Winemaker Using the Wine Resource Compiler Using the Wine Message Compiler Linking it Together: winegcc Debugging with the Wine debugger 12. Case Study: Porting a To-Be-Determined Application [30 pages] 13. Advanced Porting Techniques [25 pages] C++ Problems Working with Microsoft Foundation Classes Working with Templates Moving From Visual Studio to MinGW 14. dvanced Library Techniques [20 pages] Getting Started: Why Share Libraries? Using Linux Libraries with Winelib Applications Using Windows Libraries with Winelib Applications Why Wine is not a Shared Library [2] Peren's Open Source Series info: http://phptr.com/promotion/1484?redir=1 [3] OPL license: http://www.opencontent.org/openpub/ a good discussion of it: http://lwn.net/Articles/108250/ [4] With regards to the title, I'll be sure to mention in Wine runs on other operating systems. PS. This still leaves the door open for someone to write an O'Reilly book. PPS. I'd like to think this won't affect WWN because I really have no life. However, that's not too realistic. Hopefully WWN won't suffer too much. - Brian Vincent

7 9

Re: [resend] shell32 tests
by Rolf Kalbermatter 04 Dec '04

04 Dec '04

>+static HMODULE hshell32; >+static int (WINAPI *pSHCreateDirectoryExA)(HWND, LPCSTR, LPSECURITY_ATTRIBUTES); >+ >+static void InitFunctionPointers(void) >+{ >+ hshell32 = GetModuleHandleA("shell32.dll"); >+ >+ if(hshell32) >+ pSHCreateDirectoryExA = (void*)GetProcAddress(hshell32, "SHCreateDirectoryExA"); >+} >+ > /* creates a file with the specified name for tests */ > void createTestFile(CHAR *name) > { >@@ -398,17 +409,19 @@ > int ret; > > set_curr_dir_path(path, "testdir2\\test4.txt\0"); >- ret = SHCreateDirectoryExA(NULL, path, NULL); >+ ret = pSHCreateDirectoryExA(NULL, path, NULL); I think this is not right. Implementing dynamic loading of functions in tests is supposedly because that function may not be available on some systems. But here you invoke the (maybe uninitialized, or NULL assigned) function pointer nevertheless without protecting for this. As such your patch does only allow loading the test on such systems but will create a nice crash when run. Rolf Kalbermatter

1 0

2nd attemp at DllCanUnloadNow
by James Hawkins 03 Dec '04

03 Dec '04

This time I respect heap-based objects, leaving there internal ref counts and respective HeapFree's. I also took Alexandre's suggestions and changed Un/LockServer to DMCOMPOS_LockServer etc and change cLocks to refCount. Let me know if this is any closer to what it needs to be. Thanks. -- James Hawkins

2 1

Re: Wine book
by Ivan Leo Puoti 03 Dec '04

03 Dec '04

> The 'high level' parts (like d3drm) should work too, No program or sdk sample I know of and uses this dll currently works on wine. Ivan. ____________________________________________________________ Libero ADSL: 3 mesi gratis e navighi a 1.2 Mega, senza costi di attivazione. Abbonati subito su http://www.libero.it

2 1

03 Dec '04

On windows xp/2k the IME window class appears to be always registered, even if a program doesn't link to nor loads imm32, the class is registered. How should this be handled in wine, should the class be registered at startup? Ivan. ____________________________________________________________ Libero ADSL: 3 mesi gratis e navighi a 1.2 Mega, senza costi di attivazione. Abbonati subito su http://www.libero.it

1 0

Re: wine-preloader defunct
by James Hawkins 03 Dec '04

03 Dec '04

On Thu, 02 Dec 2004 20:01:48 -0800, Kenneth Porter <shiva(a)sewingwitch.com> wrote: > I've now got several instances of "[wine-preloader] <defunct>" in my ps > listing from a game server that's died in some strange way. Anyone have > experience in clearing these short of bouncing the whole box? They're > holding onto a couple of TCP ports that I'd like to use. The ports are > stuck in CLOSE_WAIT, because the processes are stuck in memory so the > sockets can't close. > > Does 'kill -9 processnum' not work? -- James Hawkins

6 10

Re: Implement GetLayout
by Shachar Shemesh 03 Dec '04

03 Dec '04

Rémi Assailly wrote: > I added some things to my previous patch. > Please tell me if something seems incorrect or is missing > Thanks ;) > > Changelog: > * implement GetLayout Thanks for spotting another one for my growing heap of BiDi TODOs.... http://bugs.winehq.org/show_bug.cgi?id=2584 Shachar -- Shachar Shemesh Lingnu Open Source Consulting ltd. http://www.lingnu.com/

2 1

Re: rsaenh/implglue.c: Added missing break
by Marcus Meissner 03 Dec '04

03 Dec '04

On Fri, Dec 03, 2004 at 11:49:22AM +0100, Michael Jung wrote: > Greetings, > Michael > > Changelog: > Added a missing break in encrypt_block_impl > > Index: dlls/rsaenh/implglue.c JFYI, we (Novell) are now working on reapproving WINE for US export due to your cryptographic library import. I will keep you posted, but I expect approval. Actually, in the closest meaning of the export regulations, I am not even allowed to build RPMs for SourceForge anymore here at SUSE/Novell :( Fun without end, I had hoped we keep openssl dynamic linking ;) Ciao, Marcus

2 2

Providing success stories
by Stefan Munz 03 Dec '04

03 Dec '04

Hi, I already mailed with some developers a few days ago. Basicly wether and in which way the wine logo can be used to communicate wine compatibility for software producers (this is already solved). For those who didn't read it, i copied a passage of the orig. mail: --- In order to push the use of Open Source Software we plan a project with the "Wirtschaftsförderung Region Stuttgart GmbH" (I don't know whats the equivalent in english but its a public organization that promotes OSS and assists companies that resident in Stuttgart). Within this project we want to find software producers who pay us for a wine compatibility test of their software. --- This project is starting at the moment. I thought a good idea to give something back to the community is to provide some success stories i.e. for use on winehq.com. Is this interesting? If the answer is yes, who is responsible for something of the kind. Regards, Stefan Munz

1 0

Preliminary Darwine SDK Released
by Sanjay Connare 03 Dec '04

03 Dec '04

Hello All, I have released a preliminary version of the Darwine SDK version 0.1. Many people are interested in getting Darwine up and running so they can compile programs on OS X and this release should satisfy their curiosity. The SDK features the following: -source code for the current Darwine binary 20040820 -source code for WineHelper -Xcode Integration -Xcode Template -Updated Uninstaller The Xcode integration allows for a user to compile windows source code from within the Xcode IDE using the wine tools. Users may want to note that there are some changes to the way Darwine is installed and functions. Due to limitations in Xcode, the wine source tools such as winegcc, winemaker, winebuild are installed in the /usr/bin directory and not the /Library/Darwine/bin directory. This may be changed in a future release but was necessary so Xcode integration would work correctly. As a result there is an updated uninstaller as well. The uninstaller will remove everything except for the Xcode project template folder, which is moved to the trash and needs to be removed manually. To start a new Darwine project, simply launch Xcode, select new project, and select Darwine (Windows) Application. Currently in Xcode the "Build and Run" does not work, it will build the program but not launch. However, the Build button works as expected. When compiling a Darwine application for the first time Xcode may give the error: "ld: table of contents for archive: /Library/Darwine/lib/wine/lib<name>.a is out of date; rerun ranlib(1) (can't load from it)" Open a terminal and type the following command: "sudo ranlib /Library/Darwine/lib/wine/lib<name>.a" <name> being replaced by the name of the library whose table of contents is out of date. The source code should then compile fine. There are many examples of source in the wine source code "programs" folder which is located in the root of the source directory. Simple programs should compile fine. However, bigger programs that depend on more of the windows headers will probably not compile due to header incompatabitlies between the wine and OS X headers. You can download the preliminary release here http://prdownloads.sourceforge.net/darwine/Darwine_SDK0.1.dmg?download or through the Darwine web site http://darwine.opendarwin.org Post any comments, questions or concerns to the Darwine Mailing List "darwine-devel(a)lists.sourceforge.net" . Remember this is a preliminary release and there are many bugs and issues that need to be worked out and features that need to be implemented. More information will be posted on the Darwine website in the near feature. Last but not least enjoy. Sanjay Connare

1 0

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 December 2004