This is a plugin for QtCreator to support the Rust programming language.
This project was started by Olivier Renaud, his original project can be found in the bitbucket
This project is in its very early stage. It is not yet useful for anyone, for now I focused on setting things up correctly.
The primary goals for now are:
- Allow the user to open a Cargo.toml file as a QtCreator project file.
- Setup the compile/run targets to use the corresponding Cargo commands
- Interpret the output of rustc to extract errors/warnings and link them to the files in the editor
- Provide a project creation wizard, which will be a simple wrapper around Cargo new
- Tweak various default configurations so that it is easy to work with Rust code out of the box
There is a ton of awesome features I can think of adding in the far future... But if I want to stay realistic, I would say that these 5 basic features are already enough to occupy my somewhat limited free time for a very long period!
QtCreator itself is multi-platform. My current main development machine is a Windows 10 x64, Debian 8 x64 stable, and thus it's what I use for this project. There is of course nothing Windows-specific on this project, so this should work anywhere QtCreator can run. The project is based on QtCreator 3.5.0 (open source version).
Just thinking of integrating with jenkins.
This project consists of
qt-creator
, a git/Hg subrepository that points to the Git QtCreator repository, on the v3.5.0 tag.dev-doc
, some developers-oriented docs.plugin
, a QtCreator plugin project.plugin/generic-highlighter
, syntax highlighting files that are copiedto the QtCreator install.
I configured the plugin's QMake project file so that it knows where to find the
sources of QtCreator (../qt-creator
). Also, QtCreator plugins are by default
configured so that they install themselves in the QtCreator build directory.
- Insall basic requirements for building Qt applications. Tested only on Debian 8, but for other distros you can try:
Debian/Ubuntu (apt-get)
sudo apt-get install build-essential libgl1-mesa-dev
Fedora/RHEL/CentOS (yum)
sudo yum groupinstall "C Development Tools and Libraries"
sudo yum install mesa-libGL-devel
openSUSE (zypper)
sudo zypper install -t pattern devel_basis
-
Download and install QT Community. At this moment 5.5 version is needed
-
git clone --recursive git@github.com:BProg/Rusty-Creator.git
-
Go to Rusty-Creator subdirectory (QT recomends to create shadow builds)
mkdir qt-creator-build ; cd qt-creator-build
path/to/QTCommunity/{QT-version}/{Compiler-Version}/bin/qmake -r ../qt-creator
make
- Go to Rusty-Creator/plugin directory
path/to/QTCommunity/{QT-version}/{Compiler-Version}/bin/qmake
make
make highlights
- Open terminal and type
xcode-select --install
-
Download and install QT Community. At this moment 5.5 version is needed
-
git clone --recursive git@github.com:BProg/Rusty-Creator.git
-
Go to Rusty-Creator subdirectory (QT recomends to create shadow builds)
mkdir qt-creator-build ; cd qt-creator-build
path/to/QTCommunity/{QT-version}/clang_64/bin/qmake -r ../qt-creator
make
- Go to Rusty-Creator/plugin directory
path/to/QTCommunity/{QT-version}/clang_64/bin/qmake
make
make highlights
-
Run qt creator located at
qt-creator-build/bin/qtcreator
-
To check that the plugin loaded correctly, click on
Help/About plugins
, and see if theRust
plugin appears in the "Other Languages" section, and is checked. -
Congratulations! You can now hack some code and send me pull requests!
To avoid a lot of headaches, it is recommended to use the same compiler for all the software stack. So, Qt, QtCreator and the plugin should be compiled with any supported compiler, but it should be the same for all. The CI build uses MSVC 2013. I use MSVC 2015 on my development machine (it is free, and can be used for building open source projects).
This is an example of setup:
-
Download and install MSVC 2015
-
Download the sources of Qt 5.5.0
-
Compile Qt
CALL "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64
SET PATH=C:\path-to-qt-sources\gnuwin32\bin;%PATH%
.\configure -platform win32-msvc2015 -debug-and-release -opensource -c++11 -confirm-license
nmake
- Add the newly compiled Qt
bin
directory to your path
SET PATH=C:\path-to-qt-sources\bin;%PATH%
-
Clone this project
-
Go in the
qt-creator
subdirectory, and compile it
qmake
nmake
- Go in the
plugin
subdirectory, compile
qmake
nmake
nmake highlights
-
Run QtCreator, located at
qt-creator/bin/qtcreator.exe
-
To check that the plugin loaded correctly, click on
Help/About plugins
, and see if theRust
plugin appears in the "Other Languages" section, and is checked. -
Congratulations! You can now hack some code and send me pull requests!
RustyCreator contains exactly the same features as QtCreator opensource, plus the following enhancements:
-
Syntax highlight based on the Kate format:
- Rust (
*.rs
): it's a cheap way to provide syntax highlight for now - Markdown (
*.md
,*.mmd
,*.markdown
): often used for readme files - Toml (
*.toml
,Cargo.lock
,.cargo/config
): used by Cargo - Yaml (
*.yml
,*.yaml
): used for Travis CI and Appveyor CI configuration - Json (
*.json
): 'cause it's popular
Note that I just integrated existing Kate syntax highlight files, I didn't write any of them.
- Rust (
-
Cargo project files (
Cargo.toml
) are supported as QtCreator project files. This means that inFile/Open File of Project
, the user can choose aCargo.toml
file and the project will be imported into the projects list. -
In the Projects view, a Cargo-based project shows the content of the directory where
Cargo.toml
lives, and all its subdirectories. Also, any change on the filesystem is reflected automatically in this tree. -
Work in progress: auto-detection and manual creation of Rust compilers, in the 'Build&Run/Compilers' options tab
There is a technical overview of the project in overview.md.
- ✓✓ = complete support
- ✓ = partial support
- ⋯ = work in progress
- (empty) = not started
State | Feature |
---|---|
✓✓ | Interpret Cargo.toml files as QtCreator project file |
✓✓ | Synchronize the project tree with the filesystem content |
✓✓ | Add generic syntax highlight support |
✓✓ | Integrate with a Windows CI service (Appveyor) |
✓ | Add rustc in the list of compilers |
Integrate with a MacOS CI service | |
Integrate with a Linux CI service | |
✓ | Autodetect rustc compilers on the system |
Add Cargo as a new build tool | |
Autodetect cargo tools on the system |
|
Add Cargo-specific build step | |
Add Cargo-specific run step | |
Add Cargo-specific deploy step | |
Auto-generate targets for example bins | |
Integrate unit tests and benches | |
Add either an autodetected kit or a default one | |
Add common code snippets | |
Support for cross compilation | |
Real syntax highlight | |
Basic text manipulation: auto-close parens, split strings... | |
Proper code indentation, based on Rust conventions | |
Customize default code style to match Rust conventions | |
Decorate project/files with the Rust icon! | |
Provide a more Rusty theme for the UI! | |
Debugger support | |
Code navigation | |
Code completion | |
find symbols using the Locator | |
Parse compiler output | |
Integrate lints/Clippy, possibly using a QuickFix suggestion | |
Handle Cargo sub-projects | |
Display/open crate dependencies | |
UI or autocompletion to work with the Cargo.toml file | |
Inline documentation | |
Various wizards |