gtk+及相关依赖包介绍

Requirements

Packages

You will need to get the GLib,cairo,Pango,ATK,and GTK+ developer packages to build against GTK+. To run GTK+ programs you will also need the libpng and zlib packagages,and if your code uses gettext for internationalisation and/or you want GTK+ internalisation,the gettext-runtime package.
The packages here are for people who develop software that uses GTK+. This page is not intended directly for end-users. It is expected that people who build installers for GTK+ applications for Windows bundle GTK+ with them.
These packages are not for developing or running programs that use the Cygwin Unix emulation environment. Cygwin has GTK+ packages available directly in its installer which you should use. Note that the Cygwin GTK+ uses the X11 backend,so you will need to also run an X11 server then when you run GTK+ programs on Cygwin,but presumably that is what Cygwin users want.
You are welcome to redistribute GTK+ binaries,including applications that bundle them,on other web sites,CD-ROM,and other media. You don't have to ask for permission. That's one of the points of Free Software. One important thing that the GNU licenses require is that you must also redistribute the source code. This usually means at least the gettext,GLib,GTK+,Pango and Atk sources.

What toolchain to use?

The most natural toolchain to use together with these packages would probably be the GNU compiler and other utilities. When targeting Windows,that combination is known as MinGW Using Cygwin tools to build non-Cygwin Windows binaries is not recommended unless you are very careful and look out for mixups.
It is possible to use these packages also with Microsoft's compiler. However,the DLLs use the msvcrt.dll runtime library. This means that also applications that use the DLLs should preferrably use the msvcrt.dll runtime. Specifically,this means that you should not use newer versions of the Microsoft compiler than Visual C++ 6 without knowing exactly what you are doing.

Which Windows versions?

The current GTK+ stack uses APIs that are available only on Windows 2000 or later. Long obsolete versions of GTK+ did run on Win9x and NT 4,too.

Stable Release

There are 3 types of download options below. Binaries provide only the DLLs and other files used you will need to run your GTK+-using application. Dev packages provide include files,import libraries,documentation and additional tools. Source packages provide the source code for the component in question.
If you want to repackage the necessary runtime files together with your application into an installer,you can choose to leave out for instance message catalogs for languages that your application isn't localised to anyway.

All-in-one bundle

If you find choosing,downloading and unpacking the individual zip archives below a chore,here is an all-in-one

bundle
of the GTK+ stack including 3rd-party dependencies. This bundle contains both binaries and a lot of developer files,many of which are irrelevant to most developers. If you intend to redistribute the GTK+ run-time,you need to figure out which files you can leave out yourself. A new bundle will be provided whenever one of the packages it consists of is updated.

GTK+ individual packages

Package Version Downloads
GLib 2.20.0

Binaries

Dev

Sources
GTK+ 2.16.0

Binaries

Dev

Sources
Pango 1.24.0

Binaries

Dev

Sources
ATK 1.24.0

Binaries

Dev

Sources
cairo 1.8.6

Binaries

Dev

Sources

Third Party Dependencies

You won't need all of these packages to just use GTK+ Some of the optional packages are needed for building applications like GIMP on Windows. Required packages are illustrated with

.
Package Version Downloads
zlib 1.2.3

Binaries & Dev

win_iconv 20080320

Dev & Sources

GNU libiconv 1.9.1

Binaries & Dev

Sources

win_iconv DLL 20080320

Binaries & sources

gettext-runtime 0.17

Binaries

Dev

Sources

libpng 1.2.34

Binaries

Dev
-

libjpeg 6b

Binaries

Dev
-

libtiff 3.8.2

Binaries

Dev
-

pkg-config 0.23-2

Tool binaries

Sources

Freetype 2.3.6

Binaries

Dev

Sources

Fontconfig 2.4.2

Binaries

Dev

Source
&

Patch

libexpat 2.0.0

Binaries
- -

dirent - -

Dev
-

proxy-libintl 20080918

Binaries & sources

About libpng

This is an image file format library used by GTK+,and required.
The libpng package linked to above provides libpng12-0.dll. This package is built by me (Tor Lillqvist). Previously the GTK+ stack was built against the gnuwin32 build of libpng. Confusingly,gnuwin32's older builds of libpng provided libpng13.dll,and their newer builds provided libpng12.dll. I don't know whether these builds actually are binary compatible even if the DLL name was different. To be safe,never rename DLLs.

About zlib

This is the compression library used by libpng,libjpeg and libtiff.

About win_iconv

win_iconv is an implementation of iconv for Windows by Yukihiro Nakadaira that has a much smaller footprint than GNU libiconv. The win_iconv package above includes the header file,static archive library and the source file. This library is linked statically into GLib and thus not needed separately at run-time.

About iconv.dll

GLib 2.12.4 and earlier link to iconv in a separate DLL,iconv.dll. This can either be the GNU libiconv iconv.dll,or the identically named win_iconv_dll one which obviosuly is intented to be a drop-in replacement.

About gettext

The GNU internationalization library. All of the GTK+ stack uses it,but through proxy-libintl (see below) so it is actually optional at run-time.

About libjpeg and libtiff

These libraries are used by the gdk-pixbuf library in GTK+,and for instance by GIMP.

About pkg-config

This program is useful for Makefiles and configure scripts and extensively used in building software according to the GTK+ and GNOME conventions using autotools. It uses a database specifying inter-dependencies among software packages. It is used to get the compile and link flags needed when building software using libraries that provide pkg-config data. This requires GLib 2.x.

About freetype

This is used by GIMP and by Pango's pangoft2 library. For just GTK+ applications you will not need it.

About fontconfig

Fontconfig is used by the FreeType2 backend in Pango (pangoft2) and by GIMP. Contrary to what many seem to think,fontconfig is in no way dependent on X11,so it does make some sense to use it on Windows. GTK+ does not use pangoft2,so you probably will not need this unless for GIMP. This is a slightly fixed version of fontconfig 2.4.2 from the date indicated.

About libexpat

This is required by fontconfig.

About dirent

This is the public domain implementation of dirent.h from MinGW. It is needed by Microsoft Visual C++ users that want to compile GLib. Not directly related to GLib.

About proxy-libintl

proxy-libintl is a very small static library. It acts as a proxy for the intl.dll from gettext-runtime,loading it dynamically,and failing gracefully. Fallback dummy functions are used if intl.dll isn't found. It is a static archive and the intent is to start linking this into the binaries in the GTK+ stack instead of referring directly to intl.dll. This enables application packagers to leave out the gettext-runtime binaries if they don't need or want to support i18n,without having to build own versions that don't use intl.dll.
When building DLLs against the proxy-libintl static library and using the GNU linker's auto-export feature (i.e. not using a .def file,and not using __declspec(dllexport)),it is a good idea to pass the -Wl,--exclude-libs=libintl.a in your LDFLAGS so that the libintl functions don't get exported from your DLL.



[url]http://www.gtk.org/download-windows.html[/url]

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


什么是设计模式一套被反复使用、多数人知晓的、经过分类编目的、代码 设计经验 的总结;使用设计模式是为了 可重用 代码、让代码 更容易 被他人理解、保证代码 可靠性;设计模式使代码编制  真正工程化;设计模式使软件工程的 基石脉络, 如同大厦的结构一样;并不直接用来完成代码的编写,而是 描述 在各种不同情况下,要怎么解决问题的一种方案;能使不稳定依赖于相对稳定、具体依赖于相对抽象,避免引
单一职责原则定义(Single Responsibility Principle,SRP)一个对象应该只包含 单一的职责,并且该职责被完整地封装在一个类中。Every  Object should have  a single responsibility, and that responsibility should be entirely encapsulated by t
动态代理和CGLib代理分不清吗,看看这篇文章,写的非常好,强烈推荐。原文截图*************************************************************************************************************************原文文本************
适配器模式将一个类的接口转换成客户期望的另一个接口,使得原本接口不兼容的类可以相互合作。
策略模式定义了一系列算法族,并封装在类中,它们之间可以互相替换,此模式让算法的变化独立于使用算法的客户。
设计模式讲的是如何编写可扩展、可维护、可读的高质量代码,它是针对软件开发中经常遇到的一些设计问题,总结出来的一套通用的解决方案。
模板方法模式在一个方法中定义一个算法的骨架,而将一些步骤延迟到子类中,使得子类可以在不改变算法结构的情况下,重新定义算法中的某些步骤。
迭代器模式提供了一种方法,用于遍历集合对象中的元素,而又不暴露其内部的细节。
外观模式又叫门面模式,它提供了一个统一的(高层)接口,用来访问子系统中的一群接口,使得子系统更容易使用。
单例模式(Singleton Design Pattern)保证一个类只能有一个实例,并提供一个全局访问点。
组合模式可以将对象组合成树形结构来表示“整体-部分”的层次结构,使得客户可以用一致的方式处理个别对象和对象组合。
装饰者模式能够更灵活的,动态的给对象添加其它功能,而不需要修改任何现有的底层代码。
观察者模式(Observer Design Pattern)定义了对象之间的一对多依赖,当对象状态改变的时候,所有依赖者都会自动收到通知。
代理模式为对象提供一个代理,来控制对该对象的访问。代理模式在不改变原始类代码的情况下,通过引入代理类来给原始类附加功能。
工厂模式(Factory Design Pattern)可细分为三种,分别是简单工厂,工厂方法和抽象工厂,它们都是为了更好的创建对象。
状态模式允许对象在内部状态改变时,改变它的行为,对象看起来好像改变了它的类。
命令模式将请求封装为对象,能够支持请求的排队执行、记录日志、撤销等功能。
备忘录模式(Memento Pattern)保存一个对象的某个状态,以便在适当的时候恢复对象。备忘录模式属于行为型模式。 基本介绍 **意图:**在不破坏封装性的前提下,捕获一个对象的内部状态,并在该
顾名思义,责任链模式(Chain of Responsibility Pattern)为请求创建了一个接收者对象的链。这种模式给予请求的类型,对请求的发送者和接收者进行解耦。这种类型的设计模式属于行为
享元模式(Flyweight Pattern)(轻量级)(共享元素)主要用于减少创建对象的数量,以减少内存占用和提高性能。这种类型的设计模式属于结构型模式,它提供了减少对象数量从而改善应用所需的对象结