I totally agree with Wincent about tools. Most of the times you need to follow the vendors toolsuite. Which at the end might not be so bad, as it save us some energy to make it work.
But you can always build up your setup (I mean choosing your IDE and integrate the call of the makefile in there...);
My experience goes only in MCU.
Just to complement, the post of Wincent, I would like to add the Verification tools. There I have been using Helix QAC, PC-Lint to ensure coding compliance with MISRA-C and PolySpace for run-time errors check. In few cases gtest was also useful, due to its faster setup and feedback. of course, I am talking about unit tests.
One side note, I am in the automotive market, and there all the people does nowadays are subject to techincal audits, to ensure the quality, with this means not much freedom left for open source tools.
At home, arduino, beaglebone and terminal from ubuntu is enough for me :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I totally agree with Wincent about tools. Most of the times you need to follow the vendors toolsuite. Which at the end might not be so bad, as it save us some energy to make it work.
But you can always build up your setup (I mean choosing your IDE and integrate the call of the makefile in there...);
My experience goes only in MCU.
Just to complement, the post of Wincent, I would like to add the Verification tools. There I have been using Helix QAC, PC-Lint to ensure coding compliance with MISRA-C and PolySpace for run-time errors check. In few cases gtest was also useful, due to its faster setup and feedback. of course, I am talking about unit tests.
One side note, I am in the automotive market, and there all the people does nowadays are subject to techincal audits, to ensure the quality, with this means not much freedom left for open source tools.
At home, arduino, beaglebone and terminal from ubuntu is enough for me :)