2010/4/14 Jérémie Koenig <[email protected]>: > On Tue, Apr 13, 2010 at 10:01 PM, Nguyen Thai Ngoc Duy > <[email protected]> wrote: >> Hi, >> (...) >> Except network and tty-related commands, others (sort of) work. wget >> and vi work, although limited. Linux-specific commands won't work, >> obviously. > > Hi, I intend to port BusyBox to GNU Hurd, so I'm in a situation > somewhat similar to yours. > > One question I have been asking to myself is whether and how the > applets irrelevant to a target system should be dealt with: > * disabled at the configuration stage using KConfig dependencies; > * allowed to fail to build if the user chooses them; > * allowed to build successfully with stub functions replacing the > missing calls (a fake mount() function, for instance), but which will > always fail at runtime.
I disable all applets in Config.in at the beginning, then re-enable them when they get (even partially) supported. In terms of syscalls, not all of them can be supported, so some will remain stubs and fail at runtime. There's no clear cut. For example, on Windows hardlink work, but symlinks do not :) So it's a mix of 1. and 3. I hate build failures, 2. is out of question. -- Duy _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
