On 15.12.2011 14:34 Wolfgang Denk said the following:
Dear Michael,

In message<[email protected]>  you wrote:

I am still using 4.2 to develop for an embedded PPC based appliance.
The flash image and runtime environment is coming from the supplier of
the appliance and we are developing 99% userspace applications.

In this situation is it useful to migrate to 5.1?
If yes, is it just a change of ELDK environment or is there more work to do?

That's difficult for me to answer.  You write the "runtime environment
is coming from the supplier of the appliance" - I understand that this
includes the user space target environment and libraries.  If you want
to continue to use these, you must stick with the cross tools that use
the same libraries and the matching header files etc.
Yes and no.
The appliance is shipped with a running Linux system already installed on the flash (+U-Boot). I think it would be possible to build my own flash image but currently the effort would be too high.

But the sourcecode for all of the user space libraries is available and for minor changes I even cross-compiled it for the target environment.


On the other hand, going from ELDK 4.2 to 5.1 means about 4 years of
technological progress.   We not only have a much larger list of
supported software packages and of course recent versions of the
software now, we also have support for new areas of deployment (liek
GUI support through Qte or the GMAE/Sato environments), plus support
for IDEs like Eclipse or Anjuta, or support for emulated environments
(runing your code in virtual targets under qemu), or support for a HUI
oriented image builder (HOB), or ...
That's the reason I asked. Especially Eclipse support would be interesting for me.

So while it is probably not so easy to switch to the new tools with
your existing project, it is most probably a good idea to consider
using the new tools for any new tasks or projects.

Hope this helps.
Like I expected ;-)

Thanks, will have to think about it.
Michael

_______________________________________________
eldk mailing list
[email protected]
http://lists.denx.de/mailman/listinfo/eldk

Reply via email to