Why is wine not prepackaged on the download site

gat · Post by **gat** » Mon May 26, 2008 4:10 pm

the reason that the x11 for macintosh being broken is insufficient as a cause for not having a package on the download site. the darwine source cvs repository does not carry a version on it. i personally cannot compile the source for my computer. i can install xfree86, though. if this fixes the x11 problem, considering that most people can achieve this, should there not be updated packages along with the other supported operating systems on sourceforge. hopefully by the official 1.0 release this will have happened.

James McKenzie · Post by **James McKenzie** » Mon May 26, 2008 6:37 pm

gat wrote:

the reason that the x11 for macintosh being broken is insufficient as a cause for not having a package on the download site.

The 'brokenness' of X11 on the Mac is NOT the reason that there is no
downloadable version of Wine for the Mac (PowerPC or Intel.) The fact
that the Darwine project is NOT a part of the Wine project is. Thus, if
you want to download a copy of Wine for the Mac, you should visit the
Darwine project or MikesMassiveMess.

the darwine source cvs repository does not carry a version on it.

The Darwine project does not carry Wine source code and the
create_darwine_distrib shell script goes to the Wine repository for Wine
code.

i personally cannot compile the source for my computer.

Details on your computer? What processor does it use and what version
of MacOSX are you using?

i can install xfree86, though. if this fixes the x11 problem, considering that most people can achieve this, should there not be updated packages along with the other supported operating systems on sourceforge. hopefully by the official 1.0 release this will have happened.

Again, which version of MacOSX and what machine type, PowerPC or Intel
are you trying to build Darwine on?

James McKenzie

gat · Post by **gat** » Tue May 27, 2008 10:35 am

Darwine for an intel macintosh computer is actually wine. There is no difference. The project was originally created to use qemu to emulate and allow ppc architectures to use wine. My problem is that the latest compiled wine for osx is on kronenberg's website which is 1.0-rc-1. I was hoping to test some applications on rc-2. The reason that winehq.org lists for not having a binary for mac os x on intels is that there is a problem with the x11 windowing environment that make wine not as great as it could possibly be and that the wine group does not want to give a bad impression of its software. If you search the website you can find it James. As I said before the instructions on compiling for os x from the wine website say to tell the installer the version through the terminal. My problem with this is that I am hasty to believe that this is kept up to date as the new release candidates are.

James McKenzie · Post by **James McKenzie** » Tue May 27, 2008 11:02 pm

gat wrote:

Darwine for an intel macintosh computer is actually wine.

No. I would beg to differ. I build it and you have to do several
things in order to make it work. Wine, out of the build site will not
work properly on the Mac. I tried it, so I should be aware of this
shortcoming. Also, Wine does not support Leopard's DISPLAY variable.
So we have to have workarounds to make it work. One is the
incorporation of freetype and fontforge. The other is using a start
script to set the DISPLAY variable. This makes Wine work.

There is no difference.

Code no, how we build it and run it, yes.

The project was originally created to use qemu to emulate and allow ppc architectures to use wine. My problem is that the latest compiled wine for osx is on kronenberg's website which is 1.0-rc-1. I was hoping to test some applications on rc-2.

I ran into the same problems he did. RC2 will not build on an Intel
Mac, yet. Mike will figure it out and build when ready. For now, use
RC1 and report any problems you find.

The reason that winehq.org lists for not having a binary for mac os x on intels is that there is a problem with the x11 windowing environment that make wine not as great as it could possibly be and that the wine group does not want to give a bad impression of its software.

Your ignorance is showing now. X11 2.2.1 IS the MacIntosh version of
Xorg's 7.2 release. Unlike Tiger, Apple allows this for Leopard. Apple
also installs X11 on a 'bare metal' Leopard install.

If you search the website you can find it James.

I know exactly where it is. I've been using Darwine for a little
while. The version on the Darwine.sourceforge.net is way out of date.
Darwine/PPC has NOT been maintained.

As I said before the instructions on compiling for os x from the wine website say to tell the installer the version through the terminal. My problem with this is that I am hasty to believe that this is kept up to date as the new release candidates are.

This I agree with. Darwine is almost abandonware. The PPC version was
not maintained as Q-kmu has not been maintained. The Intel version was
9.23 or something similar.

The problem is that several 'fixes' for 1.0-rc2 broke the Darwine
build. Mike is responsible for maintaining the build package and he has
not fixed it, yet. As you should be aware, both Mike and I have 'real
lives' and have to do other things with our time. You can assist, if
you wish, by getting the Darwine build package and attempting to build
it yourself. If you can find a workaround to the build breakage, we
both would appreciate it. Darwine, like Wine, is a project we all can
work on to make it better.

James McKenzie

gat · Post by **gat** » Wed May 28, 2008 11:46 am

I use Tiger still.

gat · Post by **gat** » Wed May 28, 2008 12:33 pm

I have free font and such things installed. Wine should still install itself and warn that it will not run properly without them. It should still be able to be installed without the proper fonts, yes? It should tell you where it expects them, and continue the installation. I agree a bundled installation is most beneficial, but since wine officially supports intel macs using Wine then shouldn't it be on the download site. Persons like Kronenberg - I think that is his name. I am assuming from his website - can make a compilation and have a link on Wine's website like the current situation is, but that should be a sidebar from the download page. It feels like intel macs are not really supported for Wine when they are. Most apple computer users I know -persons in my family, and friends, cannot navigate websites well enough to find these, and give up when things are not easily presented to them, like apple presents things on their website. I personally hate what apple says about the macs being unix based, but not having any of the newer linux/unix features and not supporting them. I also hate how programs from generation to generation of os X cannot function, if made for a different version, so often. I try to help my friends by telling them about Wine running windows programs on their macs, but before the wiki had the mac os link so prevalently posted they had trouble understanding what the site was saying and finding resources to help them install it. I realize that I am a poor writer, but I am trying to express that the majority of macintosh computer users that I know barely understand administrative privileges, and have never heard of root. They need an easily found download or they will not reap the benefits of Wine. It is only logical for there to be a download for macs on the download page. What I said earlier about X11 can be found her at http://wiki.winehq.org/MacOSX/FAQs , these are not my words, but information that I found at the Wine website. At the end of the page it states that X11 on the apple operating system is badly broken. The problem with using rc1 is that I do not want to trouble this organization that is aping a whole operating system using a simple server with problems that may have already been fixed. Since as you have stated there is no difference in actual code between the wine program on one operating system in place of another then is it not possibly to add some line to the make scripts to configure the compilation differently when it has detected darwin i386 macintoshs. I do believe it detects that as the operating system when I attempted to compile it myself on my computer. Since the whole purpose of configure scripts is to realize the differences in computers to create make scripts to adjust certain features, files, and what not to make the program function on different settings it is only logical that intel macs eventual become a part of the source installation targets. I understand that import changes and other significant factors are happening to create the infamous version 1.0. Possibly after that Wine will functionally include macs in its source code and download page.