Commit 38d7b8d0 authored by Christian Schaller's avatar Christian Schaller

my initial commit

parents
Primary Author:
Christian Schaller <uraeus@gnome.org>
Transmageddon, Video Transcoder
Copyright (c) 2009, Christian Schaller <uraeus@gnome.org>
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this program; if not, write to the
Free Software Foundation, Inc., 59 Temple Place - Suite 330,
Boston, MA 02111-1307, USA.
Installation Instructions
*************************
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
2006, 2007 Free Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
Basic Installation
==================
Briefly, the shell commands `./configure; make; make install' should
configure, build, and install this package. The following
more-detailed instructions are generic; see the `README' file for
instructions specific to this package.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. Caching is
disabled by default to prevent problems with accidental use of stale
cache files.
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You need `configure.ac' if
you want to change it or regenerate `configure' using a newer version
of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system.
Running `configure' might take a while. While running, it prints
some messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
6. Often, you can also type `make uninstall' to remove the installed
files again.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that the
`configure' script does not know about. Run `./configure --help' for
details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c99 CFLAGS=-g LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you can use GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
With a non-GNU `make', it is safer to compile the package for one
architecture at a time in the source code directory. After you have
installed the package for one architecture, use `make distclean' before
reconfiguring for another architecture.
Installation Names
==================
By default, `make install' installs the package's commands under
`/usr/local/bin', include files under `/usr/local/include', etc. You
can specify an installation prefix other than `/usr/local' by giving
`configure' the option `--prefix=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
PREFIX as the prefix for installing programs and libraries.
Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure' can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS KERNEL-OS
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the option `--target=TYPE' to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share, you
can create a site shell script called `config.site' that gives default
values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
==================
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script).
Unfortunately, this technique does not work for `CONFIG_SHELL' due to
an Autoconf bug. Until the bug is fixed you can use this workaround:
CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
`configure' Invocation
======================
`configure' recognizes the following options to control how it operates.
`--help'
`-h'
Print a summary of the options to `configure', and exit.
`--version'
`-V'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
`--config-cache'
`-C'
Alias for `--cache-file=config.cache'.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
AUTOMAKE_OPTIONS = dist-bzip2
SUBDIRS = bin src common
desktopdir = $(datadir)/applications
desktop_DATA = transmageddon.desktop
icondir = $(datadir)/pixmaps
icon_DATA = transmageddon.png
EXTRA_DIST = \
transmageddon.spec \
transmageddon.spec.in \
ChangeLog \
autogen.sh \
NEWS \
AUTHORS \
RELEASE \
ABOUT-NLS \
transmageddon.png
DISTCLEANFILES = \
intltool-extract \
intltool-merge \
intltool-update \
autoregen.sh \
config.log \
Makefile \
Makefile.in \
missing \
mkinstalldirs \
py-compile \
config.status \
install-sh \
configure
EXTRA_DIST += \
intltool-extract.in \
intltool-merge.in \
intltool-update.in \
TODO
locale-uninstalled:
if test -d po; then \
$(MAKE) -C po datadir=../$(top_builddir) install; \
fi
locale-uninstalled-clean:
@-rm -rf _trial_temp
@-rm -rf $(top_builddir)/locale
all-local: locale-uninstalled
clean-local: locale-uninstalled-clean
This is a simple python application for transcoding video into formats
supported by GStreamer.
* Make codec choices intelligent
Currently the choice of codecs you get with each container format is chosen by hand. We should query
the GStreamer caps and choose them automatically based on that.
* Not hardcode encoder and muxer plugin names
Let GStreamer just provide us any plugin it got available which can encode or mux to wanted format
instead of hardcoding plugin names in the code. This is probably also needed to get easy_codec to work.
* Support setting attributes on the encoders
This will allow us to choose Dirac Pro as a codec for instance as that is an attribute on the
normal Dirac encoder.
* Enable support for MXF and DNxHD. Once the MXF muxer is in gst-plugins-bad we can enable support for
MXF container format and DNxHD video codec.
* ASF support. Summer of code will hopefully provide us with a ASF muxer. This would enable all Windows
media formats.
* Add profiles
I want to have profiles for things like N810, iPhone, PSP etc. which automatically choose a container
format and codecs for you. This would ideally be combined with a videoscaling, which in turn require us
to get GStreamer to probe the file upon selection so we can make some decisions on if and how to scale.
* Enable translations
Allow translators to translate the application using po files.
* Add better error handling
Make sure the application runs even if directory names etc. are different. Enable reporting when
no plugin is found which allows allows muxing or encoding. Verify that Easy Codec install works.
* And status field which lets user know that file is done and where it ended up.
* Get application icon made
Find a graphics artist to make nice Tango style icon
* Support remuxing
Allow incoming codecs to be preserved and just remuxed into new file when possible
* Support non-muxed audio codec
Allow the outputting of non-muxed audio codecs. Not sure we really want this as it would add more options
to the UI to do something which I doubt a lot of people care to use this application for.
* More advanced features
There are many things people might want to do. We want to avoid this application becoming like a lot of
other transcoder tools though, which got more buttons and options that you can throw a stick at.
Never expose an option which a 'normal' user is unlikely to understand and want to tweak.
One example of something we *might* want to add is downmixing of audio channels.
* Move more logic out of UI file
Currently there is quite a bit of of logic code in the UI class. This should be moved down to the
transcoder file in order to ease the possibility of other user interfaces.
* Windows port
Port application to windows and get a py2exe binary going with everything. The video directory stuff is only
known current non-portable.
This diff is collapsed.
#!/bin/sh
DIE=0
package=transmageddon
srcfile=src/transmageddon.py
if test ! -f common/Makefile.am;
then
rm -R common/
echo "+ Setting up common submodule"
git submodule init
fi
git submodule update
# source helper functions
if test ! -f common/gst-autogen.sh;
then
echo There is something wrong with your source tree.
echo You are missing common/gst-autogen.sh
exit 1
fi
. common/gst-autogen.sh
CONFIGURE_DEF_OPT=''
autogen_options $@
echo -n "+ check for build tools"
if test ! -z "$NOCHECK"; then echo " skipped"; else echo; fi
version_check "autoconf" "$AUTOCONF autoconf autoconf-2.54 autoconf-2.53 autoconf-2.52" \
"ftp://ftp.gnu.org/pub/gnu/autoconf/" 2 52 || DIE=1
version_check "automake" "$AUTOMAKE automake automake-1.7 automake-1.6 automake-1.5" \
"ftp://ftp.gnu.org/pub/gnu/automake/" 1 6 || DIE=1
version_check "pkg-config" "" \
"http://www.freedesktop.org/software/pkgconfig" 0 8 0 || DIE=1
die_check $DIE
autoconf_2_52d_check || DIE=1
aclocal_check || DIE=1
autoheader_check || DIE=1
die_check $DIE
# if no arguments specified then this will be printed
if test -z "$*"; then
echo "+ checking for autogen.sh options"
echo " This autogen script will automatically run ./configure as:"
echo " ./configure $CONFIGURE_DEF_OPT"
echo " To pass any additional options, please specify them on the $0"
echo " command line."
fi
toplevel_check $srcfile
tool_run "$aclocal" "-I common/m4 $ACLOCAL_FLAGS"
tool_run "$autoconf"
tool_run "$automake" "-a -c"
test -n "$NOCONFIGURE" && {
echo "+ skipping configure stage for package $package, as requested."
echo "+ autogen.sh done."
exit 0
}
echo "+ running configure ... "
test ! -z "$CONFIGURE_DEF_OPT" && echo " ./configure default flags: $CONFIGURE_DEF_OPT"
test ! -z "$CONFIGURE_EXT_OPT" && echo " ./configure external flags: $CONFIGURE_EXT_OPT"
echo
./configure $CONFIGURE_DEF_OPT $CONFIGURE_EXT_OPT || {
echo " configure failed"
exit 1
}
bin_SCRIPTS = \
transmageddon
CLEANFILES = $(bin_SCRIPTS)
#!/bin/bash
cd /usr/lib/transmageddon
python transmageddon.py
common @ 5dc8ae30
Subproject commit 5dc8ae302733ce1aae5b1aaa613ce77a8ae4b3d9
AC_PREREQ(2.52)
dnl initialize autoconf
dnl when going to/from release please set the nano (fourth number) right !
dnl releases only do Wall, cvs and prerelease does Werror too
AC_INIT(transmageddon, 0.5,
http://www.linuxrising.org/transmageddon,
transmageddon)
dnl initialize automake
AM_INIT_AUTOMAKE
dnl define PACKAGE_VERSION_* variables
AS_VERSION
dnl can autoconf find the source ?
AC_CONFIG_SRCDIR([src/transmageddon.py])
AC_SUBST_FILE(AUTHORS)
AUTHORS=$srcdir/AUTHORS
dnl Note for packagers
dnl The following requirements are run-time requirements,
dnl make sure you don't forget them, even though you're able to
dnl build pitivi without them.
dnl
dnl For a more exhaustive list of checks, you can have a look at
dnl the runtime checks in pitivi/check.py
AC_SUBST(PYGTK_REQ, 2.8.0)
AC_SUBST(PYGST_REQ, 0.10.6)
AC_SUBST(GST_REQ, 0.10.13.1)
AM_INIT_AUTOMAKE($PACKAGE, $VERSION)
AC_SUBST(ACLOCAL_AMFLAGS, "-I common/m4")
AS_AC_EXPAND(LIBDIR, $libdir)
AC_MSG_NOTICE(Storing library files in $LIBDIR)
AS_AC_EXPAND(DATADIR, $datadir)
AC_MSG_NOTICE(Storing data files in $DATADIR)
AS_AC_EXPAND(SYSCONFDIR, $sysconfdir)
AC_MSG_NOTICE(Storing configuration files in $SYSCONFDIR)
AS_AC_EXPAND(LOCALSTATEDIR, $localstatedir)
AC_MSG_NOTICE(Using localstatedir $LOCALSTATEDIR)
dnl check for python
AS_PATH_PYTHON(2.5)
dnl ALL_LINGUAS="fr"
# GETTEXT_PACKAGE="transmageddon"
# AC_SUBST([GETTEXT_PACKAGE])
# AC_DEFINE_UNQUOTED([GETTEXT_PACKAGE], "$GETTEXT_PACKAGE", [Gettext package])
# AM_GLIB_GNU_GETTEXT
# IT_PROG_INTLTOOL([0.35.0])
CONFIGURED_PYTHONPATH=$PYTHONPATH
AC_SUBST(CONFIGURED_PYTHONPATH)
AC_CONFIG_FILES([bin/transmageddon], [chmod +x bin/transmageddon])
dnl output stuff
AC_OUTPUT(
Makefile
bin/Makefile
common/Makefile
common/m4/Makefile
src/Makefile
transmageddon.spec
transmageddon.desktop
)
8
dir
3830
svn+ssh://uraeus@svn.gnome.org/svn/gnome-media/trunk/m4
svn+ssh://uraeus@svn.gnome.org/svn/gnome-media
2008-03-25T20:31:15.016743Z
3826
malureau
svn:special svn:externals svn:needs-lock
e843a620-e025-0410-b208-ba2adad950f9
as-compiler-flag.m4
file
2007-01-02T12:26:40.000000Z
a300187cb4e725c275e6657eb6500bd7
2004-06-01T10:08:56.000000Z
2503
thomasvs
has-props
as-version.m4
file
2007-01-02T12:26:40.000000Z
fe9179ad0e92dd9463c8f71a1b7bb4db
2004-06-01T10:08:56.000000Z
2503
thomasvs
has-props
esd.m4
file
2008-03-31T13:48:19.000000Z
4395ff1d8a7059bf9eb05919be8c30b0
2008-03-25T20:31:15.016743Z
3826
malureau
has-props
K 13
svn:eol-style
V 6
native
K 13
svn:mime-type
V 7
text/m4
END
K 13
svn:eol-style
V 6
native
K 13
svn:mime-type
V 7
text/m4
END
K 13
svn:eol-style
V 6
native
K 12
svn:keywords
V 23
Author Date Id Revision
K 13
svn:mime-type
V 7
text/m4
END
dnl as-compiler-flag.m4 0.1.0
dnl autostars m4 macro for detection of compiler flags
dnl David Schleef <ds@schleef.org>
dnl $Id: as-compiler-flag.m4,v 1.1 2004/06/01 09:33:45 thomasvs Exp $
dnl AS_COMPILER_FLAG(CFLAGS, ACTION-IF-ACCEPTED, [ACTION-IF-NOT-ACCEPTED])
dnl Tries to compile with the given CFLAGS.
dnl Runs ACTION-IF-ACCEPTED if the compiler can compile with the flags,
dnl and ACTION-IF-NOT-ACCEPTED otherwise.
AC_DEFUN([AS_COMPILER_FLAG],
[
AC_MSG_CHECKING([to see if compiler understands $1])
save_CFLAGS="$CFLAGS"
CFLAGS="$CFLAGS $1"
AC_TRY_COMPILE([ ], [], [flag_ok=yes], [flag_ok=no])
CFLAGS="$save_CFLAGS"
if test "X$flag_ok" = Xyes ; then
$2
true
else
$3
true
fi
AC_MSG_RESULT([$flag_ok])
])
dnl as-version.m4 0.1.0
dnl autostars m4 macro for versioning
dnl Thomas Vander Stichele <thomas at apestaart dot org>
dnl $Id: as-version.m4,v 1.4 2004/06/01 09:40:05 thomasvs Exp $
dnl AS_VERSION(PACKAGE, PREFIX, MAJOR, MINOR, MICRO, NANO,
dnl ACTION-IF-NO-NANO, [ACTION-IF-NANO])
dnl example
dnl AS_VERSION(gstreamer, GST_VERSION, 0, 3, 2,)
dnl for a 0.3.2 release version
dnl this macro
dnl - defines [$PREFIX]_MAJOR, MINOR and MICRO
dnl - if NANO is empty, then we're in release mode, else in cvs/dev mode
dnl - defines [$PREFIX], VERSION, and [$PREFIX]_RELEASE
dnl - executes the relevant action
dnl - AC_SUBST's PACKAGE, VERSION, [$PREFIX] and [$PREFIX]_RELEASE
dnl as well as the little ones
dnl - doesn't call AM_INIT_AUTOMAKE anymore because it prevents
dnl maintainer mode from running ok
dnl
dnl don't forget to put #undef [$2] and [$2]_RELEASE in acconfig.h
dnl if you use acconfig.h
AC_DEFUN([AS_VERSION],
[
PACKAGE=[$1]
[$2]_MAJOR=[$3]
[$2]_MINOR=[$4]
[$2]_MICRO=[$5]
NANO=[$6]
[$2]_NANO=$NANO
if test "x$NANO" = "x" || test "x$NANO" = "x0";
then
AC_MSG_NOTICE(configuring [$1] for release)
VERSION=[$3].[$4].[$5]
[$2]_RELEASE=1
dnl execute action
ifelse([$7], , :, [$7])
else
AC_MSG_NOTICE(configuring [$1] for development with nano $NANO)
VERSION=[$3].[$4].[$5].$NANO
[$2]_RELEASE=0.`date +%Y%m%d.%H%M%S`
dnl execute action
ifelse([$8], , :, [$8])
fi
[$2]=$VERSION
AC_DEFINE_UNQUOTED([$2], "$[$2]", [Define the version])
AC_SUBST([$2])
AC_DEFINE_UNQUOTED([$2]_RELEASE, "$[$2]_RELEASE", [Define the release version])
AC_SUBST([$2]_RELEASE)
AC_SUBST([$2]_MAJOR)
AC_SUBST([$2]_MINOR)
AC_SUBST([$2]_MICRO)
AC_SUBST([$2]_NANO)
AC_DEFINE_UNQUOTED(PACKAGE, "$PACKAGE", [Define the package name])
AC_SUBST(PACKAGE)
AC_DEFINE_UNQUOTED(VERSION, "$VERSION", [Define the version])
AC_SUBST(VERSION)
])