Re: yuvdeinterlace + autotools

Hi Stefan,

> seems like I have some time to work on yuvdeinterlace again... The
> version on my hard-disk, however, is heavily out of sync with the CVS.
> Could someone who knows the auto-tools better than me, please explain
> me, how to modify Makefile.am so that it can cooperate with the
> following directory-structure:
>
> ./yuvdeinterlace/
> ./yuvdeinterlace/header/  <-- headerfiles, here...
> ./yuvdeinterlace/source/  <-- guess what ;-)
> ./yuvdeinterlace/object/  <-- g++ object-files
> ./yuvdeinterlace/yuvdeinterlace  <-- compiled and linked binary

Are you sure you really want to split headers and source?  You end up typing a 
LOT of header/ and source/ in your Makefile.am's ;-).  More importantly it 
makes the 'switch header/source' feature on IDEs sometimes a nuisance to set 
up.   The way compilers default their search paths also doesn't mesh quite as 
nicely.  

The object files partis easy: its 'built-in' to auto-tools. What you do is 
create a build directory and run configure make from there rather than your 
top-level source directory.  All stuff that is constructed dependent on the 
build configuration objects - final Makefile's, generated source code) and so 
on then gets created there.   

The point is it allows you to have different builds (usually debug and release 
for simple work) cleanly coexist and cleanly seperates built stuff from the 
things from which you build.

Note that there is a good book available copyleft online for autotools which 
make getting started and learning pretty straight-forward:

http://sourceware.org/autobook


cheers,

	Andrew



-- 

Dr Andrew Stevens
Erdingerstrasse 23
85464 Neufinsing
Germany

Home: +49 8121 883672
Mobile: +49 173 5397553

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/