especially if there is any question over the safe use of vfork.
Of course there are lots of cases where you can't just replace fork()
and vfork(). But here you need a decent porting if you want to take care
of the "EMBED" define. In other cases (the more common ones) it would be
"nice" just to use vfork() all over the place.
Moreover the name of the "EMBED" define seems quite outdated, as today,
many embedded devices do provide an MMU.
Hmm, I thought that current SG/uClinux-dist mostly used EMBED for things that
reduce code size (and often functionality at the same time) and
__uClinux__ for true uClinux (ie !MMU) changes.
I believe this might be changing.
I feel the uCLinux toolchain is more about the way of creating a
distribution not about the k,ind of architecture used. (e.g. the NIOS
architecture will be optionally available with and without MMU. )
-Michael
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
