HACKING 1.8 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546
  1. If you want to hack on the GIMP project, it will make you life easier
  2. to have the following packages installed:
  3. - GNU autoconf 2.13
  4. - GNU automake 1.4
  5. - GNU libtool 1.2d
  6. - GNU gettext 10.38
  7. Available in ftp://alpha.gnu.org/gnu
  8. These should be available by ftp from prep.ai.mit.edu or any of the
  9. fine GNU mirrors. Beta software can be found at alpha.gnu.org.
  10. If you are accessing gimp via CVS, then you will need to take several
  11. steps to get it to compile. You can do all these steps at once
  12. by running:
  13. cvsroot/gimp# ./autogen.sh
  14. Basically this does the following for you:
  15. cvsroot/gimp# aclocal; automake; autoconf
  16. The above commands create the "configure" script. Now you
  17. can run the configure script in cvsroot/gimp to create all
  18. the Makefiles.
  19. Before running autogen.sh or configure, make sure you have libtool
  20. in your path. Also make sure gtk.m4 is in the same --prefix relative
  21. to your automake installation.
  22. Note that autogen.sh runs configure for you. If you wish to pass
  23. options like --prefix=/usr to configure you can give those options
  24. to autogen.sh and they will be passed on to configure.
  25. Please submit patches to the gimp-developer@scam.xcf.berkeley.edu mailing
  26. list. All kinds of contributions are accepted. Patches that you wish to go
  27. into the distribution should also be uploaded to ftp://ftp.gimp.org/incoming.
  28. Follow the rules there for naming your patches.
  29. Please notice that some files in the source are generated from other sources.
  30. Among these are the files ending in _pdb.[ch] in the libgimp directory
  31. and the files ending in _cmds.c in the app subdirectory. Those are generated
  32. from the respective .pdb files in tools/pdbgen/pdb. All those files have a
  33. short notice about being autogenerated somewhere at the top.