ardupilot/AntennaTracker/wscript

#!/usr/bin/env python
# encoding: utf-8

def build(bld):
    vehicle = bld.path.name
    bld.ap_stlib(
        name=vehicle + '_libs',
        vehicle=vehicle,
        libraries=bld.ap_common_vehicle_libraries() + [
            'PID',
        ],
        use='mavlink',
    )

    bld.ap_program(
        program_name='antennatracker',
        program_groups=['bin', 'antennatracker'],
        use=vehicle + '_libs',
    )
waf: add waf support 2015-10-09 11:03:59 -03:00			`#!/usr/bin/env python`
			`# encoding: utf-8`

			`def build(bld):`
			`vehicle = bld.path.name`
waf: vehicles and antennatracker: use methods from bld Instead of from ardupilotwaf. 2016-01-21 10:04:51 -04:00			`bld.ap_stlib(`
waf: add waf support 2015-10-09 11:03:59 -03:00			`name=vehicle + '_libs',`
			`vehicle=vehicle,`
waf: ardupilotwaf: prefix build context methods with ap_ It helps to distinguish between things from waf and things from ardupilotwaf. 2016-01-22 17:00:13 -04:00			`libraries=bld.ap_common_vehicle_libraries() + [`
waf: add waf support 2015-10-09 11:03:59 -03:00			`'PID',`
			`],`
waf: allow partial builds with new mavlink as submodule The task generator for the mavlink headers is given a name 'mavlink' and is added as a dependency to all local static libraries, because all of them use sources that include mavlink headers. It would be nice to have a good way to detect sources that use mavlink headers or to declare list of libraries that use the headers, so that the dependency could be added automatically. Additionally, there's a minor change in syntax for the task generator: using strings directly instead of lists. 2016-01-13 16:35:37 -04:00			`use='mavlink',`
waf: add waf support 2015-10-09 11:03:59 -03:00			`)`

waf: vehicles and antennatracker: use methods from bld Instead of from ardupilotwaf. 2016-01-21 10:04:51 -04:00			`bld.ap_program(`
waf: change binary names APMrover2 -> ardurover AntennaTracker -> antennatracker ArduCopter -> arducopter ArduPlane -> arduplane 2016-01-17 23:42:52 -04:00			`program_name='antennatracker',`
waf: create program groups for main products Currently we need to build a different binary for each type of copter frame. This is a preparation for setting all those binaries to a group called "copter". We create the groups for the rest of the main products for consistency. 2016-03-24 17:07:13 -03:00			`program_groups=['bin', 'antennatracker'],`
waf: add waf support 2015-10-09 11:03:59 -03:00			`use=vehicle + '_libs',`
			`)`