configure, make install, AppStream, Flatpak, ioctl

[Danysan1]

To install all files into $exampleDir run:
./configure --prefix=$exampleDir
make
make install

[Danysan1]

For some reason 'make install' still does not install translation files. I am trying to understand why.

[Danysan1]

Summing up the changes of this pull:

• radeon-profile/radeon-profile.pro
  Implemented the automated installation through the Makefile install target. After running qmake and make, running make install will automatically install all the files (see below for the exact directories).
• radeon-profile/configure
  This script automatically collects CXXFLAGS, installation prefix and other info and calls qmake (whether it is from Qt5 or Qt4).

In combination with the first point, this completes the standard linux 3-step build process; running inside the radeon-profile directory the command sequence:

./configure --prefix=...
make
make install DESTDIR=...  INSTALL_ROOT=...

will install these files:

$INSTALL_ROOT/$DESTDIR/$PREFIX/bin/radeon-profile
$INSTALL_ROOT/$DESTDIR/$PREFIX/share/icons/hicolor/512x512/apps/radeon-profile.png
$INSTALL_ROOT/$DESTDIR/$PREFIX/share/applications/radeon-profile.desktop
$INSTALL_ROOT/$DESTDIR/$PREFIX/share/appdata/radeon-profile.appdata.xml
$INSTALL_ROOT/$DESTDIR/$PREFIX/share/radeon-profile/strings.*.qm

This allows to simplify the packaging scripts, automating the install process (for example, old PKGBUILD->new PKGBUILD, old debian.rules->new debian.rules, old .spec->new .spec).
I moved the icon from /share/pixmaps/ to /share/icons/hicolor/512x512/apps/ because that's the path structure where the Freedesktop standard suggests to put the icons.

• radeon-profile/extra/radeon-profile.appdata.xml
  This file contains meta-data info for the Appstream standard, used by app stores like Gnome Software.

• radeon-profile/extra/radeon-profile.desktop
  Minor improvements.

• flatpak-builder.json
  Manifest file for flatpak-builder, which automatically builds (configure,make,make install) a Flatpak package (an architecture independent portable application package). Running inside the main directory this command:
  flatpak-builder --repo=repo temp flatpak-builder.json
  will create a repository into repo/, build radeon-profile into temp/ and package it into the repository (the KDE Sdk (org.kde.Sdk) is necessary to build it, for Qt). To install it (the KDE Runtime (org.kde.Platform) is necessary, for Qt):
  flatpak --user remote-add --no-gpg-verify rp repo && flatpak --user install rp org.rp.RadeonProfile
  To run it:
  flatpak run org.rp.RadeonProfile

• radeon-profile/globalStuff.h radeon-profile/dxorg.cpp radeon-profile/uiEvents.cpp
  Fix PROFILE radeon power method, which was not detected with the daemon (diff), used the wrong path (diff) and did not work correctly with combo_pProfile on HIGH and LOW profiles (diff). Also, small cleanups (diff, diff, diff).

• radeon-profile/gpu.cpp
  Fix FGLRX initialization, which did not check the list of GPUs (diff).

• radeon-profile/main.cpp
  Added a splash screen that indicates the app loading while radeon-profile loads and waits for radeon-profile-daemon, which can take a long time.

• radeon-profile/radeon_profile.cpp radeon-profile/radeon_profile.h
  Fix Qt4 build.

• radeon-profile/translations/strings.it.ts
  Update Italian translation.

[marazmista]

Instead of changing title and push into one pull request as much changes as you can, please do small pull request for each feature when you consider it complete and tested because, when you make a pull request and then still keep committing changes after which code looks nothing like it was when pull request was opened, it is impossible to review.

[Danysan1]

Ok, I have solved merge conflicts and split this pull in four parts:

1. IOCTLs: Diff, Branch, Pull request
2. Configure, make install, flatpak: Diff, Branch
3. Fixes to PROFILE power method: Diff, Branch
4. Fixes for FGLRX driver, improved first data read, splash screen: Diff, Branch

(If you want to merge the separate branches, merge them in this order)
EDIT: I have updated the branches, you can merge them independently in any order

[Danysan1]

Leaving the four separate branches to merge, closing.