No configure file?

[Robert Stoffers]

On Monday 12 June 2006 18:53, Stefan Potyra wrote:
> Hi,
>
> Am Montag 12 Juni 2006 03:20 schrieb Robert Stoffers:
> > Hi,
> >
> > I've been messing around with building a package for Kdenlive
> > (http://kdenlive.sourceforge.net) however I'm getting an odd error about
> > the configure file missing. Attached below is the snipped output,
> > attached are the rules and control files I'm using. Any advice is
> > appreciated!
>
> Not sure for 100% what cdbs black magic is exactly doing, looks a little
> bit like testing if automake is present (which is not) and running it only
> if it's there.
>
> I'd suggest, that you also build-depend on automake1.9 (or any other
> version of automake) and retry.
>
> Cheers,
> 	Stefan.

Hi Stefan,

I've added that but still no good, same error. Below are the install 
instructions, perhaps they can provide more clues? I've tried doing 
the "make -f Makefile.cvs" command before building the package as a test, no 
success there either.


Kdenlive Installation instrucions
=================================

Installing from tarball :

Download the tarball into a directory, and unpack it :

tar -xzf kdenlive-x.x.x-src.tar.gz

where x.x.x is the version number.
(your reading this so you've already done this, right?)

Once extracted, you can enter the directory and configure and build kdenlive.

cd kdenlive
make -f Makefile.cvs
./configure --prefix=`kde-config --prefix`
make

To install, become root:

su
(enter root password at prompt)
make install

./configure takes a number of options, type ./configure --help to
discover what these are. The most important one is --prefix, which
specifies where your KDE installation is when installing. For Mandrake,
use :

./configure --prefix=/usr

Once installed, you can start Kdenlive by typing "kdenlive".

<snip>

Basic Installation
==================

   These are generic installation instructions.

   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, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').

   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 at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

   The file `configure.in' is used to create `configure' by a program
called `autoconf'.  You only need `configure.in' 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.  If you're
     using `csh' on an old version of System V, you might need to type
     `sh ./configure' instead to prevent `csh' from trying to execute
     `configure' itself.

     Running `configure' takes a while.  While running, it prints some
     messages telling which features it is checking for.

  2. Type `make' to compile the package.

  3. Type `make install' to install the programs and any data files and
     documentation.

  4. You can remove the program binaries and object files from the
     source code directory by typing `make clean'.


Thanks,

Robert Stoffers
-- 
Member, Ubuntu Linux - http://www.ubuntu.com
Staff, Freenode IRC Network- http://www.freenode.net