Winelib and windows.h

chrismcb · Post by **chrismcb** » Sun May 04, 2008 9:30 am

I installed winelib and ran winemaker on my project.
But running the makefile fails because it doesn't know where windows.h (or any other the other windows includes are)

How do I resolve this issue? Am I supposed to set the include path to windows.h on my windows drive?

vitamin · Post by **vitamin** » Sun May 04, 2008 12:35 pm

chrismcb wrote:I installed winelib and ran winemaker on my project.
But running the makefile fails because it doesn't know where windows.h (or any other the other windows includes are)

How do I resolve this issue? Am I supposed to set the include path to windows.h on my windows drive?

Winelib is not enough. You'll need whole Wine.

chrismcb · Post by **chrismcb** » Sun May 04, 2008 4:03 pm

As far as I know I got the whole wine.
I followed the wine installation instructions at http://www.winehq.org/site/download-deb

I've followed the instructions http://www.winehq.org/site/docs/winelib ... ng-started in how to port my project over. (there isn't much to it)

I've read all of the documentation that can I find. And nothing mentions doing anything to point the Include variable, or where to point it to. Or what to do so windows.h and other system includes can be found.

vitamin · Post by **vitamin** » Sun May 04, 2008 5:20 pm

chrismcb wrote:As far as I know I got the whole wine.
I followed the wine installation instructions at http://www.winehq.org/site/download-deb

I've followed the instructions http://www.winehq.org/site/docs/winelib ... ng-started in how to port my project over. (there isn't much to it)

I've read all of the documentation that can I find. And nothing mentions doing anything to point the Include variable, or where to point it to. Or what to do so windows.h and other system includes can be found.

Include dirs would be "/usr/include" or "/usr/lib/wine/includr". Not sure you really need to look at where packages put that stuff.

Honestly if you consider porting your application to Linux winelib would be the bad choice. It ties your application to specific Wine version and impose number of restrictions. The most significant - you still have to run your program through Wine. It will not be a standalone app.

What is more suggested is to:
1. Make your application work properly under Wine by fixing Wine.
2. Write 100% native port of your application.

1) gives you an advantage of having same codebase for all OSes. 2) allows you to use OS specific features and better system integration.

chrismcb · Post by **chrismcb** » Sun May 04, 2008 7:45 pm

#2 is never going to happen.

I don't understand #1. What is broken in Wine? Or rather what is broken in Wine, that would work using winelib.

So what is the advantage of rebuilding using winelib?

Dan Kegel · Post by **Dan Kegel** » Sun May 04, 2008 7:51 pm

On Sun, May 4, 2008 at 5:45 PM, chrismcb <[email protected]> wrote:

I don't understand #1. What is broken in Wine?

Try running your app and find out.

Or rather what is broken in Wine, that would work using winelib.

Nothing. Winelib is wine.

So what is the advantage of rebuilding using winelib?

It's useful if you want to target non-x86 versions of Linux.
For instance, sparc, powerpc, or arm.

If all you want to target is x86, you're better off just running
your Windows app untouched under Wine, I think.
- Dan