Hi,
I want to create my own stable IDE.I want to know how to do it???
I want to create my own stable IDE.
That's a very broad question. Let's start with a stable OS first.
What is "stable" in your opinion? What do you expect from that IDE?
I want to know how to do it???
We all do.
Well writing a (somewhat complete) IDE from scratch is very difficile task, mainly because of the sheer ammount of things it has to do to be functional, in fact for every drveloper IDE means a differenti thing which build system are are you going to support, which compiler and debugger remote debugging?
And alla of these features are what defines an IDE, otherwise you have only a glorified text editor
What i suggest doing is to start from a well known Open Source IDE that everyone loves to hate (eclipse), pick a version (the last stable?) fork it and start bugfxing until you have a relatively smooth experience, and than you are fine you have a stable IDE
Bonus points if you push the fixes to mainline
Yeah I can use Eclipse latest version Mars.Will that be stable in the sense without any bugs?I want to Basically use it for Kinetis microcontrollers.
My basic requirement is good debugging and good GUI for IDE which has many plug-ins like static and run-tiime analysis.
Please suggest me how to integrate Eclipse with GCC and any good debugger.
coide supports kinetics as well. You can also embed PE manually in your project.
Stepping back further, coide can be made to support pretty much any CMx chips - even if the IDE itself doesn't support them directly, as you can always manually add the support yourself.
coide supports kinetics as well.
I wouldn't go for coide, apart from being long dead (no updates in 8 months and just spam on the forums) it's always been quite buggy...much more than the base Eclipse.
If one wants to stay on Eclipse, and build on something already working, I would go for
Gnu Arm Eclipse plugins. All the source code is available.
Proprietary environments exist, with all kinds of prices, in addition to the free as in beer and as in freedom ones...
it's always been quite buggy
I have used coide since 1.3 and now am on 1.7, and with a few projects under its belt. I have had no problem with it. The project wizard is absolutely superb and I suspect was the inspiration behind Keil's RTT.
Since it is really GCC + Eclipse, you don't have to have CoIDE update going forward.
Another choice is emblocks -> I have been its user since day 1 - still on beta 1.0 - but almost exclusively with PIC24F. Absolutely love it.
Why do people want an IDE ?
The only use I've found for them is for a quick intro, where you lead the user through a series of simple exercises. They can be helpful there in providing a very controlled environment that corresponds directly to a tutorial. As soon as you want to get into something a bit more complex with a need for link control and more than one source directory, they mostly get in the way. And they present only a subset of the operating system's toolset, so as soon as you want to do something more general you're out of it.
Unix is the world's best IDE in the full sense of the phrase. It was designed by developers for their own purposes, and the vast majority of it is integrated through pipes or shared files. It isn't like what passes for an IDE in the GUI world : it's many times more integrated with the bits that really matter, while allowing complete generality in extensions.
Most of all, the project files are all of the form that can easily be handled by source code management - they're not intended to hold internal IDE state, but are the links between ascii-driven tools. Thus it's easy to look at differences between versions and store history in a useable form. This is essential for a professional development.
Eclipse seems to have set out to bring similar flexibility in a GUI world, but imho fails badly. It introduces extra dependencies and provides all sorts of facilities that merely replicate features of the operating system. I recently had the misfortune to work with an eclipse-based IDE that had constructed projects as a number of virtual directories. These were completely unmaintainable, with complex methods to find what was actually included and the need to introduce new files through the unintuitive IDE interface rather then by merely adding them via the familiar OS tools.
Why do people want an IDE ?
The answer is simple: code management. IDEs can be divided in 3 basic categories:
1) editor with compile button stuck on it and tools to aid the build process
2) 1 and debugging
3) 1 and 2 and code management and version control integration
Code management (finding functions, call hierarchies, finding defines, realtime syntax checking, etc) helps to work through huge projects quickly. Version control integration makes it easy to deal with various versions and look for differences/updates. Eclipse falls into category 3 and improves productivity a lot. Sure you can do everything using command line tools but for general use that is way to cumbersome. Only for very special cases command line tools offer an advantage.
Why do people want an IDE ?
ease of use, retargeting and project management.
the largest project I ever compiled is a motor cycle speedo project: CMSIS, vendor libraries, RTT, corporate middleware, emwin, a file system + an os layer, plus imagine files. a few hundred files, and 1MB+ flash. It took 15 - 20 minutes to compile on Keil.
it would be a little tough to navigate through such a project.
Why do people want an IDE ?
The only use I've found for them is for a quick intro
how do you debug? i'm guessing if you dont have a need for interactive debug, then you havent been quick intro'ed with real world softwares.. a software with one or two buttons and textboxes doesnt need debug, yes that one i agree...
Unix is the world's best IDE in the full sense of the phrase. It was designed by developers for their own purposes,
so is that the reason why most top class engineering, artists, photography videography softwares are being developed in Windows? oooppssss sorry, in Unix/Linux?
maybe I am missing something here....I use eclipse as my primary IDE and I have had no major complaints with my projects on eclipse 4.x for variety of software development. Now, talking about STM HAL...thats a whole different issue 
He said "without
any bugs". No significant piece of software, including Eclipse, is completely bug free.
maybe I am missing something here....I use eclipse as my primary IDE and I have had no major complaints with my projects on eclipse 4.x for variety of software development. Now, talking about STM HAL...thats a whole different issue
He said "without any bugs". No significant piece of software, including Eclipse, is completely bug free.
lol gotcha; no harm in dreaming for a "bugs free software"
I thought maybe you were alluding something more specific regarding eclipse 3.8 vs 4.x versions since OP specifically referred to "mars" versions.
Some have used Notepad++ to create their own IDE, because writing plug-ins is fairly trivial and you can issue commands from it.
I debug in various ways - with a GUI debugger like Lautenbach, with printfs, with an oscilloscope. It all depends on the job. I don't mean that every tool has to be command-line (though that's always easier when you're doing a quick hack to convert things for automated builds), just that their communication works through text files. I enjoy using a good debugger and it's a perfectly respectable use-case for a GUI, as is a source-code editor or browser. But I don't need them all to be in the same tool, because that tends to give me a screen crowded with useless inactive subwindows when I'm doing another function.
One IDE I tried was Atollic : that tries to reconfigure its window to suit the job you're doing. Horribly confusing. And so pointless : you already have a windowing system capable of maintaining multiple contexts for you. Why build another one on top of it ?
so is that the reason why most top class engineering, artists, photography videography softwares are being developed in Windows? oooppssss sorry, in Unix/Linux?
No, that's because that's where they see their customers. Macs for art stuff. Engineering demos in Windows because it's the lowest common denominator - they can assume everyone will have access to one, and that's good enough for a demo. Consumer stuff for windows, because that's what 'family users' buy. The only puzzle is Autocad, which clings to Windows for some unknown reason. Probably because the big design tools all started on Sun and Apollo, moved off it because they got too expensive for their customers, and now don't have the wit to move back.
The answer is simple: code management. IDEs can be divided in 3 basic categories:
Only for very special cases command line tools offer an advantage.
But code management wants to be automated. A source browser is interactive, true. But that's mostly useful when you're introduced to a system (which could be important if you have a high staff turnover). Build systems, version control, test suites, are all better scripted, and command line (or text processing, more correctly) is easier for that.
Build systems, version control, test suites, are all better scripted, and command line (or text processing, more correctly) is easier for that.
This.
The big advantage of "command line" is that you can easily incorporate new tools into your environment. E.g., I can write a Python program to generate some C++, which then gets compiled into the build. Or calculate a bunch of code metrics, add them into a sqlite3 database, and generate reports from there. And if someone else writes some really interesting Lisp code to talk to the version control system (from inside emacs), I can use that too. Command-line pieces fit together easily because they all use text to get work done.
Extending an IDE is much harder because they're (generally) monolithic, written in annoying languages, and use obnoxious file formats to represent state information.
so is that the reason why most top class engineering, artists, photography videography softwares are being developed in Windows? oooppssss sorry, in Unix/Linux?
No, that's because that's where they see their customers. Macs for art stuff. Engineering demos in Windows because it's the lowest common denominator - they can assume everyone will have access to one, and that's good enough for a demo. Consumer stuff for windows, because that's what 'family users' buy. The only puzzle is Autocad, which clings to Windows for some unknown reason. Probably because the big design tools all started on Sun and Apollo, moved off it because they got too expensive for their customers, and now don't have the wit to move back.
With Linux desktop usage historically at never more than 2%, it's easy to see why few professional development package vendors go out of their way to support it.
That 2% is on average. In engineering the use of Linux is much more widespread. A poll on this forum indicated over 25% uses Linux as a primary OS. Xilinx wouldn't care to support Linux if only 2% of their users used Linux!
That 2% is on average. In engineering the use of Linux is much more widespread. A poll on this forum indicated over 25% uses Linux as a primary OS. Xilinx wouldn't care to support Linux if only 2% of their users used Linux!
Interesting. I suspect that a large proportion of the people on this forum are hobbyists. I wonder what percentage of professional developers use Linux?
Interesting. I suspect that a large proportion of the people on this forum are hobbyists. I wonder what percentage of professional developers use Linux?
For FPGA a lot. Both Xilinx and Altera tools work way better and fully utilize multicore systems on Linux. But with Xilinx tools, you can also see that they were originally developed for UNIX. Some of really old stuff shines through in places
That does not apply for free Web-editions, which are locked to a single core anyway.
It also helps that the rest of the toolchain from third-party vendors (like Multisim) are also fully supported on Linux.
Kinetis Design studio is vanilla Eclipse + gnu arm embedded + open OCD in a nice package. Save you self some time and just use it. It is all open source if you feel like working on an IDE