Add CI

[katyo]

Solution for #73

Implemented tasks:

• Check code formatting rules
• Check code quality using clippy
• Generate bindings for supported platforms (stable Rust)
• Check building on all supported platforms (stable Rust)
• Check building on different Rust channels (stable/beta/nightly, Linux x86_64)
• Run tests on native Linux platforms (x86_64 and i686)
• Create pull-requests for updating generated bindings
• Publish crates when pushing version tag (It requires explicitly setting versions in manifests of crates)

All tasks runs on ubuntu 20.04.
System version of DRM headers is used, so bindings may lack some bleeding edge APIs.
To get publishing working you need set CRATES_TOKEN secret.

Currently supported platforms for bindgen:

• Linux x86
• Linux x86_64
• Linux arm
• Linux aarch64

Needed for gbm.rs#4

[katyo]

@Drakulix,
I would like to assign concrete version numbers to dependencies for some reasons.
I done it on another CI branch to get working check with -Z minimal-versions.

[Drakulix]

@Drakulix,
I would like to assign concrete version numbers to dependencies for some reasons.
I done it on another CI branch to get working check with -Z minimal-versions.

I have filled #77

[katyo]

@Drakulix I have rebased this PR.
Is any more which should be done before merging?

[Drakulix]

@Drakulix I have rebased this PR.
Is any more which should be done before merging?

I do not think so.

@Slabity anything you would like to add?

[Drakulix]

@katyo Could you rebase one more time?

@Slabity I would merge this, setup the auto-publish feature for this repo and then release 0.4. Any objections?

[Slabity]

@Slabity I would merge this, setup the auto-publish feature for this repo and then release 0.4. Any objections?

No objections at all. Having proper CI and auto-publishing is probably a good idea.

[katyo]

@Drakulix @Slabity Hope it's ready to merge.

Don't forget to add CRATES_TOKEN secret before publising on crates.io via tags.

[Drakulix]

Looks good!
Two last questions, through...

@Slabity can you setup the CRATES_TOKEN secret?
Alternatively I can do it, if you give me push access to drm-sys as well, otherwise the upload will fail.

[Drakulix]

Can this step deal with the three different packages of the repository?
Or do we need multiple steps here?

The order is important as well, since the crates depend on each other.
We need to push drm-sys first, then drm-ffi and at last drm.

[katyo]

This step uses publish-crates action which supports publishing workspace members with dependencies.
It works for my projects just a fine. I hope it will also works here.

[MarijnS95]

@katyo You might want to expand this with --all-targets so that the examples are linted, too.

In other news something odd is going on with the clippy on nightly. The current 1.51 stable gives off extra upper_case_acronyms warnings in src/lib.rs, and tons of redundant_field_names warnings, but nightly doesn't. Is this a temporary fluke or do we need extra configuration? Have you seen this on other projects?

[MarijnS95]

Ah, these crates are not in a workspace :)