Gert van den Berg wrote: > On Mon, Dec 7, 2009 at 19:47, doh123 <wineforum-user@xxxxxxxxxx> wrote: > > > and look at all the options you have... you can specify MANY things. Â I have no idea which all ones will suit your needs because I just don't have enough information... you can put many many flags on a ./configure though. Â I'd recommend at minimum to set a prefix on it, and to do a "make install" at the end to install to that prefix... something like this. > > > > > > Code: > > > > ./configure --prefix=/Applications/Wine --disable-win16 > > make depend > > make > > make install > > > > this will make Wine build for, and install to running in /Applications/Wine > > There are also many other --without commands you can see o the help, to build without things you don't need. > > > > he wants to package it... So just installing it is probably not the > best method. (configuring for a custom directory and the installing it > might work though....) (--prefix=~/my_wine for example) > (a 'make tarball' kind of command would have been handy...) except he can easily right click the Wine folder here and hit "compress" makes a transportable zip, throw it on any other Mac's /Applications folder, double click the zip... and its there on the other machine... not totalyl sure there wont be permission problems though, which is why I like using things in .apps, they get special permissions, helps make it more transportable. if he wants a full install program, he can use the package maker that comes with Xcode, and make an installer from the install....
