File: DEVELOPERS

package info (click to toggle)
giflib 4.1.6-9
  • links: PTS, VCS
  • area: main
  • in suites: squeeze
  • size: 2,968 kB
  • ctags: 1,009
  • sloc: ansic: 11,186; sh: 9,222; cpp: 907; makefile: 183; sed: 57; perl: 54
file content (29 lines) | stat: -rw-r--r-- 1,111 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
Things to tell developers of libungif....

=======
Build Tools:
libungif presently uses autoconf, automake, and libtool in order to build
shared libraries for a wide variety of platforms.  The distributed tarball has
files prebuilt from these tools.  The cvs repository does not.  If you want to
build libungif you will need to have these tools available.  I currently run
with the following versions:
autoconf 2.57
automake 1.7.8
libtool 1.5

(P.S. I use the autogen.sh script in the top level directory to generate
configure, Makefile.in, etc using these tools.)

=======
cvs:
I currently do my work in a subversion repository.  Since sourceforge is still
using cvs and not subversion, there's nothing in the sourceforge tree.

If someone else wants to do development we can definitely talk about the best
way to share version control access.

=======
I create the distribution tar ball by using the `make dist` command.... After
hacking all I want, I check my sources into cvs, checkout a clean tree, run
./autogen.sh; make dist and then attempt to compile from the libungif-*.tar.gz
file that is generated.