MPLABX, eclipse and netbeans are biggest pieces of shit software in the world, fucken a I can’t stand this slowness, over bloat, locking up, and the unable to resolve bullshit,

(Porting a suppliers project and build script over to a simple makefile, and so the project can open and build in sublime or vim rather these other bullshit IDES

📌

> Bloated, slow, unintuitive
> uses Make

@12bitfloat wtf is wrong with make ?

@QuanticoCEO About everything

@12bitfloat and what would you suggest to use? For a build system?

@QuanticoCEO They all kinda suck. I wish we had a general purpose Gradle but in not retarded

@12bitfloat I will agree a better way to build would be nice, but really makefiles are just scripts of what you would do if you compiled it manually... so idk. Make doesn’t bother me.. I’ve never tried Cmake with make ... but I only do embedded c stuff so gradle isnt an option lol

@QuanticoCEO if you have a largeish project I can recommend Ninja as a build system, it's hilariously fast. Not great for manual hacking though, Make is still superior for that.

Ninja isn't meant to be written by hand, you should use a custom script or a tool like CMake to generate it (the linked document describes Ninja as "Where other build systems are high-level languages, Ninja aims to be an assembler.")

https://ninja-build.org/manual.html

@RememberMe hmmm thank you for that information, I’m going to look further into this, I’ll do some testing and stuff to see it’s viability for our use case, and if it is superior to make then I’ll get our team to switch...

Side note...

I started working with this team a year ago

Most of my team of 35 or so folks are “of the older generation” stuck in their ways, and have been doing stuff the same way with minimal change over the last 20 years.

We’re an embedded automotive supplier so I’m not super surprised about that, but since I started with this team about a year ago, I have pushed them into the “modern” age, lol ... got them started using versioning control systems, first SVN, due to corporate aspect of centralized, but we have recently switched to HelixCore we found their ability and way of versioning binary files like ECAD and documents. Along with workflow implementation. Was better than git and SVN combined.

I got them using HelixQAC static analysis, helixALM, and Helix Swarm (because of the requirements, issue AND test case management) which was better than my first choice of Atlassian stack.

I’ve converted our group to more modular code, their was zero reusability of code prior and no traceability, on both electrical schematics and software. Everyone thought in terms of “main” literally everything was in main.c 50k-1000k line main.c ...

I’ve gotten use doing unit tests and now I’m finally working on getting us to use Jenkins for automation.

Lol sooo with all these changes in the last year I’m actually surprised my team has “keep“ up with my “young blood” lol but they have been very adaptive compared to teams I’ve seen in the past. It might be because of my experience for my age they trust me more, not sure..

But I’ll look into this Ninja stuff for sure