Cisco MSI and Qt
summary
Cisco MSI uses QtCore and QtNetwork as the only Qt modules to reach Linux and Windows endpoints across x86, amd64, PowerPC, ARM and MIPS, with unit tests run on every commit. A 20k‑line C++ codebase ports to Qt in three weeks plus three weeks stabilizing; total code grows to ~115k C++ and 21k C by Sept 2011. Implementations include a network interface notifier (cross‑platform signals for interface up/down/address) and a raw Ethernet socket (works on BSD/Linux, requires a Windows driver); memory tracked per commit.
AI-written summary · about
chapters (15)
- 0:00Introduction and welcome
- 1:07What is Medianet
- 2:09MSI architecture overview
- 3:56Endpoints using MSI
- 4:38Switching to Qt in 2010
- 7:26Why Qt over CrossOS
- 9:12Fighting misconceptions about Qt
- 10:57Learning Qt internals
- 12:00Memory footprint analysis
- 13:03Qt modules used in MSI
- 14:06Qt extensions introduction
- 14:27Interface events extension
- 18:16Raw socket extension
- 20:42Qt for embedded platforms
- 21:05Q&A session
related talks
54mEnabling IoT OSs for Intel Quark MCU platforms: The Fast Way
49mScaling Qt from Desktop to Servers and Micro-controllers
01h 30m“Qt as a C++ Framework: History, Present State and Future”
27mCoding Qt for greater interoperability and portability ...
33mQtinUse - Networked, GUI-Driven Automation
27mSet Yourself up for Success — Lessons Learned from Building 100+ Devices with C++/Qt/QML
49mWriting better code with help from Qt and the compiler
50mC++ at High Subsonic Speed