Re: App on L4Re

Adam Lackorzynski <[email protected]>
Newsgroups gmane.comp.micro-kernel.l4.devel
Message-ID <[email protected]>
Hi,

On Wed Nov 28, 2012 at 12:44:04 +0800, OSDepend wrote:
> >To add to what Björn already mentioned: You are free to use whatever you
> >like but for that you need to have an understanding on the options. L4Re
> >is an offer that significantly reduces complexity for developing native
> >L4 applications. For example, look at l4/pkg/hello/server/src/main.c,
> >the "Hello World" greeting. This is a native L4 application, you do not
> >need Linux to run it. However, L4Re, among many more things, makes it
> >possible that this program is so common to you and you immediately
> >understand what it is doing. But if you like you can also work directly
> >on the kernel's interfaces only. However, then you are likely starting
> >to develop an operating system layer before starting your application.
> >Adam
> 
> Thank you for your help. What i really care about is how well the L4Re
> is providing. Because i have a willing to port a search engine or a
> hadoop framework on L4Re to see if i can gain much more performance
> benifit.  In L4Re, you have already present uclibc and pthread for
> programmer. But it seems like that I need to build the application
> (hello world) with the L4Re, and after that i can boot the system and
> run the app.

Yes, that's the current workflow. Usually we use for example Qemu to
launch and run systems on our laptops. Physical systems are usually
booted via network.

> Can i just build and run my applications on L4Re after the
> L4Re+Fiasco.OS has been boot? Is there any tools developed to dynamic
> build and load applications? (i'm not refereing to the Ned which inits
> and loads compiled apps.)

Indeed, there's no ready-to-use solution for that.



Adam
-- 
Adam                 [email protected]
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.