How to proceed?
nishant
development of the IDE for the ARM processors.
But unfortunately we have not decided the strategy yet.
I think we should follow the Software Engineering way to design this
IDE.
What do all of you think about this?
during initial phase this might consume our little bit of efforts and
time,
but it will save lot of head ache, resources and time during our
actual work.
with regards,
NISHANT CHAWRE
+919763430098
tuxdna
> Hello friends, as per our discussion we have decided to start
> development of the IDE for the ARM processors.
> But unfortunately we have not decided the strategy yet.
> I think we should follow the Software Engineering way to design this
> IDE.
Rightly said, first lets figure out the requirements:
* The key idea is to integrate a code editor, code builder and a deployer
* code editor needs to be featureful for developing C/C++ code
* code builder needs to understand the project specific build files (
which maybe autoconf based or just plain makefile based )
* a deployer: this is the key component which we have to focus on
* the IDE which we would eventuall build should be usable on Windows,
Linux and MacOS
Let me recall about the requirements regarding "deployer". Basically
the deployer part needs to burn the hex code onto the microchip. Hex
code is what we get after building a project for microchip.
I had asked in an earlier mail if anyone could experiment with a real
device the former steps.
http://groups.google.com/group/armstrong-ide/browse_thread/thread/faf3604125364564
> What do all of you think about this?
> during initial phase this might consume our little bit of efforts and
> time,
> but it will save lot of head ache, resources and time during our
> actual work.
>
I think first lets try to get familiar with ARM build process and
deployment in general and then target the specific device. Sure its a
log way to go, lets explore!
I thought that we could use an ARM emulator ( say QEMU ) to do some
experimentation. It only helps to run programs for ARM architecture.
However our _key_ requirement is to be able to understand how to burn
hex code onto a chip.
Any suggestions on this?
Regards,
Saleem
Siddharth Sharangpani
Sorry for the delayed response, was tied up with some other work, yes we can start using the SDLC lifecycle if possible.
It would be although an overkill initially, but will help in getting lesser errors going forward.
Quick questions
Are we going to use Code blocks ? if i recollect properly
or are we going to use Python GTK +
Cheers
Sid