File | Date | Author | Commit |
---|---|---|---|
anitmt | 2020-05-11 |
![]() |
[d76a44] added more build folders in .gitignore |
anitmt-server | 2001-12-02 |
![]() |
[b738fd] schit entfernt |
anivision | 2020-05-04 |
![]() |
[fdf080] fixed static library links for newer automake v... |
doc | 2020-05-05 |
![]() |
[66dfbc] Added circles demo video |
hlib | 2020-05-04 |
![]() |
[4e62c8] get anivision compiling with new gcc/flex++/bis... |
rendview | 2020-05-04 |
![]() |
[4e62c8] get anivision compiling with new gcc/flex++/bis... |
.gitignore | 2020-05-04 |
![]() |
[92f8bc] added README.md for overall repo |
README.md | 2020-05-11 |
![]() |
[f099fa] Fixed some build targets and explain cross-comp... |
AniTMT and AniVision are two animation systems built on top of the raytracer
povray. AniTMT was built by Jan Theofel, Manuel Moser and Martin Trautmann as
a project for the german national competition "jugend Forscht". AniVision was
build by Wolfgang Wieser who met Martin on the german national computer
science competition.
Both systems differ a bit in concept. While AniVision primarily assumes
animation actions that are appended in time, AniTMT includes a solver network
which allows to throw in as many attributes about the movements as you like
and remaining information is calculated or default-setted as needed. In fact
both systems were finally integrated so you can use AniTMT as a description
language within AniVision.
In another way of describing the difference, AniTMT exploits the descriptive
power of a declarative language whereas AniVision allows for more complex
expressions in an imparative style.
The old version has a less meta-programmed description language. However,
after finishing the really cool new meta programming description (in fact we
generate the code that generates code for generating scene descriptions that
generate images) nobody put much energy into developing the animation language
that makes use of all the generating power.
see solver description example.
You can download precompiled packages for many RPM based distributions from
here.
If you like to build the software without rpm spec, you can do this as
follows (make -j4 runs make with 4 processes, you can adjust this as you like):
pushd anitmt
./autogen.sh
mkdir build
cd build
../configure
make -j4
make install
cd -
popd
pushd hlib
./autogen.sh
mkdir build
cd build
../configure
make -j4
make install
cd -
popd
pushd rendview
./autogen.sh
mkdir build
cd build
../configure --with-hlib="$(pwd)/../../hlib/build"
make -j4
make install
cd -
popd
pushd anivision
./autogen.sh
mkdir build
cd build
../configure --with-hlib="$(pwd)/../../hlib/build" --with-anitmt-build="$(pwd)/../../anitmt/build" --with-anitmt-src="$(pwd)/../../anitmt"
make -j4
make install
cd -
popd
cd anitmt/examples/
./make_examples
cd -
The examples are very small. Have a look at the make_examples script. There
are some commented commands which render a much nicer version of the circles example.
cd anivision/examples/
./make_examples
cd -
The AniTMT Examples use tga2avi and mkavi for converting images to
videos. These days, much better tools exist as open source software. Here, one
example:
ffmpeg -framerate 25 -i f%07d.tga -c:v libx264 -profile:v high -crf 20
-pix_fmt yuv420p output.mp4
taken from here
If you are a fan of free video codes, please send me another example
and I will put it here as well.
configure
call add --prefix=/home/<user>/progs/local
LD_LIBRARY_PATH=/home/<user>/progs/local/lib64
cd anitmt/examples/
LD_LIBRARY_PATH=/home/<user>/progs/local/lib64 ./make_examples
cd -
cd anivision/examples/
LD_LIBRARY_PATH=/home/<user>/progs/local/lib64 ./make_examples
cd -
Cross-compiling windows executables from linux generally works. Look in /usr
how your system compilier is called and replace x86_64-suse-linux
in my
example (https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Specifying-Target-Triplets.html#Specifying-Target-Triplets).
pushd anitmt
./autogen.sh
mkdir build-windows
cd build-windows
../configure --prefix=/usr/x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --build=x86_64-suse-linux --target=x86_64-suse-linux
make -j4
cd -
popd
This will produce build-windows/anitmt-calc/anitmt-calc-static and some error
messages since producing shared library versions fails. libtool seems to be
incompatible with cross-compiling to Windows.