I totally agree with that, based on the frustration I had in the past
several days.

First I tried out Centos 4.6. The reason for that is the only Linux system
officially supported
in our company is RHEL4. I might be able to get in house help regarding IT
setup. But the tools
coming with Centos 4.5 are too old. Then I switched to Centos 5.2, the tools
(autoconf) are still too
old to run image-creator autogen.sh. OK, fine. If inside Moblin, people are
using FC9, I reformatted my
disk, and installed FC9. Now image-creator autogen.sh can run, good. The
first time I typed "sudo image-creator", I
got "Unsupported distribution: distribution.redhat".

OK, I guess the next thing I will do is reformatting my disk again, and
install Ubuntu Gusty. And try it out again.

Now anyone has comment on
http://www.theregister.co.uk/2008/07/23/moblin_reworked/  ?
"Re-jigged Intel mobile Linux stack dumps Ubuntu". Does this means we need
to switch host environment again or it is
just how target packages are managed?  I had hoped for embedded system, the
build environment itself is well isolated
from the host environment. Seems not true for image-creator. Also it is a
little too "black box". We need to figure out what
is happening behind the pretty GUI. Why not using a white-box design?


best regards,
Guo

On Tue, Aug 5, 2008 at 4:09 AM, Tero Saarni <[EMAIL PROTECTED]> wrote:

> On Mon, Aug 4, 2008 at 21:43, Rusty Lynch <[EMAIL PROTECTED]> wrote:
> > The fact that a particular target stack is using deb or using rpm
> > packaging should not effect your choice of host distribution.
>
> I wouldn't say it should not effect the choice.  There are advantages
> in running the same distribution on host and target.  It makes
> development more convenient and saves time in integration.
>
> --
> Tero
>
> _______________________________________________
> dev mailing list
> [email protected]
> https://www.moblin.org/mailman/listinfo/dev
>
_______________________________________________
dev mailing list
[email protected]
https://www.moblin.org/mailman/listinfo/dev

Reply via email to