mirror of https://github.com/GNOME/gimp.git
dddcdb42c6
... when building on Windows. From bug 780270, comment 18: I'm still having issue with Windows MinGW, but I have traced the issue with the autoconf itself, and the autoconf-archive script "ax_prog_cc_for_build.m4". I have written to the autoconf-archive mailing list. It seem that this script never worked as intended since a long time because the way it works, it pushdef a few elements, then it disable cross-compiling (for the following test), and invoke AC_PROG_CC (which in turn invoke the code that find and set the exe extention). Then it grab the BUILD_EXEEXT from that. This is neat and simple, but the issue is that the autoconf AC_PROG_CC macro only invoke the code that is responsible for finding the exe (and obj) extensions once (with m4_expand_once). So, the end-result is that in the resulting configure script, EXEEXT is properly evaluated, but when comes the time to evaluate BUILD_EXEEXT, no test is performed to actually find the exe (and obj) extension, even if the cross-compilation option changed (which is the case for the duration of this test). So, BUILD_EXEEXT will always end up blank (defined, but blank). |
||
|---|---|---|
| app | ||
| build | ||
| cursors | ||
| data | ||
| desktop | ||
| devel-docs | ||
| docs | ||
| etc | ||
| icons | ||
| libgimp | ||
| libgimpbase | ||
| libgimpcolor | ||
| libgimpconfig | ||
| libgimpmath | ||
| libgimpmodule | ||
| libgimpthumb | ||
| libgimpwidgets | ||
| m4macros | ||
| menus | ||
| modules | ||
| plug-ins | ||
| po | ||
| po-libgimp | ||
| po-plug-ins | ||
| po-python | ||
| po-script-fu | ||
| po-tags | ||
| po-tips | ||
| themes | ||
| tools | ||
| .dir-locals.el | ||
| .gitignore | ||
| .kateconfig | ||
| AUTHORS | ||
| COPYING | ||
| ChangeLog.pre-1-0 | ||
| ChangeLog.pre-1-2 | ||
| ChangeLog.pre-2-0 | ||
| ChangeLog.pre-2-2 | ||
| ChangeLog.pre-2-4 | ||
| ChangeLog.pre-2-6 | ||
| ChangeLog.pre-git | ||
| HACKING | ||
| INSTALL.in | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile.am | ||
| NEWS | ||
| NEWS.pre-2-0 | ||
| NEWS.pre-2-2 | ||
| NEWS.pre-2-4 | ||
| NEWS.pre-2-6 | ||
| NEWS.pre-2-8 | ||
| README | ||
| README.i18n | ||
| acinclude.m4 | ||
| authors.dtd | ||
| authors.xml | ||
| authors.xsl | ||
| autogen.sh | ||
| config.h.win32 | ||
| configure.ac | ||
| gimp-zip.in | ||
| gimp.doap | ||
| gimp.pc.in | ||
| gimpthumb.pc.in | ||
| gimpui.pc.in | ||
README
------------------------------
GNU Image Manipulation Program
2.9 Development Branch
------------------------------
This is an unstable development release, an intermediate state on the
way to the next stable release 2.10. GIMP 2.9 may or may not do what
you expect. Save your work early and often. If you want a stable
version, please use GIMP 2.8 instead.
GIMP 2.9 replaces earlier GIMP 2.x versions. It is advised that you
uninstall them before installing GIMP 2.9. If you want to keep your
older GIMP 2.x installation in parallel to GIMP 2.9, you have to
choose a separate prefix which is not in your default library search
path. Otherwise your previous GIMP installation will start to use the
new libraries. You have been warned.
If you think you found a bug in this version, please make sure that it
hasn't been reported earlier and that it is not just new stuff that is
still being worked on and obviously not quite finished yet.
If you want to hack on GIMP, please read the file HACKING. For
detailed installation instructions, see the file INSTALL.
1. Web Resources
================
GIMP's home page is at:
http://www.gimp.org/
Please be sure to visit this site for information, documentation,
tutorials, news, etc. All things GIMP-ish are available from there.
The automated plug-in registry is located at:
http://registry.gimp.org/
There you can get the latest versions of plug-ins, using a convenient
forms-based interface.
The latest version of GIMP can be found at:
http://www.gimp.org/downloads/
2. Mailing Lists
================
We have several mailing lists dedicated to GIMP user and development
discussion. There is more info at
http://www.gimp.org/mail_lists.html
Links to several archives of the mailing lists are included in that page.
Gimp-user-list is a mailing list dedicated to user problems, hints and
tips, discussion of cool effects, etc. Gimp-developer-list is oriented
to GIMP core and plug-in developers. Gimp-gui-list is for discussing
about GIMP interface to improve user experience. Most people will only
want to be subscribed to gimp-user-list. If you want to help develop
GIMP, the gimp-developer mailing list is a good starting point; if you
want to help with GUI design, the gimp-gui list is where you want to
subscribe.
3. IRC
======
And finally, for the real junkies, there is an IRC channel devoted to
GIMP. On GIMPNet (a private free software oriented network) there is
#gimp. Many of the developers hang out there. Some of the GIMPNet
servers are:
irc.gimp.org:6667
irc.us.gimp.org:6667
irc.eu.gimp.org:6667
4. Customizing
==============
The look of GIMP's interface can be customized like any other GTK app
by editing the ~/.gtkrc-2.0 file or by using "themes" (ready-made
customizations). For downloadable themes and further details, see
http://art.gnome.org/themes/gtk2 . Additionally, GIMP reads the file
~/.config/GIMP/2.9/gtkrc so you can have settings that only apply to GIMP.
Included is a set of keybindings similar to those in Adobe Photoshop.
You can find them in the ps-menurc file. To use them, copy this file
to ~/.config/GIMP/2.9/menurc. You can also manually change the keybindings to
any of your choice by editing ~/.config/GIMP/2.9/menurc.
Have fun,
Spencer Kimball
Peter Mattis
Federico Mena
Manish Singh
Sven Neumann
Michael Natterer
Dave Neary
Martin Nordholts