etherboot-developers

Re: [Etherboot-developers] bin and bin32

[<ke...@us...>]

>Can we merge everthing into just bin?
>
>Unless we setup for cross compilers we cannot build for multiple
>architectures simultaneously.  And currently I definitely cannot
>build for LinuxBIOS and non LinuxBIOS simultaneously on the same
>architecture.
>
>What I would like to do is create a setup where I can have multiple
>Config files and each Config file would have it's own seperate bin
>directory.
>
>The easiest way I can think to do that right now is:
>1) reverse the includes and have Config include Makefile
>   so we can be flexible about the name.
>2) Have a variable in Config that specifies the bin directory,
>   or the directory the bin directory lives in.
>3) Have a variable in Config that specifies where the Etherboot
>   source tree lives.
>
>Being able to do:
>make -f Config-lnxi blah
>make -f Config-lnxi-lb blah
>
>And generate all of the romimages I need would be very nice
>when I am generating a binary rpm with all of the romimages I need.
>And it would make compile testing with different Config easy 
>as well.

Sounds good, do you want to do it?

Re: [Etherboot-developers] bin and bin32

[Michael B. <mb...@fe...>]

On Wed, 16 Oct 2002, Ken Yap wrote:
> >What I would like to do is create a setup where I can have multiple
> >Config files and each Config file would have it's own seperate bin
> >directory.
> >The easiest way I can think to do that right now is:
> >1) reverse the includes and have Config include Makefile
> >   so we can be flexible about the name.
> >2) Have a variable in Config that specifies the bin directory,
> >   or the directory the bin directory lives in.
> >3) Have a variable in Config that specifies where the Etherboot
> >   source tree lives.
> >Being able to do:
> >make -f Config-lnxi blah
> >make -f Config-lnxi-lb blah
> >And generate all of the romimages I need would be very nice
> >when I am generating a binary rpm with all of the romimages I need.
> >And it would make compile testing with different Config easy
> >as well.
> Sounds good, do you want to do it?

One small request: please have Config include Makefile.inc (or something
similar) and have a Makefile that just contains:

% : force
	@$(MAKE) -f Config $@
force : ;

This is so that it's still possible to just type "make" and get something
built.  It's a "beginner-friendly" thing; we probably don't want to put
off new developers by breaking the standard build procedure.

Michael

Re: [Etherboot-developers] bin and bin32

[<ebi...@ln...>]

Michael Brown <mb...@fe...> writes:

> On Wed, 16 Oct 2002, Ken Yap wrote:
> > >What I would like to do is create a setup where I can have multiple
> > >Config files and each Config file would have it's own seperate bin
> > >directory.
> > >The easiest way I can think to do that right now is:
> > >1) reverse the includes and have Config include Makefile
> > >   so we can be flexible about the name.
> > >2) Have a variable in Config that specifies the bin directory,
> > >   or the directory the bin directory lives in.
> > >3) Have a variable in Config that specifies where the Etherboot
> > >   source tree lives.
> > >Being able to do:
> > >make -f Config-lnxi blah
> > >make -f Config-lnxi-lb blah
> > >And generate all of the romimages I need would be very nice
> > >when I am generating a binary rpm with all of the romimages I need.
> > >And it would make compile testing with different Config easy
> > >as well.
> > Sounds good, do you want to do it?

I will put in my todo list.  I just don't know when I will get
there as my schedule is up in the air beyond this week where I try
to get code into the kernel.
 
> One small request: please have Config include Makefile.inc (or something
> similar) and have a Makefile that just contains:
> 
> % : force
> 	@$(MAKE) -f Config $@
> force : ;
> 
> This is so that it's still possible to just type "make" and get something
> built.  It's a "beginner-friendly" thing; we probably don't want to put
> off new developers by breaking the standard build procedure.

Sounds good.  I couldn't think of something sane with my
initial proposal.

And eventually we will want a variable in Config that
tell the machine type to build for if are doing a cross compile.

Does anyone see any value in a ./configure script at this time.
Having something that goes out and tests to make certain you
have a working compiler and linker at build time could be handy.

But for now I will just plan on the baby step of turning the Makefile
inside out.

Eric