[okl4-developer] Porting Apps to Wombat

[Jorge Torres]

Hi,

I'm not sure if I understand correctly, but as far as your applications are
architecture independent, and are able to run for a regular Linux
distribution, you shouldn't have too many problems, you must  know is that
out of the box wombat due to it being embedded targeted uses busybox, so if
you want can either tweak for not using it, or port your applications to
busybox, they have a complete howto on their website.

Cheers,

Jorge


On Jan 16, 2008 3:16 AM, Subcommander l0r3zz <l0r3zz at gmail.com> wrote:

> Please forgive me if this is a tad off topic, but I would like to know
> (before I build something myself)
> If there are scripts, apps, emacs macros, etc that will run through a
> source tree and identify all of the system calls and/or libc calls in a body
> of code.  I would think this is a first step in porting any large body of
> code to a new OS.  That way you can be sure to map all of the syscalls that
> the App would be using to appropriate entry points in the Wombat and/or
> Iguana processes.
> I guess for input in addition to the source code, you would need some form
> of definition database to identify which functions are actually
> syscalls/libc calls for a particular OS version.
>
> Does NICTA/OK-LAbs have some tools to do this? I would imagine that this
> is a task done many times so there must be something out there that I'm not
> aware of.
>
>
> Geoff
>
>
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20080116/3fabd0c2/attachment.htm