Замена STM32CubeIDE и переход в среду VSCode для Embedded-разработки

Бесплатных IDE для разработки микроконтроллеров не так уж много, а их интерфейс, основанный на Eclipse, вызывает у меня только страдания. В итоге разработка превращается в постоянное переключение с VSCode для редактирования кода в CubeIDE для его сборки и отладки. Но почему бы не собрать все инструменты в VSCode в едином расширении, заодно подогнав автогенерацию проектов под стиль компании/личные предпочтения? Об и будет моя первая статья. Привет, Хабр!

https://habr.com/ru/articles/1020160/

#xmake #cubeide #stm32 #vscode_extension

**Xmake v3.0.6 đã ra mắt!** 🚀
Hỗ trợ xây dựng ứng dụng native Android, tích hợp Flang (Fortran), và tạo gói AppImage/dmg dễ dàng. Cải tiến hiệu suất và nhiều tính năng mới cho lập trình viên.

#Xmake #LậpTrình #AndroidDev #Fortran #AppImage #DevTools #Coding #TechNews #PhầnMềm

https://www.reddit.com/r/programming/comments/1q3qk3z/xmake_v306_released_android_native_apps_flang/

People often complain that my coding style rule that you should not use abbreviations gives overly verbose code. I normally reply that:

• Code is written once and read many times, optimising for reading is better, and
• People have different preconceptions about what abbreviations may mean.

Today, I found a great example, in the #xmake codebase. The function that checks whether a code snippet in a C-family language compiles has the following set of options to pick the languages:

cc|cxx|mm|mxx

You will note that most of these are file extensions that the compiler will support with a default language inferred from the extension:

• cc: C++ file.
• cxx: C++ file.
• mm: Objective-C++ file.
• mxx: None.

In contrast, xmake treats them as:

• cc: C
• cxx: C++
• mm: Objective-C
• mxx: Objective-C++

If you see in the code sourcekind="mm", you would be forgiven for assuming that the code should be assumed to be Objective-C++, because that's what clang or gcc will assume a .mm file is.

It adds almost nothing to the verbosity of these to treat c as C, c++ as C++, objective-c as Objective-C, and objective-c++ as Objective-C++. Yet a person who sees sourcekind="objective-c" will be able to understand that the code should be treated as Objective-C with zero additional context.

Good news:

I've tracked down the commit that can be applied to #xmake 3.0.0 to fix it.

Bad news:

Apparently 3.0.0 had so many regressions that they aren't going to do a new release for a while yet because they want to fix them all.

And thus, hopefully, another project learns the value of putting out a call for testing before a major release.

Today I tried the #conan package repo feature on #codeberg 🥰 to publish sources and build artifacts from my #forgejo runners:
https://forgejo.org/docs/latest/user/packages/

It just works perfect and stores #c or #cpp libraries to be consumed by other projects. 👍

Package management is "the thing" why other languages had an advantage for a long time, it's really necessary to catch up here.
Next task: setup #xmake with #conan.

However ... now I finally need to think about proper versioning of commits and releases. 🥱

I really want to like #xmake, but when it deduplicates positional compiler flags added with `add_cflags` (even if I set `force = true`) because it doesn't know what they do, it's hard not to scream at it.

Simple rule of thumb: if you don't know what something is, don't modify it.

I started playing around with #xmake https://xmake.io/ some weeks ago.

I thought it is just #CMake written in #LUA, but it is totally different and for many scenarios easier to write.

Its greatest advantage is its package management feature, using #conan and many other online repositories.

I love it more and more every time I use it.