Prepare for coding sprint - BrentBaccala/Singular GitHub Wiki

Here we tried to list some tools/packages/setup-configurations that might be helpful during the coding-sprint.

Strongly recommended:

• master and SW git check-outs and builds (simultaneously): see Building Singular from source

Assumed:

• the usual build chain (gcc/clang, autotools, libtoolize, make/gmake etc)
• git
• editor, diff

Additional (for SW-related git repository):

• own github forks of Singular/Sources for exchanging code pushing & sending pull requests
• added TC remote repository for testing

Note: one might require github and TC accounts for some tasks

see also Development model

Helpful:

• git GUI, e.g. qgit, sourcetree, tig or see http://git-scm.com/downloads/guis
• sdiff (belongs to diffutils) or vimdiff or kdiff3 or meld or p4merge or windiff etc.

Extra (only for testing and debugging the differences between 32-bit and 64-bit builds):

• 32-bit build (for 64 native OS/builds)

Note: this requires configuring, building 32-bit versions of GMP, NTL/FLINT, Python2, readline etc... (e.g. configured with CFLAGS=-m32 CXXFLAGS=-m32 LDFLAGS=-m32) and installing them locally (say under $ROOT32). SW may than be configured, for example, as follows:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ROOT32/lib ./configure --with-gmp=$ROOT32 --with-ntl=$ROOT32 CFLAGS=-m32 CXXFLAGS=-m32 'LDFLAGS=-m32 -L$ROOT32/lib' PKG_CONFIG_PATH=$ROOT32/lib/pkgconfig/ --with-python=$ROOT32/bin/python2.7