Frankly, when developing for embedded platforms, yes, IDEs are too much to 
ask for. 90% of embedded programming today is done with command-line tools 
as it has been for decades. Once in a while someone builds an IDE, but they 
are invariably so limited in application as to be more or a straightjacket 
than a real tool.  The amount of work it takes to produce a truly useful 
IDE makes sense only if you're developing on a commercial platform with 
millions of credit-card holding users. So if you want to develop for 
Windows, Android, and such, good IDEs are available. If you're programming 
a custom board, well, better get used to building your own tools.


On Friday, May 30, 2014 11:52:53 AM UTC-7, Simon Platten wrote:
>
> true, is it to much to ask to use an IDE?
>
> I have it all working for Java, would just like to do the same for C.
>
>
> On Friday, 30 May 2014 19:37:58 UTC+1, RobertCNelson wrote:
>>
>> On Fri, May 30, 2014 at 1:33 PM, Simon Platten <[email protected]> 
>> wrote: 
>> > I know C and C++ very well...I've been developing in it since the 80's. 
>> > 
>> > What I find difficult is the lack of complete information, is it to 
>> much to 
>> > expect that having bought the hardware for the software and 
>> documentation to 
>> > be complete? 
>> > 
>> > Sorry, I'm so fed up with dead ends...and pissy people with atitudes, 
>> that 
>> > instead of offering help, make wise cracks. 
>> > 
>> > Eclipse isn't the problem, the set-up of the toolchain is. 
>> > 
>> > Sorry, I guess you can tell, I'm a bit tired and just want to make some 
>> > progress on the project, instead of battling with the set-up. 
>>
>> You can always ssh in and build on the target.  That's just the way 
>> i've always done it. 
>>
>> Regards, 
>>
>> -- 
>> Robert Nelson 
>> http://www.rcn-ee.com/ 
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to