# CMake CMake is a software build system for building C++ code and managing the software build process. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## В OpenIDE появилась поддержка C/C++ благодаря независимому разработчику DevFeed: [В OpenIDE появилась поддержка C/C++ благодаря независимому разработчику]() Original publisher: [Read original article]() Author: honest\_niceman (Haulmont) Published: 2026-09-16T15:22:55Z Content type: news Language: ru Sources: [Tagir Valeev]() Topics: [c/c++](), [CMake]() Tags: [c](), [c-c-plus-plus](), [c-plus-plus](), [clangd](), [cmake](), [ide-c-plus-plus-5a4cbf95fd05](), [intellij-platform](), [openide](), [rdev](), [tag-a071763eb5bb]() ### AI overview OpenIDE's marketplace has published the C/C++ Support plugin, created by an independent community developer. The beta plugin provides code completion, syntax highlighting, navigation, symbol renaming, project creation, and CMake-based compilation and builds. ### Source excerpt В маркетплейсе OpenIDE появился плагин C/C++ Support, для работы с C и C++. Его написал независимый разработчик из сообщества. Поддержку C++ пользователи просили давно, и автор решил не ждать, а взяться за неё самостоятельно. Читать далее ## What's New for C++ Developers in Visual Studio 2026 (18.7 - 18.10) DevFeed: [What's New for C++ Developers in Visual Studio 2026 (18.7 - 18.10)]() Original publisher: [Read original article]() Author: Augustin Popa Published: 2026-09-14T06:38:16Z Content type: article Language: en Sources: [C++ Team Blog]() Topics: [Visual Studio 2026](), [C++](), [GitHub Copilot](), [MSVC](), [AI-assisted coding](), [CMake](), [Git](), [Submodules]() Tags: [2026](), [build-optimization](), [c-plus-plus](), [cmake](), [copilot](), [git](), [modernization](), [msvc](), [submodules](), [testing](), [tools](), [visual-studio](), [visual-studio-2026]() ### AI overview This Microsoft C++ Team Blog post recaps Visual Studio 2026 versions 18.7 through 18.10 for C++ developers. It covers C++ reliability fixes, GitHub Copilot modernization for upgrading MSBuild and CMake projects to newer MSVC Build Tools, improved code navigation, discoverable MSVC Build Tools installations, Git worktrees and submodules in the IDE, and debugging improvements. ### Source excerpt Over the past few months, we have continued shipping monthly Visual Studio 2026 releases, delivering improvements across all stages of the development cycle. In this blog post, we'll recap everything that changed from version 18.7 through 18.10 (released this month) that is relevant for C++ developers. This includes new tools for maintaining and navigating C++ [...] The post What's New for C++ Developers in Visual Studio 2026 (18.7 - 18.10) appeared first on C++ Team Blog. ## Microsoft at CppCon 2026 DevFeed: [Microsoft at CppCon 2026]() Original publisher: [Read original article]() Author: Augustin Popa Published: 2026-09-14T00:16:42Z Content type: news Language: en Sources: [C++ Team Blog]() Topics: [C++](), [Microsoft](), [Visual Studio](), [Visual Studio 2026](), [GitHub Copilot](), [MSVC](), [Visual Studio Code](), [Artificial Intelligence](), [Optimization](), [CMake]() Tags: [ai](), [c-plus-plus](), [cmake](), [copilot](), [cppcon](), [github-copilot](), [microsoft](), [msvc](), [optimization](), [safety](), [survey](), [visual-studio](), [visual-studio-2026]() ### AI overview Microsoft's CppCon 2026 sessions cover modern C++ development, including AI-assisted workflows, MSVC, Visual Studio, Visual Studio Code, compiler optimization, C++ safety, and stricter compiler warnings. The article also provides conference logistics, speaker sessions, and a survey invitation. ### Source excerpt Microsoft will be at CppCon 2026 in Aurora, Colorado, which is taking place from September 14 through 18. Join us for talks from Microsoft speakers and colleagues across the C++ community and visit the Microsoft booth Monday through Thursday to meet the team and discuss the tools, technologies, and challenges that matter to you. If [...] The post Microsoft at CppCon 2026 appeared first on C++ Team Blog. ## C++-техрадар: что разработчики действительно готовы брать в работу DevFeed: [C++-техрадар: что разработчики действительно готовы брать в работу]() Original publisher: [Read original article]() Author: Kaspersky\_Lab ("Лаборатория Касперского") Published: 2026-08-07T13:17:24Z Content type: article Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [C++](), [CMake](), [PostgreSQL]() Tags: [bash](), [bazel](), [c-plus-plus](), [clang](), [cmake](), [gdb](), [git](), [plus-plus-3a0baa67a2fc](), [postgresql](), [tech-radar](), [vs-code]() ### AI overview The article analyzes the C++ portion of a technical radar based on survey responses from developers at C++ Russia and HolyJS. It explains how technologies are assessed across Adopt, Trial, Assess, and Hold categories, emphasizing that the overall distribution of votes matters more than a single dominant response. The supplied evidence specifically notes CMake as a strong performer and PostgreSQL as dividing respondents. ### Source excerpt В мае на конференциях C++ Russia и HolyJS мы предложили участникам оценить технологии, инструменты и инженерные практики, с которыми они работают или за которыми следят. Так появились данные для двух технических радаров: по экосистеме C++ и по JavaScript. Сырые цифры сами по себе рассказывают немного, поэтому мы отдали результаты на разбор эксперту. Виктор Новиков, руководитель группы разработки в "Лаборатории Касперского", посмотрел на распределения голосов и поделился своим мнением, почему CMake уверенно побеждает, а PostgreSQL раскалывает аудиторию пополам. В этой статье -- его анализ C++-части исследования. Про техрадар JavaScript мы расскажем в другой статье. Посмотреть радар и принять участие в голосовании можно на странице проекта. Читать далее ## Vulkan SC SDK Released: An Integrated Toolchain for Vulkan Safety-Critical Development DevFeed: [Vulkan SC SDK Released: An Integrated Toolchain for Vulkan Safety-Critical Development]() Original publisher: [Read original article]() Author: Khronos Group (webservices@khronosgroup.org) Published: 2026-05-06T13:00:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [SDK](), [toolchain](), [Development](), [Linux](), [Windows](), [CMake]() Tags: [api](), [blog-vulkans](), [building](), [cmake](), [components](), [configuration](), [developer-experience](), [developers](), [development](), [download](), [ecosystem](), [getting-started](), [install](), [installation](), [integration](), [linux](), [sdk](), [toolchain](), [tools](), [vulkan](), [vulkan-sc](), [windows]() ### AI overview The Vulkan SC SDK is a unified installer for tools supporting safety-critical application development. It provides Linux and Windows installers, optional environment setup, CMake integration, pipeline cache compiler discovery, and components including the Vulkan SC loader, emulation and validation layers, device simulation, utilities, and samples. Version 1.0.21 is available on GitHub. ### Source excerpt Developers building safety-critical applications can now get started with Vulkan® SC faster than ever. The new Vulkan SC SDK is a simpler way to install and use a comprehensive set of tools and utilities to leverage the Vulkan SC ecosystem. With installers for Linux and Windows, the SDK makes it easy for developers to get up and running quickly, whether they are just getting started with Vulkan SC or building on existing deployments. ## ESP-IDF: Propagating compiler flags to ExternalProject builds DevFeed: [ESP-IDF: Propagating compiler flags to ExternalProject builds]() Original publisher: [Read original article]() Author: John Lee Published: 2026-04-27T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [CMake](), [Compiler]() Tags: [blog](), [build](), [build-system](), [cmake](), [compiler](), [compiler-flags](), [esp-idf]() ### AI overview This ESP-IDF post explains why compiler options driven by Kconfig and components do not automatically propagate to ExternalProject_Add() builds. It describes using response files tied to the appropriate build context to keep compiler flags aligned between the outer and nested CMake projects. ### Source excerpt When an ESP-IDF project uses ExternalProject_Add(), compiler options driven by Kconfig and components do not flow into the nested build on their own. This post walks through why that happens and how to keep the outer and inner CMake worlds aligned. ## dcmake: a new CMake debugger UI DevFeed: [dcmake: a new CMake debugger UI]() Original publisher: [Read original article]() Published: 2026-04-07T03:04:02Z Content type: article Language: en Sources: [Chris Wellons]() Topics: [CMake](), [debugging](), [GUI](), [Visual Studio](), [Software Engineering]() Tags: [ai](), [cmake](), [cpp](), [debugger](), [engineering-productivity](), [linux](), [macos](), [ui](), [visual-studio](), [windows]() ### AI overview The article introduces dcmake, a cross-platform native GUI debugger for CMake's debugger mode. It describes its DAP-based interaction, Dear ImGui interface, Visual Studio-inspired controls, persistent UI state, and use of AI to accelerate development. ### Source excerpt CMake has a --debugger mode since 3.27 (July 2023), allowing software to manipulate it interactively through the Debugger Adaptor Protocol (DAP), an HTTP-like protocol passing JSON messages. Debugger front-ends can start, stop, step, breakpoint, query variables, etc. a live CMake. When I came across this mode, I immediately conceived a project putting it to use. Thanks to recent leaps in software engineering productivity, I had a working prototype in 30 minutes, and by the end of that same day, a complete, multi-platform, native, GUI application. I named it dcmake ("debugger for CMake"). I've tested it on macOS, Windows, and Linux. Despite only being couple days old, it's one of the coolest things I've ever built. Prior to 2026, I estimate it would have taken me a month to get the tool to this point. It has a Dear ImGui interface, which I've experienced as a user but never built on myself before. Specifically the docking branch. In a sense it's a toolkit for building debuggers, so it's playing an enormous role in how quickly I put this project together. All of the "windows" tear out and may be free-floating or docked wherever you like, closely matching the classic Visual Studio UI. I borrowed all the same keybindings: F10 to step over, F11 to step in, F5 to start/continue, shift+F5 to stop. Click on line numbers to toggle breakpoints, right click to run-to-line, hover over variables with the mouse to see their values. Nearly every every UI state persists across sessions, and it opens nearly instantly. This is just one of many situations I've used AI the past month for UI development, and it's been shockingly effective. I can describe roughly the interface I want, and the AI makes it happen in a matter of minutes. It understands what I mean, filling in the details, sometimes anticipating what I'll ask for next. If I'm unsure how I want a UI to work, it also offers good advice. If I need simple icons and such, it can draw those, too. It's all incredibly empowering. On ## Manage multiple ESP-IDF build configurations with ease DevFeed: [Manage multiple ESP-IDF build configurations with ease]() Original publisher: [Read original article]() Author: John Lee Published: 2025-12-05T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [configuration](), [CMake](), [Command-line interface](), [Testing]() Tags: [blog](), [build-system](), [cmake](), [command-line](), [configuration](), [esp-idf](), [how-to](), [sdkconfig]() ### AI overview This tutorial explains how ESP-IDF v6.0 build configuration presets simplify switching among development, production, and testing builds. It covers reusable JSON-based settings, CMake Presets support, and separate build directories for parallel configuration management. ### Source excerpt Tired of juggling complex command-line arguments with endless idf.py flags? ESP-IDF v6.0 introduces a new feature, letting you switch between multiple build configuration. Learn how to structure your project, isolate sdkconfig files, and migrate from ad-hoc commands to clean, declarative builds. ## Advanced techniques for porting libraries to ESP-IDF components DevFeed: [Advanced techniques for porting libraries to ESP-IDF components]() Original publisher: [Read original article]() Author: John Lee Published: 2025-11-24T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Library](), [AWS IoT Core](), [OpenSSH](), [WebSocket](), [aio](), [CMake](), [make](), [POSIX]() Tags: [blog](), [cmake](), [compiler](), [component](), [components](), [esp-idf](), [feature-flags](), [library](), [linux](), [mqtt](), [porting](), [posix](), [ssh](), [systems](), [techniques]() ### AI overview This follow-up article presents advanced techniques for porting larger libraries, particularly those designed for Linux or POSIX systems, into reusable ESP-IDF components. It covers assessing reusable code, adapting build systems and port layers, configuration, header injection, linker wrapping, and compiler-warning management, with examples including asio, mosquitto, libssh, and libwebsockets. ### Source excerpt This article follows up on the article 'Porting a library to an ESP-IDF component' and shows some advanced tips and tricks when porting larger libraries into ESP-IDF components. ## ESP-IDF Tutorials: Basic HTTP server DevFeed: [ESP-IDF Tutorials: Basic HTTP server]() Original publisher: [Read original article]() Author: John Lee Published: 2025-06-26T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [HTTP](), [Espressif](), [servers](), [HTML](), [CMake](), [browser]() Tags: [article](), [blog](), [browser](), [cmake](), [devices](), [esp](), [esp-idf](), [espressif](), [html](), [http-server](), [practitioner](), [tutorial](), [tutorials]() ### AI overview This tutorial explains how to set up a basic HTTP server with ESP-IDF, create a URI route that serves an HTML page, and view that page in a web browser on Espressif devices. ### Source excerpt This article shows how to create a simple HTTP server. It explains the functions you need and the setup required. After reading this, you should be able to create your own HTTP server on Espressif devices. ## A Year of Rust in ClickHouse DevFeed: [A Year of Rust in ClickHouse]() Original publisher: [Read original article]() Author: Alexey Milovidov Published: 2025-04-01T00:00:00Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Rust](), [C++](), [CMake](), [Programming]() Tags: [applications](), [c-plus-plus](), [clickhouse](), [cmake](), [code](), [components](), [integration](), [libraries](), [programming](), [rust]() ### AI overview The article describes adding Rust support to ClickHouse without rewriting the existing C++ codebase. It covers integrating Rust components with the CMake build system, interoperating with C++, and using the BLAKE3 hash function as an initial integration component. ### Source excerpt This story is about how ClickHouse supports Rust components in the C++ code base and the challenges we had to overcome. ## What is the ESP Component Registry? DevFeed: [What is the ESP Component Registry?]() Original publisher: [Read original article]() Author: John Lee Published: 2024-11-08T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Development](), [Command-line interface](), [Code](), [CMake]() Tags: [architecture](), [article](), [blog](), [cli](), [cmake](), [component](), [components](), [dependencies](), [development](), [esp-idf](), [libraries](), [registry](), [reuse]() ### AI overview This article explains the ESP Component Registry and the concepts behind it: components, the component manager, and the registry. It describes how reusable components support ESP-IDF projects and how the component manager adds dependencies, creates component structures, and downloads dependencies during CMake builds. ### Source excerpt When starting a new project, we often reuse existing code, for example from libraries and drivers. This not only saves time but also makes your project easier to maintain. In this article, we will explore what the ESP Component Registry is and the key concepts of components, making it easy to understand not only how to use components but also how to contribute. Concept# The architecture of ESP-IDF is modular, making it easier to understand and maintain. ## Blog: Falco Weekly 10 - 2024 DevFeed: [Blog: Falco Weekly 10 - 2024]() Original publisher: [Read original article]() Published: 2024-03-08T00:00:00Z Content type: news Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [Kernel](), [API](), [CMake](), [Compiler](), [Testing]() Tags: [blog](), [bugfixes](), [falco](), [news](), [weekly]() ### AI overview Falco's weekly recap reports that the project graduated and reviews changes across its repositories, including the kmod configure system, a CRI API refactor, compiler sanitizer options, crash and file-descriptor fixes, new tests, and configuration and validation changes in Falco. ### Source excerpt What happened in Falco this week? First of all, you probably already heard it, Falco is now graduated! If you missed this important news, go ahead and give our graduation blog post a read! Let's go through the major changes that happened in various repositories under the falcosecurity organization during the last week. Libs We are approaching the 0.15.0 tag, therefore mostly bugfixes were merged, plus a great new feature and some refactors: The so-called "kmod configure system" was finally merged: https://github.com/falcosecurity/libs/pull/1452. This helps us to ensure that our kernel module builds even when some features get backported from more recent kernels (ie: when checking for kernel release version in the code is not enough). Kudos to Angelo Puglisi for shipping such a feature! Also, keep an eye for the very same thing for bpf too: https://github.com/falcosecurity/libs/pull/1729! Thanks to the kmod configure system, our kernel-testing matrix is now fully green for kmod! A big CRI API refactor finally landed: https://github.com/falcosecurity/libs/pull/1600 Proceeding with the journey around compiler sanitizers, we now have proper cmake options to enable ASAN and UBSAN: https://github.com/falcosecurity/libs/pull/1721 Fixed a crash when reading proclist from scap: https://github.com/falcosecurity/libs/pull/1726 Fixed some socketpair fds problems: https://github.com/falcosecurity/libs/pull/1733 Fixed and added some more tests: https://github.com/falcosecurity/libs/pull/1736, https://github.com/falcosecurity/libs/pull/1727 Falco Some small changes happened too, in Falco main repository: The proposal about features adoption and deprecation was merged: https://github.com/falcosecurity/falco/pull/2986! Added a new configuration key falco_libs.thread_table_size to customize max thread table size in libsinsp: https://github.com/falcosecurity/falco/pull/3071 Throw an error when an invalid macro/list name is used: https://github.com/falcosecurity/falco/pull/3116 Fixed u ## Blog: Falco Weekly 4 - 2024 DevFeed: [Blog: Falco Weekly 4 - 2024]() Original publisher: [Read original article]() Published: 2024-01-26T00:00:00Z Content type: article Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [C++](), [eBPF](), [CMake](), [Gke]() Tags: [c-plus-plus](), [cmake](), [deadlock](), [deprecated](), [ebpf](), [enum](), [falco](), [gke](), [process](), [release](), [testing]() ### AI overview This weekly Falco recap covers changes across the falcosecurity repositories, including the Falco 0.37.0-rc2 release, a performance-driven reversion to the older sorcery implementation, library fixes, driver and logger improvements, and updates to falcoctl and rules. It also notes experimental plugin and engine features and invites community feedback. ### Source excerpt What happened in Falco this week? Let's go through the major changes that happened in various repositories under the falcosecurity organization. Libs Libs will need a 0.14.2 tag for the Falco 0.37.0 release, with the revert of https://github.com/falcosecurity/libs/pull/1533 PR. During our release process, we found out that the new std::filesystem based implementaton was up to 8x time slower than the old ones; that's because it supports much more cases and does many more checks. Therefore, in https://github.com/falcosecurity/libs/pull/1645, we revert to the old sorcery implementation, plus some minor improvements and added tests. Moreover, many more changes landed in libs, that won't be part of the upcoming Falco 0.37.0 release: Modernized C++ struct/enum/union declarations: https://github.com/falcosecurity/libs/pull/1588 Added support for newfstatat syscall: https://github.com/falcosecurity/libs/pull/1628 Fixed a potential deadlock for kmod: https://github.com/falcosecurity/libs/pull/1629 Big effort by our hero, Jason, to cleanup some stale macros: https://github.com/falcosecurity/libs/pull/1633,https://github.com/falcosecurity/libs/pull/1634,https://github.com/falcosecurity/libs/pull/1635,https://github.com/falcosecurity/libs/pull/1637,https://github.com/falcosecurity/libs/pull/1638 A small fix for old ebpf driver to support some GKE envs: https://github.com/falcosecurity/libs/pull/1642 Solved a data race and segfault in logger: https://github.com/falcosecurity/libs/pull/1643 Allow to selectively disable bpf and kmod engines from cmake: https://github.com/falcosecurity/libs/pull/1644 Falco Falco tag 0.37.0-rc2 is out! Try it! Moreover: syscall_event_drops was soft-deprecated to get ready for Falco 0.38.0 upcoming cleanups: https://github.com/falcosecurity/falco/pull/3015 Avoid storing escaped strings in engine: https://github.com/falcosecurity/falco/pull/3028 Bumped falcoctl to v0.7.1 and rules to 3.0.0: https://github.com/falcosecurity/falco/pull/3030,https://gith ## Blog: Falco Weekly 46 - 2023 DevFeed: [Blog: Falco Weekly 46 - 2023]() Original publisher: [Read original article]() Published: 2023-11-17T00:00:00Z Content type: article Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [Development](), [ci](), [CMake](), [openssl](), [osx](), [win32]() Tags: [blog](), [changes](), [ci](), [cmake](), [falco](), [openssl](), [osx](), [weekly](), [win32]() ### AI overview Falco Weekly 46 reviews development changes across Falco-related repositories, including library cleanups, fixes, new features, experimental ppc64le support, an OpenSSL upgrade, CI support for win32 and osx, and Kubernetes metadata work involving gRPC. ### Source excerpt This is the first of a series of weekly blog post whose aim is to give a quick overview about the development of Falco and its related projects. What happened in Falco this week? Let's go through the major changes that happened in various repositories under the falcosecurity organization. Libs Lots of cleanups happened in the libs repo; the most outstanding ones being: udig engine removal (https://github.com/falcosecurity/libs/pull/1485) dropped legacy metadata clients for k8s and mesos (https://github.com/falcosecurity/libs/pull/1478) cleaned up proc callback handling code (https://github.com/falcosecurity/libs/pull/1471) Please, note that the removal of the legacy k8s client is part of a bigger effort to entirely rewrite it as a plugin, with a more future proof architecture and language. See the tracking issue: https://github.com/falcosecurity/libs/issues/987. All of these cleanups account for ~26k loc removed!! :rocket: Moreover, some fixes landed: removed some more Undefined Behavior warnings from integer copies (https://github.com/falcosecurity/libs/pull/1481) solved win32 linking issues with zlib (https://github.com/falcosecurity/libs/pull/1484) prevent libbpf stats from being collected with no bpf stats (https://github.com/falcosecurity/libs/pull/1487) Finally, some new features were merged: libraries will now be properly installed under CMAKE_INSTALL_LIBDIR (https://github.com/falcosecurity/libs/pull/1101) added ppc64le experimental support for modern bpf driver (https://github.com/falcosecurity/libs/pull/1475) upgraded openssl to 3.1.4 (https://github.com/falcosecurity/libs/pull/1488) Also, we now have a target release date and a tracking issue for libs 0.14 and next driver release: https://github.com/falcosecurity/libs/issues/1482. Falco Now Falco builds and runs on win32 and osx too! https://github.com/falcosecurity/falco/pull/2889 While Falco won't ship for these platforms, we will now have proper CI for them. Following the huge round of cleanups in libs ## Espressif-IDE 2.8.0 Adds Partition Editors, Build Configurations, and Debugger Improvements DevFeed: [Espressif-IDE 2.8.0 Adds Partition Editors, Build Configurations, and Debugger Improvements]() Original publisher: [Read original article]() Author: John Lee Published: 2023-02-01T00:00:00Z Content type: release Language: en Sources: [Blog on Developer Portal]() Topics: [Espressif IDE](), [ESP-IDF](), [configuration](), [debug](), [CMake]() Tags: [blog](), [bug-fixes](), [cmake](), [configuration](), [debug](), [eclipse](), [esp-idf](), [espresif-ide](), [espressif](), [espressif-ide](), [espressif-ide-2-8-0](), [new-features](), [ui](), [windows]() ### AI overview Espressif-IDE 2.8.0 introduces partition table and NVS table editors, support for multiple build configurations, and a remote GDB timeout adjustment. The release also includes debugger configuration enhancements, bug fixes, and installation guidance for Windows, macOS, and Linux users. ### Source excerpt Espressif-IDE 2.8.0 was released recently, featuring a Partition table editor NVS Partition Editor along with enhancements in the Debugger Configuration and many more bug fixes to stabilize and improve the overall quality of the plugin. You can get the latest version using the update site, but if you're starting for the first time and you're a Windows user, I would recommend using the Espressif-IDE Windows Offline installer which does most of the work of installing all the prerequisites,... ## Релиз CLion 2021.2: улучшения в отладчике, проверка времени жизни объектов, поддержка CMake Presets DevFeed: [Релиз CLion 2021.2: улучшения в отладчике, проверка времени жизни объектов, поддержка CMake Presets]() Original publisher: [Read original article]() Author: anastasiak2512 (JetBrains) Published: 2021-07-29T13:29:29Z Content type: release Language: ru Sources: [JetBrains RU]() Topics: [CLion](), [C++](), [CMake](), [ide](), [Windows Subsystem for Linux](), [MSVC]() Tags: [autotools](), [c-plus-plus](), [cling](), [clion](), [cmake](), [debugger](), [freertos](), [ide](), [lifetimes](), [make](), [msvc](), [windows](), [wsl]() ### AI overview JetBrains presents CLion 2021.2, a cross-platform IDE for C and C++. The release adds protection against common C++ memory-access problems, CMake Build Presets support, GNU Autotools project support, remote-host and WSL profiling, debugger improvements, and Cling integration. ### Source excerpt Привет, Хабр! В конце июля в JetBrains стартует очередной релизный "паровоз". На этой неделе обновились многие IDE на платформе IntelliJ, на следующей запланированы обновления наших продуктов для .NET. И сегодня мы хотим поговорить о CLion 2021.2 -- новейшей версии нашей кроссплатформенной IDE для разработки на C и C++. Коротко о главном. CLion 2021.2 защитит ваш код от типичных проблем доступа к памяти в C++, автоматически загрузит настройки сборки приложения из CMake Build Presets, откроет проект с использованием GNU Autotools, поможет с профилированием на удаленном хосте и на WSL. Кроме того, значительно улучшен отладчик (самые крупные обновления ждут наших пользователей на Windows). А для тех, кто пока только изучает C++ или прототипирует новое приложение или библиотеку, мы добавили интеграцию с Cling -- интерпретатором С++. Дьявол в деталях ## ReactOS in 2020 DevFeed: [ReactOS in 2020]() Original publisher: [Read original article]() Published: 2021-01-02T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Kernel](), [build tools](), [CMake](), [Filesystems](), [gcc](), [Shell](), [clang](), [Command-line interface](), [MSVC](), [GitHub]() Tags: [c-plus-plus](), [ci](), [clang](), [cmake](), [command-line](), [filesystem](), [free](), [gcc](), [github](), [kernel](), [msvc](), [open-source](), [os](), [react](), [reactos](), [shell](), [tooling](), [upgrade](), [win32](), [winapi]() ### AI overview A 2020 retrospective on ReactOS reports bug fixes, new instabilities, full-time kernel hires, shell improvements, RAPPS application-manager enhancements, and upgrades to its compiler and build tooling. It covers GCC 8.4, CMake 3.17, restored Clang CI builds, reduced older MSVC support, and a move to the C99 standard. ### Source excerpt Despite all the turbulence, it has been quite a productive year for ReactOS. Many bugs and instabilities were resolved, many more have been introduced. This year we hired two kernel developers full-time, this happened for the first time in the project's history. The post highlights some of the changes which may be interesting to the community. Shell changes Shell hasn't seen much attention recently, due to most of the work being concentrated in the kernel, but there are still some useful fixes and feature implementations: ## A New Cross-Platform Open Source C++ Framework DevFeed: [A New Cross-Platform Open Source C++ Framework]() Original publisher: [Read original article]() Author: Jeff Preshing Published: 2020-05-26T11:50:00Z Content type: article Language: en Sources: [Jeff Preshing]() Topics: [C++](), [Framework](), [cross-platform](), [Open Source](), [CMake](), [Containers](), [Processes]() Tags: [c-plus-plus](), [cmake](), [containers](), [cross-platform](), [framework](), [modular](), [open-source](), [process]() ### AI overview The article introduces Plywood, a cross-platform open-source C++ framework released from a custom game engine. Plywood provides a workspace for multiple applications, built-in modules for I/O, containers, and process creation, plus runtime reflection and serialization. It uses CMake internally and runs on Windows, Linux, and macOS. ### Source excerpt For the past little while - OK, long while - I've been working on a custom game engine in C++. Today, I'm releasing part of that game engine as an open source framework. It's called the Plywood framework. View the documentation View on GitHub Please note that Plywood, by itself, is not a game engine! It's a framework for building all kinds of software using C++. For example, Plywood's documentation is generated with the help of a C++ parser, formatted by a Markdown parser, and runs on a custom webserver all written using Plywood. Integrating third-party libraries can a pain in C++, but Plywood aims to simplify it. Here's a short Plywood program that uses Cairo and Libavcodec to render a vector animation to a video file: And here's one that synthesizes a short music clip to an MP3: The source code for these examples is included in the Plywood repository, and everything builds and runs on Windows, Linux and macOS. Of course, Plywood also serves as the foundation for my (proprietary) game engine, which I call the Arc80 Engine. That's why Plywood came into existence in the first place. I haven't shipped a complete game using the Arc80 Engine yet, but I have made a number of prototypes with it. More on that later! What's Included In Plywood Plywood comes with: A workspace designed to help you reuse code between applications. A set of built-in modules providing cross-platform I/O, containers, process creation and more. A runtime reflection and serialization system. Here are a few more details about each component. The Workspace Most open source C++ projects are libraries that are meant to be integrated into other applications. Plywood is the opposite of that: It gives you a workspace into which source code and libraries can be integrated. A single Plywood workspace can contain several applications - a webserver, a game engine, a command-line tool. Plywood simplifies the task of building and sharing code between them. Plywood uses CMake under the hood, but you don't have t ## ReactOS Build Environment 2.2 released DevFeed: [ReactOS Build Environment 2.2 released]() Original publisher: [Read original article]() Published: 2020-05-01T00:00:00Z Content type: release Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [build tools](), [gcc](), [toolchain](), [Parser](), [C](), [C++](), [CMake](), [Visual Studio](), [Linux](), [macOS](), [Windows]() Tags: [binutils](), [build](), [c](), [c-plus-plus](), [cmake](), [compiler](), [free](), [gcc](), [linux](), [macos](), [open-source](), [os](), [react](), [reactos](), [toolchain](), [visual-studio](), [win32](), [winapi]() ### AI overview ReactOS Build Environment 2.2 upgrades the project's compiler and build tools, replacing GCC 4.7.2 with GCC 8.4.0. The release improves diagnostics, adds support for newer C and C++ standards, includes Bison and Flex, and updates the remaining toolchain. ### Source excerpt The ReactOS Build Environment (RosBE), our curated set of compilers and build tools, has just received a major upgrade. After more than 7 years of using the same and now ancient GCC 4.7.2, ReactOS is finally going to be built with the help of a modern compiler (GCC 8.4.0). Among other things, the new version better detects programming mistakes like improperly sized buffers, and comes with improved error messages to pinpoint such mistakes to the corresponding position in code. ## Eclipse Plugin for ESP-IDF DevFeed: [Eclipse Plugin for ESP-IDF]() Original publisher: [Read original article]() Author: John Lee Published: 2020-04-17T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [ESP32](), [Internet of things](), [Tooling](), [CMake](), [debugging](), [SDK](), [configuration]() Tags: [blog](), [cmake](), [configuration](), [debugging](), [eclipse](), [esp-idf](), [esp32](), [gnu-linux](), [iot](), [macos](), [plugins](), [tooling](), [windows]() ### AI overview The ESP-IDF Eclipse Plugin provides an Eclipse-based development environment for ESP32 IoT applications. It supports project setup, SDK configuration, CMake editing, building, flashing, serial monitoring, and debugging on Windows, macOS, and GNU/Linux. ### Source excerpt ESP-IDF Eclipse Plugin brings developers an easy-to-use Eclipse-based development environment for developing ESP32 based IoT applications. It provides better tooling capabilities, which simplifies and enhances standard Eclipse CDT for developing and debugging ESP32 IoT applications. It offers advanced editing, compiling, flashing and debugging features with the addition of Installing the tools, SDK configuration and CMake editors. The plug-in runs on Windows, macOS and GNU/Linux. ## Weaponizing your favorite Go program for Cobalt Strike DevFeed: [Weaponizing your favorite Go program for Cobalt Strike]() Original publisher: [Read original article]() Author: CCob Published: 2020-01-26T17:40:54Z Content type: tutorial Language: en Sources: [Ethical Chaos]() Topics: [Go Language](), [CMake](), [gcc](), [Compiler](), [GitHub]() Tags: [bypass](), [cmake](), [cobalt-strike](), [compiler](), [edr](), [gcc](), [github](), [go](), [golang](), [reflective-dll](), [weaponize](), [weaponizing]() ### AI overview This tutorial explains how to adapt a Go program into a reflective DLL for in-memory execution within Cobalt Strike. It presents a GitHub template based on gobuster and describes its use of CMake, GCC, the Go compiler, and CGO. ### Source excerpt How to convert a Go program to a reflective DLL for Cobalt Strike The post Weaponizing your favorite Go program for Cobalt Strike appeared first on Ethical Chaos. ## April 2018 meeting minutes DevFeed: [April 2018 meeting minutes]() Original publisher: [Read original article]() Published: 2018-05-01T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [WINE](), [Drupal](), [Jekyll](), [Git](), [CMake](), [Python]() Tags: [also](), [cmake](), [cms](), [free](), [git](), [jekyll](), [open-source](), [os](), [python](), [react](), [reactos](), [win32](), [winapi](), [wine]() ### AI overview ReactOS team members report on development work from the April 2018 meeting, including ReactOS 0.4.8, a proposed Git- and Jekyll-based website system, shell and API changes, bug fixes, USB patches, CMake updates, and other ongoing projects. ### Source excerpt 2018-04-26 19:00 UTC #meeting Proceedings Meeting started at 19:01 by Colin Finck Point 1: Status Reports Point 1: Status Reports Aleksandar Andrejevic had nothing to report, except that he now has some free time. He is currently looking at where he left off. Amine Khaldi is doing what he usually does, addressing anything he can help with, working on the Wine staging syncs etc. Colin Finck helped getting 0.4.8 out of the door and submitted his master's thesis 2 weeks ago. ## Animated line drawings with OpenCV DevFeed: [Animated line drawings with OpenCV]() Original publisher: [Read original article]() Author: Oona Räisänen (noreply@blogger.com) Published: 2017-12-30T12:15:00Z Content type: tutorial Language: en Sources: [Oona Räisänen]() Topics: [OpenCV](), [C++](), [Computer vision](), [CMake](), [Command-line interface]() Tags: [art](), [c-plus-plus](), [canvas](), [cmake](), [compiler-flags](), [computer-vision](), [gaussian](), [graphics](), [gui](), [make](), [music](), [plotting](), [programming](), [rgb](), [rotation](), [subpixel](), [terminal](), [vector](), [video]() ### AI overview This tutorial shows how to use OpenCV and C++ to create pixel-level animated graphics and save them as video. It covers project setup with CMake, drawing rotating concentric rings on an RGB canvas, subpixel antialiasing, and a Gaussian blur glow effect. ### Source excerpt OpenCV is a pretty versatile C++ computer vision library. Because I use it every day it has also become my go-to tool for creating simple animations at pixel level, for fun, and saving them as video files. This is not one of its core functions but happens to be possible using its GUI drawing tools. Below we'll take a look at some video art I wrote for a music project. It goes a bit further than just line drawings but the rest is pretty much just flavouring. As you'll see, creating images in OpenCV has a lot in common with how you would work with layers and filters in an image editor like GIMP or Photoshop. Setting it up It doesn't take a lot of boilerplate to initialize an OpenCV project. Here's my minimal CMakeLists.txt: cmake_minimum_required (VERSION 2.8) project (marmalade) find_package (OpenCV REQUIRED) add_executable (marmalade marmalade.cc) target_link_libraries (marmalade ${OpenCV_LIBS}) I also like to set compiler flags to enforce the C++11 standard, but this is not necessary. In the main .cc file I have: #include "opencv2/imgproc/imgproc.hpp" #include "opencv2/highgui/highgui.hpp" Now you can build the project by just typing cmake . && make in the terminal. Basic shapes First, we'll need an empty canvas. It will be a matrix (cv::Mat) with three unsigned char channels for RGB at Full HD resolution: const cv::Size video_size(1920, 1080); cv::Mat mat_frame = cv::Mat::zeros(video_size, CV_8UC3); This will also initialize everything to zero, i.e. black. Now we can draw our graphics! I had an initial idea of an endless cascade of concentric rings each rotating at a different speed. There might be color and brightness variations as well but otherwise it would stay static the whole time. You can't see a circle's rotation around its center, so we'll add some features to them as well, maybe some kind of bars or spokes. A simplified render method for a ring would look like this: void Ring::RenderTo(cv::Mat& mat_output) const { cv::circle(mat_output, 8 * center_, 8 * [Next page]()