Wine 1.2 rc1

[lfchisholm]

trying to install this new release and got this message.
I tried to locate the dev. pkgs but no luck.
yum install did not bring back anything.
also tried to search on Fedora to loacate them to install but no luck.
any help would be appreciated.
Larry

checking for X... no
configure: error: X development files not found. Wine will be built
without X support, which probably isn't what you want. You will need to install
development packages of Xlib/Xfree86 at the very least.
Use the --without-x option if you really want this.

[Gert van den Berg]

On Sun, May 23, 2010 at 16:53, lfchisholm <[email protected]> wrote:

trying to install this new release and got this message.
I tried to locate the dev. pkgs but no luck.
yum install did not bring back anything.
also tried to search on Fedora to loacate them to install but no luck.
any help would be appreciated.
Larry

checking for X... no
configure: error: X development files not found. Wine will be built
without X support, which probably isn't what you want. You will need to install
development packages of Xlib/Xfree86 at the very least.
Use the --without-x option if you really want this.

You're trying to compile Wine...

If this is what you want to do, see here:
http://wiki.winehq.org/Recommended_Packages

What you probably want: http://fedoraproject.org/wiki/AndreasBierfert/Wine

Gert

[lfchisholm]

Thank you Gert
perhaps I should wait a couple of weeks as wine should release a new version on June 8th and Fedora will be on final 13 release.
Larry

[Gert van den Berg]

On Sun, May 23, 2010 at 19:41, lfchisholm <[email protected]> wrote:

Thank you Gert
perhaps I should wait a couple of weeks as wine should release a new version on June 8th and Fedora will be on final 13 release.
Larry

The Fedora packages does seem out of date...

Compiling Wine is not so hard once you've got all the packages
installed (If you are running 64-bit Fedora, note that there is a
separate page with instructions for 64-bit Linux...)

You basically need to install lots of -devel packages... (I'm not
running fedora, the Wiki (linked in previous post) is probably a much
better source as to which ones..)

Once that is installed, it should compile quite easily... (I prefer to
skip "make install" and to run Wine directly from where it was
compiled...)

Also, when compiling Wine, it might be worth figuring out how to get
the source from git, since it allows you to test a up-to-the-minute
version of Wine (and the downloads for upgrades are smaller.) There is
a wiki page with some information (GitWine AFAIK). (For the first few
times, I would stick to the tar downloads...)

Gert

[David Gerard]

On 24 May 2010 06:10, Gert van den Berg <[email protected]> wrote:

Compiling Wine is not so hard once you've got all the packages
installed (If you are running 64-bit Fedora, note that there is a
separate page with instructions for 64-bit Linux...)
You basically need to install lots of -devel packages... (I'm not
running fedora, the Wiki (linked in previous post) is probably a much
better source as to which ones..)
Once that is installed, it should compile quite easily... (I prefer to
skip "make install" and to run Wine directly from where it was
compiled...)

Yep. Compiling Wine is very easy. It just takes a few hours to compile

Also, when compiling Wine, it might be worth figuring out how to get
the source from git, since it allows you to test a up-to-the-minute
version of Wine (and the downloads for upgrades are smaller.) There is
a wiki page with some information (GitWine AFAIK). (For the first few
times, I would stick to the tar downloads...)

Do it with the tarball to make sure you have all the prerequisites.

But the nice thing about Wine from git is that you can do regression
testing if your Windows app stops working. And regression testing and
bisecting - tracking down the *precise* commit that broke your stuff -
is really pretty easy with git, if you're comfortable with a command
line.


- d.

[Gert van den Berg]

On Mon, May 24, 2010 at 11:47, David Gerard <[email protected]> wrote:

Yep. Compiling Wine is very easy. It just takes a few hours to compile

Not (the second time) with ccache, make -j5 and a quad core...
(Running Gentoo when buying CPU was main reason for the choice...)

Wine is quite large though, it takes several times longer than the
Linux kernel to compile... (Not sure if user-focused configure options
is documented somewhere that compiles it without developer focused
parts (like tests, etc))

Gert

[Sven]

On Mon, May 24, 2010 at 11:47, David Gerard <[email protected]> wrote:

Yep. Compiling Wine is very easy. It just takes a few hours to compile

Not (the second time) with ccache, make -j5 and a quad core...
(Running Gentoo when buying CPU was main reason for the choice...)

Wine is quite large though, it takes several times longer than the
Linux kernel to compile... (Not sure if user-focused configure options
is documented somewhere that compiles it without developer focused
parts (like tests, etc))

Gert

Like --disable-tests?

I compile wine every day after make distclean with make -j 2 btw, and it only takes a few minutes for me.

[dj--alex]

compiling with Phenom X955 @ 3.5Ghz it take about 40 minutes

[DL]

GCC 4.3+ with -ftree-vectorization speeds up compile times a lot, in my experience. My compiles only take around 8 minutes with a Pentium [email protected] (Core 2 Duo with less cache)

[DL]

GCC 4.3+ with -ftree-vectorization speeds up compile times a lot, in my experience. My compiles only take around 8 minutes with a Pentium [email protected] (Core 2 Duo with less cache)

A bit of a typo there: The flag is actually -ftree-vectorize.

[lfchisholm]

Gert
Not sure you will read this but I am trying to install wine-1.2-rc3
I am running Suse 10.2 32bit
I extracted the file into the download folder
I cd until I got into the tools folder and was in the user logon
I then did a ./wineinstall and it prompted to install as root I answered yes
got down to the question about make install answered yes
then it completed ok.
am I now at a point that if I want to start wine I will have to use command line?
also do I have to run winecfg?
I read and search faq's and it seems there are so many bits and pieces that don't seem to put the whole process into one list of install instructions for tar files.
thank you
Larry

[dimesio]

am I now at a point that if I want to start wine I will have to use command line?
also do I have to run winecfg?

http://wiki.winehq.org/FAQ#head-83998f2 ... 80c8f22b0b
You don't need to run winecfg unless you want to change any of the default settings.

[Gert van den Berg]

On Tue, Jun 15, 2010 at 15:05, lfchisholm <[email protected]> wrote:

then it completed ok.
am I now at a point that if I want to start wine I will have to use command line?

You might want to use /usr/local/bin/wine to start Wine, to ensure
that the version you compiled is being run...

(I prefer not to install it (but I only compile the git version
myself) and run it with /path/to/source/wine (It allows you to easily
keep multiple versions lying around...))

Gert