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

Re: wxWindows + building from source in Debian



Dave Howorth wrote:
On Friday 17 October 2003 16:13, I wrote:

| >>I need to install wxWindows 2.4 on a Woody system so I can build
| >>another application (TreeView X).  Does anybody have any idea of the
| >>best way to do this, and what steps are involved?


I haven't built Debian-ised software from source before (except a kernel). It seems a lot more complicated than just downloading the upstream package and building it.

Thankfully Derrick 'dman' Hudson replied:

$ apt-get source libwxgtk2.4
$ cd [wx...]    # whatever the directory is called
$ fakeroot ./debian/rules binary
$ su
# dpkg -i ../libwxgtk2.4*.deb

You'll definitely need the "lib" package to run that other app.
You'll need the -dev package (or maybe it's called wxwin2.4-headers)
to compile that other app.


I suspect I need both the -dev and the -headers but when I did the apt-get it looked to me like it downloaded the same package three times.

I tried the fakeroot command but it just sat there so I looked in the Debian Reference and tried

wxwindows2.4-2.4.1.2# dpkg-buildpackage -us -uc

(I'm running as root so I left out the -rfakeroot). It ran but produced failed dependencies:

dpkg-buildpackage: source package is wxwindows2.4
dpkg-buildpackage: source version is 2.4.1.2
dpkg-buildpackage: source maintainer is Ron Lee <ron@debian.org>
dpkg-buildpackage: host architecture is i386
dpkg-checkbuilddeps: Unmet build dependencies: libgtk1.2-dev, python (>=2.3), python2.3-dev, libpng2-dev, libtiff3g-dev, xlibmesa-gl-dev | libgl-dev, xlibmesa-glu-dev | libglu-dev, libesd0-dev
dpkg-buildpackage: Build dependencies/conflicts unsatisfied; aborting.

Which leaves me with a general question and a specific one.

The general question is why the dependencies weren't picked up when I did the apt-get source? And is there in principle a general way to resolve them or do I have to apt-get them all individually.

Because you may be downloading it for a reason other than to build it.
If you already have the necesseray -dev libraries and headers installed
(say, from upstream and Debian doesn't see them) you can pass -d to
dpkg-buildpackage, which will just ignore the build dependencies.  But
that will probably cause parts of the build to fail, since the
libraries will be missing.  Just apt-get the necessary packages.

The specific question is why these particular dependencies are arising. It's asking for python but I didn't ask for the Python interface (libwxgtk2.4-python) [and it wants a version of Python I don't have since I'm on Woody] and it's asking for GL support though GL support is an optional feature of wxWindows that I don't believe is needed by the application I actually want to use (it's a feature of the python interface, though). So I'd like to eliminate the need for those dependencies rather than upgrade python and who knows what else.

wxWindows 2.4 is very recent, and requires some newer libraries. Try
editing the debian/rules file in the package and edit out the part
for the packages you don't want.  To disable OpenGL support, just
remove each instance of the --with-opengl or --enable-opengl (can't
remember which it is) from the debian/rules files.

All suggestions gratefully received.

Thanks, Dave

HTH,

-Roberto

Attachment: pgpAecwyk0UoV.pgp
Description: PGP signature


Reply to: