f6dec901bb
It turns out that the name function does not have much use in practice except for naming the thread of the component's initial entrypoint. For dynamically linked components, this thread is created by the dynamic linker. It is named "ep" in these cases. Considering that we will eventually turn all regular components into dynamically linked executables, the additional information provided by the Component::name() function remains unused. So it is better to not bother the component developers with adding boilerplate code.
42 lines
830 B
C++
42 lines
830 B
C++
/*
|
|
* \brief Hook functions for bootstrapping the component
|
|
* \author Norman Feske
|
|
* \date 2015-12-17
|
|
*/
|
|
|
|
/*
|
|
* Copyright (C) 2015 Genode Labs GmbH
|
|
*
|
|
* This file is part of the Genode OS framework, which is distributed
|
|
* under the terms of the GNU General Public License version 2.
|
|
*/
|
|
|
|
#ifndef _INCLUDE__BASE__COMPONENT_H_
|
|
#define _INCLUDE__BASE__COMPONENT_H_
|
|
|
|
#include <base/env.h>
|
|
#include <base/stdint.h>
|
|
|
|
namespace Genode { struct Env; }
|
|
|
|
|
|
/**
|
|
* Interface to be provided by the component implementation
|
|
*/
|
|
namespace Component
|
|
{
|
|
/**
|
|
* Return stack size of the component's initial entrypoint
|
|
*/
|
|
Genode::size_t stack_size();
|
|
|
|
/**
|
|
* Construct component
|
|
*
|
|
* \param env interface to the component's execution environment
|
|
*/
|
|
void construct(Genode::Env &env);
|
|
}
|
|
|
|
#endif /* _INCLUDE__BASE__COMPONENT_H_ */
|