wine users - Oct 2011 - Getting started with porting to Mac OSX

Hi all, I'm your newest member, a software author of a few Windows apps.  

I've been wanting for years to somehow get them working on the Mac (and
possibly Linux depending on demand) without a major rewrite, and it looks like
Wine may be just what I'm been looking for.

I've read what introductory info I can find but I'm still trying to get
my head around how the whole thing works and how I would set it up.  Some
answers to the following would be much appreciated to get me started:

1. Do I build with static Wine libraries (or source) to produce a native Mac
binary?  Or do I build a regular Windows exe and then it runs against Wine
dynamic libraries to simulate the expected Windows API environment on the Mac?

2. Does the build process have to happen on a Mac, and if so what compiler?  Or
can I build on Windows with Visual Studio in a special Wine configuration to
create a Mac executable that I copy across?

3. Can you point me to any guides or info that specifically describes the
process and considerations for porting Windows apps to Mac for developers?

Wine directly runs Windows apps.  Since its yet to be perfected, it may help to
modify your source code some to make sure it works with Wine 100%, but that all
depends on your program and what it uses.

Wine itself isn't a porting tool... in that it doesn't make Mac versions
of programs.  It is just a way to run Windows programs without Windows.

You may want to look at Winelib (which I am no expert on) which is more of a
porting tool part of Wine.
http://www.winehq.org/docs/winelib-guide/index

For the Mac, you may want to look at Wineskin (http://wineskin.doh123.com/)
(which is my own project) which I design around actually making a finished and
distributable Mac app.  This doesn't use Winelib, but normal Wine.  Its a
bundled up app with everything needed to run the Windows program installed into
it.