nanogui: NanoX -- Recommended development approach?
Subject:
RE: [nanogui] NanoX -- Recommended development approach?
From:
"Martin Kajdas" ####@####.####
Date:
24 Jul 2007 16:27:36 +0100
Message-Id: <CF2BB830A62F914F848E5AD5FFF57AC229160A@mkmail.MKPROD.COM>
I think your email is a little confusing.
Are you asking about the development platform or embedded target
platform.
From the development stand point it does not matter too much but I think
it is a lot easier if the development platform is the same or close to
the target platform.
I stopped using Windows for all embedded stuff 4 years ago and I could
not be happier.
I use Linux as a development platform as well as a target platform.
I do not cross compile because my target is i386 based.
I use Kdevelop as IDE but you can also use Eclipse on Linux.
The hardest part is to get the Linux started on the target.
Because everything runs from flash memory (in my case), you have to hack
Linux Kernel to start from your specific hardware.
In my case, it took about 50 lines of kernel code changes to get Linux
booting into text console which is already running in VGA graphics frame
buffer mode set by the kernel.
After that, I just start nanoX and my app linked with libnx.
I do not do anything special for nanoX nor libnx to run and the only
difference in my app between the embedded platform and the PC platform
are some calls to the driver that interfaces to my specific hardware.
Martin
-----Original Message-----
From: ####@####.#### ####@####.#### On Behalf Of
Ricardo Jasinski
Sent: Monday, July 23, 2007 7:53 AM
To: ####@####.####
Subject: [nanogui] NanoX -- Recommended development approach?
Good morning everyone,
I believe I've seen someone mention that you could develop an
application in Linux with nanox, and later cross-compile it to an
embedded target.
Maybe someone could explain this with a little detail? I've been doing
all development under Windows, from within my microcontrollers IDE which
is based on Eclipse. Up til now, I've compiled all nanox source code
together with my application, but I dislike this approach because
whenever there's a new version out there it requires a lot of
"adjustments".
Any thoughts are welcome!
Sincerely,
Ricardo Jasinski.
