http://www.eiffelroom.com/tag/smartphone Comments for "smartphone" en http://www.eiffelroom.com/blog/donthb/looks_like_i_have_to_use_the_blog_to_post_a_question#comment-327 <p>Looks like some of my questions have been answered over at <a href="http://groups.eiffel.com">http://groups.eiffel.com</a>.</p> <p>Thanks again.</p> Tue, 11 Sep 2007 11:22:02 -0700 DonTHB comment 327 at http://www.eiffelroom.com http://www.eiffelroom.com/blog/donthb/looks_like_i_have_to_use_the_blog_to_post_a_question#comment-326 <p>For the moment, I believe it is best to subscribe to the Eiffel Software mailing list at <a href="http://groups.eiffel.com">http://groups.eiffel.com</a> for such questions. The blog was not exactly designed for that purpose.</p> <p>Porting the Eiffel runtime to a new platform is usually relatively easy assuming that your platform has a decent C compiler (i.e. ANSI C) and that the platform provides some of the basic API that you can find on most operating systems, i.e: <ul> <li> malloc, free for memory allocation</li> <li> read/write/fopen/... for file/network access</li> <li> other APIs that the runtime may need can also be excluded</li> </ul> </p> <p>Currently, Eiffel Software supports the VxWorks tool chain for embedded development. It has been successfully used on HPPA and PowerPC architecture.</p> <p>The way we do it is that you develop on either your platform of choice with EiffelStudio. Then you take the C generated code and compile it for your target platform. Debugging is somewhat limited to C debugging but the generated code is following pretty closely your Eiffel code. If you can define some macros with your debugger then it makes it even easier.</p> <p>Hope this helps, Manu</p> Mon, 10 Sep 2007 10:35:00 -0700 manus_eiffel comment 326 at http://www.eiffelroom.com