AWS CodeBuild vs qmake

AWS CodeBuild is a paid, cloud-hosted continuous integration service for compiling, testing, and packaging code from build scripts. It provisions and scales build capacity automatically, so projects do not require users to manage build servers. Preconfigured environments cover Java, Python, Node.js, Ruby, Go, Android, .NET Core for Linux, and Docker; teams can also supply Docker-based environments. A YAML build specification defines commands for each build phase and other settings. Builds can start from CodeCommit, GitHub, GitHub Enterprise, Bitbucket, Amazon S3, or CodePipeline, and can work with Jenkins. Artifacts can be stored in S3 or sent to an artifact repository. IAM provides access controls, while KMS keys encrypt artifacts. Build timing, status, commit ID, metrics, and logs are available through the service and CloudWatch, with SNS event notifications. A free plan provides stated monthly allowances; paid usage starts at 0.01 USD and can add charges for data transfer and related AWS services.

qmake manages builds for applications, libraries and other components by turning project files into Makefiles. Its `.pro` files can define source files, configuration, libraries and include paths. It supplies build rules for Qt's moc and uic tools, with templates for applications, libraries and plugins. Projects can specify third-party libraries, and qmake can use pkg-config for supported libraries such as D-Bus and ogg. It can generate Microsoft Visual Studio project files and, on macOS, Xcode project files. Platform notes cover iOS universal binaries, frameworks and bundles. In Qt 6, qmake remains supported for building Qt applications, but cannot compile custom Qt plugins or libraries that rely on Qt 5 build-system internals. Qt warns that building an untrusted project can execute code on the build machine. The Qt Community Edition is free under LGPL or GPL terms, with source-code obligations and limited access to some Qt capabilities.