Re: Makeing librsvg work (bizp2.dll missing)
- From: Tor Lillqvist <tml iki fi>
- To: Hartmut Goebel <h goebel goebel-consult de>
- Cc: gtk-app-devel-list gnome org
- Subject: Re: Makeing librsvg work (bizp2.dll missing)
- Date: Tue, 28 Jul 2009 00:32:02 +0300
Because ftp.gnome.org does not provide an installer (which sets the
path, etc.)
Well, setting the PATH system-wide to include where one GTK+ runtime
is installed is really not appropriate because the idea is that each
application bundles an own copy of the GTK+ stack. And what does the
"etc" stand for? The GTK+ stack doesn't require any Registry settings
or whatever.
What I am trying to say is that I really don't believe in the idea of
having a shared, system-wide GTK+ on Windows, and thus I don't see
that the GTK+ stack *by itself* would need an installer. (Sure, *apps*
that bundle it need installers, and for people writing Windows
Installer -based app installers, a merge module could be useful.)
But yeah, there are differing opinions about all that.
Sorry, I mixed it up. bzip2.dll is required by libgsf-1-114.dll. I
downloaded the version from ftp.gnome.org and checked this: Yes,
bzip2.dll is required here, too:
There is also a libbzip2 package on ftp.gnome.org:
http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libbzip2-1.0.2.zip
$ grep -r bzip2 .
Übereinstimmungen in Binärdatei ./bin/libgsf-1-114.dll.
It happened to work this time, but there are more appropriate tools
than grep to use to check for dependencies. objdump -p for instance.
You might get false positives from just a grep. Consider for instance
if there was some error message in a DLL that said "sorry, bzip2
compression not supported" because the DLL in question had not been
built to use any bzip2 library... ;)
--tml
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]