Building additional binaries

Rob Landley rob at landley.net
Wed Jul 5 15:26:25 UTC 2006


On Wednesday 05 July 2006 12:51 am, Jason Schoon wrote:
> On 7/4/06, Rob Landley <rob at landley.net> wrote:
> > On Tuesday 04 July 2006 7:13 pm, Shaun Jackman wrote:
> > > I had been using the following patch to build a bFLT binary in the
> > > top-level Makefile. This configuration should be accomplished in the
> > > .config.mak file in the output directory. Unfortunately, it's not as
> > > simple as adding `all: busybox.bflt' to .config.mak, because
> > > .config.mak is included from Rules.mak and by every Makefile, not just
> > > the top-level. So, I added `busybox: busybox.bflt' to .config.mak,
> > > which is a bit of a hack, but works. In any case, I thought I'd poll
> > > the mailing list for a better solution. Perhaps the `all' target of
> > > the top-level Makefile should depend on a phony `all-extra' target
> > > that could be defined by .config.mak.
> >
> > What are you trying to accomplish?  You're not adding another applet to
> > busybox, you're building an external binary with strange dependencies on
> > busybox internals?
>
> He is building in bFLT format (uClinux binary flat format) rather than ELF.
> Seems like a worthwhile and hopefully not insurmountable task.

Ah!  I remember the earlier discussion on this now.

Yes, that's a worthwhile goal.  What are its dependencies?  (I'm pretty sure I 
don't have the bflt tools on my system.)

Possibly a "make busybox-flat" target or some such?

Rob
-- 
Never bet against the cheap plastic solution.



More information about the busybox mailing list