The app structure is the best for OSX, and easy to move around and work, just throw it on any machine in any folder and double click and run the app, just like its a native OSX app.... but if you just want a folder with wine in it, that works too. if you build it on the same OS version you want to run it on, and just move it and run it under X11.app... thats not hard at all. Any library missing on the other machine that is needed, that Wine was compiled against, you will figure out pretty easy when you actually try to move it and run it, it will give errors about missing libraries... then you know to add those libraries in. build wine to a custom prefix... when you build it, so you get just the files you need for wine, not a bunch of extra junk... you can do this with the --prefix command on ./configure. if yours is 400mb your getting a bunch of extra stuff. full wine build should be around 100mb... less if you disable a bunch of stuff in configure you don't need. If it complains about not being able to find certain libraries, just make a launch script that adds in DYLD_FALLBACK_LIBRARY_PATH to the folders of any libraries it complains about... so if it doesn't find them, it will check where you told it to check.