Hi Waldemar,

>> I suggest putting everything _generated_ into e.g. build/
>> so that we have
>>
>> build/
>>      bin/
>>      tools/
>>      toolchain_mipsel/
>>      pkgs_mipsel/ (the former build_mipsel)
>>      lbin/
>>      staging_dir_mipsel/
Sound more well-sorted...

> May be we could use a better directory for the firmware and
> packages, too.
Well, "bin" and "bin/packages" is ok for me so far.

But what I really like to see is a possibility to build Images for
multiple devices at the same time as I work with different stuff here
and I don't want to maintain a separate config-file for each.

This is even useful for nightly snapshot builds where you want to
provide images for all supported targets.

> I need to think about this. Any comments to the other design?
Yes, I think I will like it ;-)

Some other stuff:
- why do we support "rrdtool" and "rrdtool1"? Maybe we should drop
  "rrdtool1"?

- what about an expected first release date? I'd like to see a stable
  1.0 relase maybe only for "nvram" machines in next future and the
  buildroot and configfs changes later for 1.1.
  So we might get more feedback as more people begin to use it.

wbx: May I have another closer look at the rewriting stuff of truc, it
is totally annoying now.

And, can you write this directory layout down to a small first
documentation page? It might be useful.
Maybe the possible "make" targets should be documented too as soon as
possible (tg?).

/Markus

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
freewrt-developers mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-developers

Reply via email to