Re: Questions about git and building wine

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



vitamin wrote:
> 
> john.moonsugar wrote:
> > git clone git://source.winehq.org/git/wine.git wine-git
> > cd wine-git
> > 
> > git checkout wine-0.9.59
> > git reset --hard wine-0.9.59
> 
> 
> Both commands with do the same in your case.
> 


Ah! Thank you. I thought that might be the case, as I wasn't making any changes, but it wasn't clear to me if the reset was necessary too.


> 
> john.moonsugar wrote:
> > That looks like what I want. I don't want to overwrite my current wine install, so I add the option "--prefix=/usr/local/wine" to configure,
> 
> The best way to no not overwrite your current version is to not install your compiled version at all. But rather running it from the compile dir. The only side affect is you have to specify fill path to "wine".


That's very handy to know, and it does seem to solve the problem I was having where the command "/usr/local/wine/bin/wine --version" returned 1.1.2 after I'd built and installed 0.9.59. Now when I execute "$HOME/wine/src/wine-git/wine --version" I get 0.9.59, which is what I was expecting. Apparently trying to use a different configure --prefix sent me off on a wild goose chase.

Anyway, it would be great if someone could set up instructions for how to do this specifically oriented towards people who just need to test. All the instructions I've found so far are much more oriented towards people who want to make changes or do patches. If I just overlooked (and I have looked) such instructions, please do point them out. Thanks!






[Index of Archives]     [Gimp for Windows]     [Red Hat]     [Samba]     [Yosemite Camping]     [Graphics Cards]     [Wine Home]

  Powered by Linux