[Kdenlive-devel] Debian support

[Jason Wood]

On Sunday 09 Nov 2003 6:30 pm, liebrand at apollo.nu wrote:
> Well I've got some info for your FAQ page on how to get kdenlive compiling
> on debian ... i say 'compiling'.. not yet 'running' ;-)
>
> 1- Don't mess with KDE yourself! ;-)
> Basically find a distro that comes with the KDE3, or dont bother. I've
> tried to upgrade the bits and pieces of KDE one at a time, and ended having
> a completely non-usable system.. hehe.. But I've now installed the latest
> knoppix (3.3) 

:-) 

> well... almost
>
> Although all dependencies are now all in place, I had (/have) some problems
> compiling. First, piave (0.2.0) compiled fine. But then kdenlive (0.2.0)
> gave some errors. So instead of looking at the problems, I decided it was
> time to move up anyhow.

There were a number of minor compilation issues with kdenlive 0.2.0 that only 
seemed to affect debian. Those issues are all fixed in kdenlive 0.2.3.

>
> So I'm trying to compile 0.2.3. But Piave is not happy. It took me a while
> to workout that I had to have the CFLAGS and CXXFLAGS (i did both to be
> sure): -DENABLE_DEBUG=0
> -DENABLE_EXPERIMENTAL_CODE=0
>
> It hadn't listed that anywhere on the piave site, but at least now the
> compilation went a little further.. only to halt on:
>
> In file included from sndfile.c:24:
> sfendian.h:33:10: #error "Target CPU endian-ness unknown. May need to hand
> edit src/config.h"
>
> Is there another flag I need to set somewhere? Having things not defined is
> an easy one... figuring out what cpu type i have to set where is a little
> more tricky ;-)

Well, we are definitely getting closer to an answer here.

The ENABLE_DEBUG and ENABLE_EXPERIMENTAL_CODE flags, along with target CPU 
endianess and a whole host of other configuration options should all be setup 
by the ./configure script.

In particular, as hinted at in the error message you got, ./configure should 
generate a config.h file with the settings in (not to be confused with the 
config.h.in file). Could you check to see if that files has been generated? I 
am unsure as to which directory it lives in. If you find it, try renaming it 
and re-running the ./configure script to make sure that it does regenerate 
it.

If you could send me a copy of config.h as well (assuming it exists), I'll see 
if I can get any information out of it. You are not the only person who has 
been having issues with piave compilation (although it works fine on my 
machine), so the sooner we can figure out what is wrong, the better! :-)

Cheers,
Jason

-- 
Jason Wood
Homepage : www.uchian.pwp.blueyonder.co.uk