ardour/share/mcp/wscript

#!/usr/bin/env python

import os

top = '.'
out = 'build'

def configure(conf):
    pass

def build(bld):
    devinfo = bld.path.ant_glob ('*.device')
    profiles = bld.path.ant_glob ('*.profile')
    bld.install_files (os.path.join(bld.env['DATADIR'], 'mcp'), devinfo)
    bld.install_files (os.path.join(bld.env['DATADIR'], 'mcp'), profiles)

def options(opt):
    pass
wscript: use consistent python shebang path Most wscripts use #!/usr/bin/env python Use that consistently. The wscripts are not executed directly and do not need the shebang path, but it might guide editors and other tools to recognize the files as being Python-ish. 2022-01-25 00:41:24 +01:00			`#!/usr/bin/env python`
major rationalization of use of search paths. ardour now has just 4 functions used to define how external resources are located: ardour_config_search_path() (for system or user specific configuration data), ardour_data_search_path() (for machine, user and system independent data), ardour_dll_directory() (base directory where shared libraries are found) and user_config_directory(). These are now used throughout the code. the config, data and dll paths/directories can be overridden by environment variables. the user config dir is added as the first element of the first two search paths, and use selectively when searching for a few other things. This commit re-enabes ./waf install, and it is believed that it works fully at this point (more testing likely required) git-svn-id: svn://localhost/ardour2/branches/3.0@12326 d708f5d6-7413-0410-9779-e7cbd77b26cf 2012-05-18 17:24:06 +00:00
			`import os`

			`top = '.'`
			`out = 'build'`

			`def configure(conf):`
			`pass`

			`def build(bld):`
			`devinfo = bld.path.ant_glob ('*.device')`
			`profiles = bld.path.ant_glob ('*.profile')`
finish unfinished work at basing all install paths on the program name 2014-04-28 21:11:08 -04:00			`bld.install_files (os.path.join(bld.env['DATADIR'], 'mcp'), devinfo)`
			`bld.install_files (os.path.join(bld.env['DATADIR'], 'mcp'), profiles)`
major rationalization of use of search paths. ardour now has just 4 functions used to define how external resources are located: ardour_config_search_path() (for system or user specific configuration data), ardour_data_search_path() (for machine, user and system independent data), ardour_dll_directory() (base directory where shared libraries are found) and user_config_directory(). These are now used throughout the code. the config, data and dll paths/directories can be overridden by environment variables. the user config dir is added as the first element of the first two search paths, and use selectively when searching for a few other things. This commit re-enabes ./waf install, and it is believed that it works fully at this point (more testing likely required) git-svn-id: svn://localhost/ardour2/branches/3.0@12326 d708f5d6-7413-0410-9779-e7cbd77b26cf 2012-05-18 17:24:06 +00:00
			`def options(opt):`
			`pass`