https://github.com/bbreslauer/qt-bazel-example

An example QT application built with Bazel
https://github.com/bbreslauer/qt-bazel-example

Last synced: 3 months ago
JSON representation

An example QT application built with Bazel

• Host: GitHub
• URL: https://github.com/bbreslauer/qt-bazel-example
• Owner: bbreslauer
• License: unlicense
• Created: 2016-04-10T06:38:49.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2020-04-04T23:20:45.000Z (over 4 years ago)
• Last Synced: 2024-07-17T15:00:10.124Z (4 months ago)
• Language: Starlark
• Homepage:
• Size: 8.79 KB
• Stars: 41
• Watchers: 3
• Forks: 11
• Open Issues: 5
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• awesome-bazel - QT application

README

        
# QT setup for Bazel

This repository contains a simple Qt5 Hello World application with that is

built with [http://bazel.io/](Bazel).

The Bazel setup has been tested on an Arch Linux system with Qt5 installed. It

should work on other OSes, possibly with changes to the WORKSPACE file and the

qt.bzl file that adjust the paths in them.

# History

I wanted to figure out how to build a Qt application with Bazel, but I could not find any examples online and it was very difficult to add into my existing application. So I created this simple example to figure out how to get a build working, and then figured that other people might want to build their Qt apps with Bazel, so I posted it so that others didn't have to spend as much time figuring this out. This example, though minimal, I think satisfies the use case of "how do I get Bazel to build a Qt app?".

This repository, out of the box, does not necessarily work on all platforms, or with all the different Qt libraries, but making those changes should be easy. However, I do not have time to ensure that this example works on all different combinations of platforms and libraries, so my suggestion is to copy the relevant files into your repository and modify them as needed. Pull requests are unlikely to be accepted, so on the plus side, it's unlikely that you would need to merge in changes from this repository at any point.