Revision 561, 0.6 kB (checked in by arnonym, 16 years ago)

Merge the scons-branch to trunk.

This basicly adds scons as a buildsystem. This does not mean that auto* is dropped instantly (the added files should not collide) but allows for some testing in the transition-process. The auto*-files are deleted later on...

Due to this, the (which gets built by is copied from using scons. When dropping make this file should be moved to

The scons-system is probably missing a lot of things you are used to in make. But at least here it does build a usable libffado. :-)

To use scons, simply do a "scons". If you want to know about configuration, "scons -h" allows you to view and set parameters, which are saved from there on. What do I mean with this? "scons -h PREFIX=$HOME" sets the install-prefix to $HOME and shows the helptext that already incorporates the changed option. Another "scons -h" will show the same help-text and scons remembers the changed prefix. "scons" now builds the libs and apps and "scons install" installs everything into the prefix. "scons -c install" cleans the local dir and uninstalls the package while "scons -c" just cleans the local dir.

BTW: I also set several more ignores, I am just to lazy to split these two commits. ;-)

1 #! /usr/bin/env python
3 Import( 'env' )
5 env = env.Copy()
7 #env.AppendUnique( CPPPATH=["#/src"] )
8 #env.AppendUnique( LIBPATH=["#/src"] )
9 #env.AppendUnique( LIBS=["ffado"] )
11 #for app in ["test-ffado", "test-extplugcmd", "test-fw410", "test-volume", "test-mixer", "test-cycletimer", "test-timestampedbuffer", "test-ieee1394service", "test-streamdump"]:
12 #       env.Program( target=app, source = app+".cpp" )
14 #env.Program( target="test-ffado", source = "test-ffado.cpp" )
15 #env.Program( target="", source = ".cpp" )
17 #env.Program( target="test-sytmonitor", source = env.Split( "test-sytmonitor.cpp SytMonitor.cpp" ) )
18 #
20 env.SConscript( dirs="mixer", exports="env" )
Note: See TracBrowser for help on using the browser.