On Wednesday 31 May 2006 10:59, Tomáš Ebenlendr wrote:
> So if I understand it correctly:
> Grub & modules (i.e., everything that is run w/o OS) is target.
Yes.
> Grub-emu (i.e., everythhing that is run in some OS) is host.
Not really. grub-emu is a debugging tool, so, strictly speaking, it
So if I understand it correctly:
Grub & modules (i.e., everything that is run w/o OS) is target.
Grub-emu (i.e., everythhing that is run in some OS) is host.
We don't have "make-tools" in c-code nor asm. (This is host in
some projects:
tools that are first compiled and then used while com
I describe the new build system a bit here. Maybe this should be written in
somewhere else (such as INSTALL) as well...
GRUB uses "target" and "host". "build" is not explicitly used. A target
represents a native environment where GRUB runs. In reality, the target type
affects:
- the cpu type
On Fri, May 26, 2006 at 09:04:55PM +0200, Yoshinori K. Okuji wrote:
> According to a suggestion by an autoconf developer, I think we should change
> the build system in this way:
>
> [...]
>
> If there is no objection, I will work on this issue very soon.
To give some feedback: I support this i
> According to a suggestion by an autoconf developer, I think we should change
> the build system in this way:
>
> - Use "host" to represent an environment in which utilities (tools) run. This
> is a natural interpretation of the meaning of "host" in autoconf.
>
> - Use "target" to represent a
According to a suggestion by an autoconf developer, I think we should change
the build system in this way:
- Use "host" to represent an environment in which utilities (tools) run. This
is a natural interpretation of the meaning of "host" in autoconf.
- Use "target" to represent a native environ
