1 Nov
2008
1 Nov
'08
5:17 a.m.
I have in the past written one script per version of
Ubuntu to install Wine's build dependencies.
Many versions on, that's getting old, and I figure
it'd be better to have a single script that handles
all common versions on Linux.
I've taken a first stab at that, combining my scripts
for gutsy and hardy, and adding ibex. The result is at
http://winezeug.googlecode.com/svn/trunk/install-wine-deps.sh
If anyone wants to add support to that script for another
OS, please do, and send me the patch.
I'd like to see this in the wine tree sometime. It's
kind of silly we have to direct people to a big,
confusing wiki page (or set of them) to explain
how to install the needed packages; let's just
have a unified script and be done with it.
2 Nov
2 Nov
7:32 a.m.
Dan Kegel wrote:
I have in the past written one script per version of
Ubuntu to install Wine's build dependencies.
Many versions on, that's getting old, and I figure
it'd be better to have a single script that handles
all common versions on Linux.
I've taken a first stab at that, combining my scripts
for gutsy and hardy, and adding ibex. The result is at
http://winezeug.googlecode.com/svn/trunk/install-wine-deps.sh
If anyone wants to add support to that script for another
OS, please do, and send me the patch.
I'd like to see this in the wine tree sometime. It's
kind of silly we have to direct people to a big,
confusing wiki page (or set of them) to explain
how to install the needed packages; let's just
have a unified script and be done with it.
Bonus points if you somehow manage to use packagekit.
Thanks,
Scott Ritchie
3:03 p.m.
On Sat, Nov 1, 2008 at 11:32 PM, Scott Ritchie <scott(a)open-vote.org> wrote:
Bonus points if you somehow manage to use packagekit.
I s'pose, but because the package names change from
distro to distro, it wouldn't add that much portability,
would it?
3 Nov
3 Nov
4:46 a.m.
Dan Kegel wrote:
On Sat, Nov 1, 2008 at 11:32 PM, Scott Ritchie
<scott(a)open-vote.org> wrote:
Working around that issue is the whole point of packagekit ;)
Thanks,
Scott Ritchie
Bonus points if you
somehow manage to use packagekit.
I s'pose, but because the package names change from
distro to distro, it wouldn't add that much portability,
would it?
5:07 a.m.
Bonus points if you
somehow manage to use packagekit.
I s'pose, but because the package names change from
distro to distro, it wouldn't add that much portability,
would it? 
2 Nov
2 Nov
4:31 p.m.
I can see where this would be useful for building on some platforms, but
doesn't "sudo apt-get build-dep wine" work fine (for the most part) for
Ubuntu?
The last time I compiled on a fresh *buntu, I recall using build-dep and
then having to install one nvidia-specific '-dev' package to get DirectX
support working. I think it was nvidia-glx-177-dev; Until it added some
headers or whatnot, ./configure insisted it was going to build without
DirectX.
As far as specific tweaks: on Intrepid Ibex I don't believe x-dev or
qt3-dev-tools are required. X-dev's a transitional package only
dependent on x11proto-core-dev, which is already in your list. I don't
have qt3-dev-tools installed (and everything compiles/runs clean).
-J
Dan Kegel wrote:
I have in the past written one script per version of
Ubuntu to install Wine's build dependencies.
Many versions on, that's getting old, and I figure
it'd be better to have a single script that handles
all common versions on Linux.
I've taken a first stab at that, combining my scripts
for gutsy and hardy, and adding ibex. The result is at
http://winezeug.googlecode.com/svn/trunk/install-wine-deps.sh
If anyone wants to add support to that script for another
OS, please do, and send me the patch.
I'd like to see this in the wine tree sometime. It's
kind of silly we have to direct people to a big,
confusing wiki page (or set of them) to explain
how to install the needed packages; let's just
have a unified script and be done with it.
4:41 p.m.
On Sun, Nov 02, 2008 at 10:31:11AM -0600, Evil Jay wrote:
I can see where this would be useful for building on
some platforms, but
doesn't "sudo apt-get build-dep wine" work fine (for the most part) for
Ubuntu?
The last time I compiled on a fresh *buntu, I recall using build-dep and
then having to install one nvidia-specific '-dev' package to get DirectX
support working. I think it was nvidia-glx-177-dev; Until it added some
headers or whatnot, ./configure insisted it was going to build without
DirectX.
As far as specific tweaks: on Intrepid Ibex I don't believe x-dev or
qt3-dev-tools are required. X-dev's a transitional package only
dependent on x11proto-core-dev, which is already in your list. I don't
have qt3-dev-tools installed (and everything compiles/runs clean).
Same for RPM building, just one "rpm -i wine-.....src.rpm" will also request
necessary dependencies. Afterwards you can deinstall the wine-...src.rpm again.
Ciao, Marcus
6:08 p.m.
On Sun, Nov 2, 2008 at 8:41 AM, Marcus Meissner <marcus(a)jet.franken.de> wrote:
Same for RPM building, just one "rpm -i
wine-.....src.rpm" will also request
necessary dependencies. Afterwards you can deinstall the wine-...src.rpm again.
Again, I'm aiming at having something independent of,
and perhaps upstream of, the list that the packagers
maintain.
6:03 p.m.
On Sun, Nov 2, 2008 at 8:31 AM, Evil Jay <wine(a)eternaldusk.com> wrote:
I can see where this would be useful for building on
some platforms, but
doesn't "sudo apt-get build-dep wine" work fine (for the most part) for
Ubuntu?
I don't trust that.
The last time I compiled on a fresh *buntu, I recall
using build-dep and
then having to install one nvidia-specific '-dev' package to get DirectX
support working. I think it was nvidia-glx-177-dev; Until it added some
headers or whatnot, ./configure insisted it was going to build without
DirectX.
See? In general, I would like install-build-deps.sh to be
independent of the people who package wine. Think of
it as perhaps the upstream of build-dep.
As far as specific tweaks: on Intrepid Ibex I
don't believe x-dev or
qt3-dev-tools are required. X-dev's a transitional package only
dependent on x11proto-core-dev, which is already in your list. I don't
have qt3-dev-tools installed (and everything compiles/runs clean).
Hmm, I'm not really sure how the qt stuff snuck in there.
I guess libqt3-mt-dev was in the build deps when I started.
I'll try removing all the qt stuff and see what happens.
- Dan
5678
days inactive
5680
days old
8 comments
4 participants
participants (4)
-
Dan Kegel -
Evil Jay -
Marcus Meissner -
Scott Ritchie