launch.h File Reference

#include <algorithm>
#include <map>
#include <set>
#include <sstream>
#include <string>
#include <vector>
#include "goby/middleware/tool/interface/model.h"

Go to the source code of this file.

Classes
struct	goby::middleware::tool::interface::LaunchUnit
	What one launch file starts: a platform, or one module (one gobyd) of a platform. More...
struct	goby::middleware::tool::interface::LaunchLine
	One goby_launch line, worked out from a run: entry. More...
struct	goby::middleware::tool::interface::ParsedLaunchLine
	One line of an existing launch file, as goby_launch would read it. More...
struct	goby::middleware::tool::interface::LaunchDifference
	A difference between a launch file and a deployment's launch lines. More...

Namespaces
namespace	goby
	The global namespace for the Goby project.
namespace	goby::middleware
	Objects implementing the Goby nested middleware.
namespace	goby::middleware::tool
namespace	goby::middleware::tool::interface
namespace	goby::middleware::tool::interface::detail

Functions
std::string	goby::middleware::tool::interface::detail::replace_all (std::string text, const std::string &from, const std::string &to)
std::string	goby::middleware::tool::interface::detail::first_word_basename (const std::string &command)
bool	goby::middleware::tool::interface::detail::in_unit (const LaunchEntry &e, const LaunchUnit &unit)
const Application *	goby::middleware::tool::interface::detail::application (const LaunchUnit &unit, const LaunchEntry &e)
bool	goby::middleware::tool::interface::detail::requires_intervehicle (const Application &app)
std::string	goby::middleware::tool::interface::detail::when_command (const std::string &when)
	A when: condition as a shell command: "A =~ REGEX", "A == B", "A != B", or a command whose exit status decides. Kept free of '[' and ']', which end goby_launch's [directives].
std::string	goby::middleware::tool::interface::detail::escape_double_quoted (const std::string &text)
bool	goby::middleware::tool::interface::detail::is_gobyd (const LaunchEntry &e)
std::vector< LaunchUnit >	goby::middleware::tool::interface::launch_units (const Deployment &deployment)
	Every launch file a deployment makes: one per platform, or per module where a platform has modules.
std::vector< std::string >	goby::middleware::tool::interface::auto_hold (const LaunchUnit &unit)
	gobyd's hold: applications with a required intervehicle subscription, which must be subscribed before anything is published to them, and goby_intervehicle_portal, which carries their subscriptions
std::vector< std::string >	goby::middleware::tool::interface::auto_expected (const LaunchUnit &unit, const LaunchEntry &coroner)
	goby_coroner's expected names: every Goby application in the unit but the coroner itself and those marked expected: false
std::vector< std::string >	goby::middleware::tool::interface::detail::expand_auto (const std::vector< std::string > &given, const std::vector< std::string > &derived)
std::vector< LaunchLine >	goby::middleware::tool::interface::launch_lines (const LaunchUnit &unit)
	The goby_launch lines for a unit, in run: order (disabled entries included)
std::string	goby::middleware::tool::interface::launch_line_text (const LaunchLine &line)
	"[kill=..., name=..., env=...] command", as goby_launch reads it
std::string	goby::middleware::tool::interface::render_launch (const LaunchUnit &unit, const std::string &deployment_file)
	A goby_launch file for the unit.
void	goby::middleware::tool::interface::check_launch (const Deployment &deployment, Issues &issues)
	Problems with a deployment's launch data: anything goby_launch would cut at a '#', a Goby application listed before gobyd, a hold list that misses a required intervehicle subscriber, and an expected list that differs from what is launched.
std::vector< ParsedLaunchLine >	goby::middleware::tool::interface::parse_launch_file (const std::string &text)
std::vector< LaunchDifference >	goby::middleware::tool::interface::check_launch_file (const LaunchUnit &unit, const std::string &launch_text)
	Compare a hand-written launch file with what the deployment would launch.