[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] adding applications to Petalinux platform: what do I need to know?




Dan

I agree with John, totally. You should be using the petalinux-new-app approach when building app that are not part of the kernel core or, what I will call for lack of a better name, kernel apps. My method is required because changes are required to be made to kernel apps such as the IP stack, aka, IPRoute2 and the kernel core. But this makes one wonder if all the apps in the user and lib directories should be moved to the user-app tree?

Another issue with cross-compiling, that I'm sure the experts know about, which bit me hard. It deals with apps that build programs which are used to build other portions of the app. Still have not resolved how to get around this one. An example app is MySQL.

Speaking of kernel core modiifications. I wonder if anyone has looked into the correct method to patch the kernel. With the rpmbuild process for Fedora, as an example, the file kernel.spec is modified with the patch file to be applied. Is there a similar method with the Petalinux environment? Right now I simply run a multi-patch file against the linux-2.6.x-petalogix tree.

...Chris

John Williams wrote:
Hi Chris, Dan,

On Wed, Jun 10, 2009 at 3:29 AM, Chris Robson <Chris.Robson@xxxxxxxxxxxx> wrote:

You will have to cross compile things.  Generally application trees are
placed in the ./petalinux/user directory tree and user libraries are placed
in ./petalinux-dist/lib tree.

For user-created apps, we recommend using the petalinux-new-app
script, which places your apps in software/user-apps, with a template
Makefile etc.  In most cases this is preferred over what Chris
describes.

Plugging in your app down into the petalinux-dist/user hierarchy is
fiddly, and hides your app down in among tens of thousands of lines of
standard source code.  It also means you hack on standard config and
scripts and Makefiles, making a future upgrade more problematic.

Note there's nothing stopping you using a more complex Makefile like
Chris offers, in the user-apps tree, then you get the best of both
worlds.

Regards,

John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/