sigmoid

..oo..oo..oo..oo..oo..oo..

I finally uploaded my builts of Qt v5.6.1 (snapshot) and Qt v5.7.0 Release Candidate, you can check them out at the Precompiled Qt4 and Qt5 page.

I was able to build Qt v5.7.0 RC with MSVC 2013 and 2015, older compilers seem to have issues. As for Qt v5.6.1 it was not possible to build with MSVC 2008. Since the compiler has been dropped upstream and I don’t use it either, the choice to drop it was easy.

I will most likely build another set of v5.6.x and v5.7.x once newer versions as out. Qt v5.7.x will most likely be release within June and maybe v5.6.x will also get to v5.6.2.

The builds are untested, so if you have issues leave me a comment, I can probably help.

Note also that I have moved older Qt builds to a separate Qt4 and Qt5 (Past Builds) page.

0

Just finished compiling Boost 1.61 for all popular MSVC compilers, MSVC 2008 through 2015. Since 1.60, I made a patch to enable Boost.Locale and Boost.Regex to link against static ICU, which is not supported upstream. You can download scripts, patches, etc. at the Precompiled Boost page, as always.

For older releases head to the Precompiled Boost (Past Builds) page.

All precompiled binaries are unsupported, untested and are only here for my own use, however chances are some of you may find them useful. Let me know if you have any issues and I will try to help.

enjoy!

0

Compiled OpenSSL v1.0.1t and v1.0.2h for MSVC 2008-2015 are now available in the Precompiled OpenSSL page. Build scripts and patches available for anyone who wants to customize their builds.

Note that old versions of OpenSSL are now in the Precompiled OpenSSL (Past Builds) page, however it is only there for archival purposes, do not use for any production systems. Actually, if you are doing any serious work, you ought to build your own OpenSSL anyway.

0

I just finished compiling the MariaDB v5.5.48 libraries. I have also managed to reorganize the prebuild pages a bit, so that past builds are now on their own page, while the latest builds will remain always in the Precompiled MariaDB page.

So we’re almost there with the preparations of the Qt 5.6 build!

0

Definitely follow these instructions on configuring udev on your system: https://wiki.cyanogenmod.org/w/UDEV

On a Gentoo system also ensure you have emerged: dev-util/android-tools

Even if you do all the steps and still do not get an Authorisation Request when plugging your phone over USB and your adb devices is empty, then you probably have to do the following in addition to everything mentioned already:

Plug your phone over USB and get a list of the attached USB devices by executing as root:

# lsusb
Bus 001 Device 055: ID 0e8d:201d MediaTek Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
...
..

The 4-character string highlighted with red is the vendor id of the mobile device. Of course if you have a different phone this will vary.
Now edit, or create if it doesn’t exist the file ~/.android/adb_usb.ini and place on a single line the prefix 0x followed by your vendor id:

# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x0e8d

Then restart the adbd:

adb kill-server
adb start-server;
adb devices

If all other steps were done correctly, you should see on your phone an Authorisation Request. Go ahead and accept to be able to access your phone from your linux host.

4+