Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow toggling CRe's new dithering & scaling #888

Merged
merged 114 commits into from
Apr 18, 2019
Merged

Allow toggling CRe's new dithering & scaling #888

merged 114 commits into from
Apr 18, 2019

Commits on Apr 17, 2019

  1. Build the new scaler code

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    4b9f088 View commit details
    Browse the repository at this point in the history

  2. Allow toggling smooth scaling

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    4f9861d View commit details
    Browse the repository at this point in the history

  3. Now with the right function name ;D

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    32425f3 View commit details
    Browse the repository at this point in the history

  4. Lay the groundwork to make SW/HW dithering easily toggleable

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    1bacd69 View commit details
    Browse the repository at this point in the history

  5. Allow toggling SW dithering in CRe

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    d69ced1 View commit details
    Browse the repository at this point in the history

  6. Don't even try to enable SW dithering when !8bpp, as nothing will honor 

    it anyway
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    9e87b55 View commit details
    Browse the repository at this point in the history

  7. Initial naive port of the dithering algo to the Lua BB

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    7aa3810 View commit details
    Browse the repository at this point in the history

  8. Simplify that

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    345b073 View commit details
    Browse the repository at this point in the history

  9. And port dithering to the C BB

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    9cd67b9 View commit details
    Browse the repository at this point in the history

  10. And now it actually builds ;p

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    e41ca23 View commit details
    Browse the repository at this point in the history

  11. Ups.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    3e9cc31 View commit details
    Browse the repository at this point in the history

  12. Nice typo.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    c265656 View commit details
    Browse the repository at this point in the history

  13. Make sure we pass a Color8 to the dither algo in the Lua BB

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    9def095 View commit details
    Browse the repository at this point in the history

  14. Declare dither_o8x8 earlier for ditherpmulblend

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    41135d6 View commit details
    Browse the repository at this point in the history

  15. Jot that down for one rainy day of experimentation...

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    babdd9f View commit details
    Browse the repository at this point in the history

  16. Bump CRe to pickup the required dithering/scaling changes 

    Let's see PB's GCC choke on C11/C++11...
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    a4cbade View commit details
    Browse the repository at this point in the history

  17. Heh. That's what happens when DIV255 gets more accurate ;).

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    ed5e6d9 View commit details
    Browse the repository at this point in the history

  18. Enforce C11/C++11 w/ GNU extensions on older compilers. 

    Here's hoping that'll do the trick even on PB...
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    c394ecf View commit details
    Browse the repository at this point in the history

  19. And explain why GCC 6 

    (IIRC, GCC 6.0 never came out, so, eh).
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    ffb8c5c View commit details
    Browse the repository at this point in the history

  20. More comments :)

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    59f4e17 View commit details
    Browse the repository at this point in the history

  21. Bypass ccache when version checking (maybe?)

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    dc86eff View commit details
    Browse the repository at this point in the history

  22. Vague attempt at getting CMake to actually use the right flags 

    It's calling CXX w/ CFLAGS, which is braindead on all kinds of levels.
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    45f8cbf View commit details
    Browse the repository at this point in the history

  23. Oh, CMake, how I love how you pull bogus CFLAGS out of nowhere.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    9bb7c33 View commit details
    Browse the repository at this point in the history

  24. Nope, CMake is still the worst.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    0433298 View commit details
    Browse the repository at this point in the history

  25. Slightly smaller hammer should be enough.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    c33d180 View commit details
    Browse the repository at this point in the history

  26. -_-"

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    6461bca View commit details
    Browse the repository at this point in the history

  27. Right, not CMake ;D. 

    CRe is C++, use CXX & CXXFLAGS, even for the DYNLIB calls.
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    63dfb22 View commit details
    Browse the repository at this point in the history

  28. Oh, fun, fun fun, expect all kind of weird shit to break now that CMake 

    actually picks up CFLAGS & friends.
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    2b2cf75 View commit details
    Browse the repository at this point in the history

  29. Drop that, too, we haven't seen such an old Clang version in basically 

    forever.
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    622b8b2 View commit details
    Browse the repository at this point in the history

  30. Hopefully that should do the trick... 

    Otherwise, it's time for hilariously undocumented hacks.
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    dab3442 View commit details
    Browse the repository at this point in the history

  31. One last try of being nice...

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    6c80329 View commit details
    Browse the repository at this point in the history

  32. Why CMake is testing the CXX compiler in a project where CXX isn't 

    requested is one of life's great mysteries.
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    b811c6c View commit details
    Browse the repository at this point in the history

  33. Gross hacks it is, then.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    ecfecca View commit details
    Browse the repository at this point in the history

  34. Okay, let's try to break everything, because CMake is being stupid.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    f8a5069 View commit details
    Browse the repository at this point in the history

  35. SHould be slightly more adapated to our build system, now...

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    7e7a9c5 View commit details
    Browse the repository at this point in the history

  36. Missed that bit of insanity... 

    Possibly useful w/ Android & PB TCs...
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    4f55d53 View commit details
    Browse the repository at this point in the history

  37. This is going to be fun...

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    e3d9272 View commit details
    Browse the repository at this point in the history

  38. I doubt this will help...

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    8296ae5 View commit details
    Browse the repository at this point in the history

  39. Well, what do you know.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    2cbac1a View commit details
    Browse the repository at this point in the history

  40. Eh.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    da9cd4e View commit details
    Browse the repository at this point in the history

  41. Nasty stray double quote

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    a705736 View commit details
    Browse the repository at this point in the history

  42. Huh.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    566080b View commit details
    Browse the repository at this point in the history

  43. Let there be logs!

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    0df4c8b View commit details
    Browse the repository at this point in the history

  44. -_-".

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    414175a View commit details
    Browse the repository at this point in the history

  45. That should be much less annoying that simply daisy-chaining those 

    around.
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    5112505 View commit details
    Browse the repository at this point in the history

  46. Duh.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    b0ebfe6 View commit details
    Browse the repository at this point in the history

  47. I smell stupid string handling on the horizon

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    df3ec6a View commit details
    Browse the repository at this point in the history

  48. With a bit of luck, the ExternalProject doc will turn out to actually 

    have been useful, for once.
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    fc89125 View commit details
    Browse the repository at this point in the history

  49. Because of course this makes much mùore sense.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    8d5d9a5 View commit details
    Browse the repository at this point in the history

  50. jpeg-turbo daisy-chaining doesn't work with Ninja, for some reason.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    a1676ce View commit details
    Browse the repository at this point in the history

  51. Hopefully fix jpeg-utrbo when x-compiling without having to duplicate 

    the insane arch logic...
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    7753e7c View commit details
    Browse the repository at this point in the history

  52. windres is windows only, and that confuses libtool, apparently.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    7ff8fa0 View commit details
    Browse the repository at this point in the history

  53. --verbose is apparently not a thing (yet)

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    db1eacb View commit details
    Browse the repository at this point in the history

  54. Don't need that anymore

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    bd3725b View commit details
    Browse the repository at this point in the history

  55. I would really like to see those gcc invocations, now...

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    5949557 View commit details
    Browse the repository at this point in the history

  56. Okay, let's see if that expands in a non-stupid manner...

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    b68a6df View commit details
    Browse the repository at this point in the history

  57. Okay, let's try to figure out why CMake is trying to call "" instead of 

    AR...
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    a4e5389 View commit details
    Browse the repository at this point in the history

  58. Might actually get verbose output this way...

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    79ad925 View commit details
    Browse the repository at this point in the history

  59. Let's assume ccache is fucking with me.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    0b192d4 View commit details
    Browse the repository at this point in the history

  60. Don't use CHOST when it isn't set 

    Fix MACHINE & OUTPUT_DIR on native builds
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    2266158 View commit details
    Browse the repository at this point in the history

  61. Clear LDFLAGS for the minilua build, because Android has some pretty 

    nasty target-specific flags in there.
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    71fa7ad View commit details
    Browse the repository at this point in the history

  62. Don't enforce std anywhere else, now that it's handled in Makefile.defs

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    0b08010 View commit details
    Browse the repository at this point in the history

  63. I'm getting a drink.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    33b30be View commit details
    Browse the repository at this point in the history

  64. Prefer command -v to which, and prefer LTO-friendly wrappers to base 

    ar/ranlib/nm (because they're currently not built properly to be
plugin-aware automagically).
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    dc2b4aa View commit details
    Browse the repository at this point in the history

  65. Hide verbosity behind a VERBOSE define

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    8ee00da View commit details
    Browse the repository at this point in the history

  66. Lowercase

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    87abe91 View commit details
    Browse the repository at this point in the history

  67. This generates a shitton of stupid warnings, and doesn't help Travis.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    4edbd2b View commit details
    Browse the repository at this point in the history

  68. Stupid workaround it is, then.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    edd2374 View commit details
    Browse the repository at this point in the history

  69. Hopefully take care of LuaJIT + LDFLAGS for good...

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    1ce9e13 View commit details
    Browse the repository at this point in the history

  70. Even stupider hammer?

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    809370d View commit details
    Browse the repository at this point in the history

  71. Ye olde printf debugging

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    8b608be View commit details
    Browse the repository at this point in the history

  72. Of course we can't have nice things.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    d39b8e3 View commit details
    Browse the repository at this point in the history

  73. Well, that didn't work. 

    Let's see if ditching Ninja magically fixes it like jpeg-turbo...
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    85b0ee4 View commit details
    Browse the repository at this point in the history

  74. DUh.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    9e6a76e View commit details
    Browse the repository at this point in the history

  75. Okay, so, at least it's consistent ;p

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    d9c62cc View commit details
    Browse the repository at this point in the history

  76. Okay, apparetly, those are cache values...

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    4746597 View commit details
    Browse the repository at this point in the history

  77. Fix distclean (the spaces added by += were neutering it)

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    ed923ac View commit details
    Browse the repository at this point in the history

  78. Let's try bumping OpenSSL, and doing a slow descent into madness re: 

    RPATH+ORIGIN...
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    ee4eb30 View commit details
    Browse the repository at this point in the history

  79. Update to LuaSec 0.8

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    f430ac6 View commit details
    Browse the repository at this point in the history

  80. Ups.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    12e0bf8 View commit details
    Browse the repository at this point in the history

  81. Hmm?

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    b68811c View commit details
    Browse the repository at this point in the history

  82. Ups, misrerad that.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    eadbcfb View commit details
    Browse the repository at this point in the history

  83. Take two...

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    6dfeb0d View commit details
    Browse the repository at this point in the history

  84. Ups.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    f3efdb9 View commit details
    Browse the repository at this point in the history

  85. Oh, that one was sneaky.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    888d74e View commit details
    Browse the repository at this point in the history

  86. Possibly less broken on Android

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    fb30e06 View commit details
    Browse the repository at this point in the history

  87. Update sover

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    482b5f9 View commit details
    Browse the repository at this point in the history

  88. RPATH, take two.

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    8ad92e3 View commit details
    Browse the repository at this point in the history

  89. Okay, ORIGIN is a go 

    (phew.)
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    529fa6a View commit details
    Browse the repository at this point in the history

  90. Bump CRe for Android fix

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    533c1f7 View commit details
    Browse the repository at this point in the history

  91. That's why REALCC was used ;)

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    e5c6908 View commit details
    Browse the repository at this point in the history

  92. Amend that comment

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    f1e22e1 View commit details
    Browse the repository at this point in the history

  93. Prevent x-compilation stupidity during MuPDF build

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    f1eb46f View commit details
    Browse the repository at this point in the history

  94. Let's see if that's enough to get a useful error out of Pb's shitty GCC 

    version

Otherwise, it's going to get hairy...
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    bd82c3a View commit details
    Browse the repository at this point in the history

  95. Huh, wait, it's actually PRSTUX. 

    Which is using GCC 4.9.3, so, err, that's unexpected, since it is mostly
C11 compliant.
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    488c9d3 View commit details
    Browse the repository at this point in the history

  96. Bump CRe for the complete Android fix ;p. 

    It's also missing *at runtime* on some devices, even @ API 16.
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    7322691 View commit details
    Browse the repository at this point in the history

  97. Ah, right, I'd forgotten how this worked. 

    Got to generate them on the host first, no matter what.
Which means drop LDFLAGS like Lua for this step ;).
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    27c15b4 View commit details
    Browse the repository at this point in the history

  98. Agh, I'm stupid. 

    The gen stage is host, don't flag it cross -_-".
It's the build stage that should be flagged cross.
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    9b29336 View commit details
    Browse the repository at this point in the history

  99. This should fix OpenSSL on GCC 4.9 (i.e., PRSTUX). 

    Make it PRSTUX only, as it's a GCC bug, specific to this release.
    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    23731f2 View commit details
    Browse the repository at this point in the history

  100. Strip more flags that OpenSSL chokes on for Android...

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    5cc2e4d View commit details
    Browse the repository at this point in the history

  101. Simple replace is enough ;).

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    24f2c9c View commit details
    Browse the repository at this point in the history

  102. Hopefully fixes Android build...

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    c96158f View commit details
    Browse the repository at this point in the history

  103. Err, set API level on both Android variants -_-".

    @NiLuJe
    NiLuJe committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    a328007 View commit details
    Browse the repository at this point in the history

Commits on Apr 18, 2019

  1. Well, the soft approach didn't work, I see...

    @NiLuJe
    NiLuJe committed Apr 18, 2019
    Configuration menu
    Copy the full SHA
    62ee45c View commit details
    Browse the repository at this point in the history

  2. Ups, we install a standalone toolchain...

    @NiLuJe
    NiLuJe committed Apr 18, 2019
    Configuration menu
    Copy the full SHA
    e7749e4 View commit details
    Browse the repository at this point in the history

  3. Keep those around, just in case...

    @NiLuJe
    NiLuJe committed Apr 18, 2019
    Configuration menu
    Copy the full SHA
    db57c8f View commit details
    Browse the repository at this point in the history

  4. Third time's the charm?

    @NiLuJe
    NiLuJe committed Apr 18, 2019
    Configuration menu
    Copy the full SHA
    21da5b8 View commit details
    Browse the repository at this point in the history

  5. Okay, don't override CC on Android

    @NiLuJe
    NiLuJe committed Apr 18, 2019
    Configuration menu
    Copy the full SHA
    aa775de View commit details
    Browse the repository at this point in the history

  6. Or do, because ccache is awful.

    @NiLuJe
    NiLuJe committed Apr 18, 2019
    Configuration menu
    Copy the full SHA
    08b7b68 View commit details
    Browse the repository at this point in the history

  7. That was stupid ;)

    @NiLuJe
    NiLuJe committed Apr 18, 2019
    Configuration menu
    Copy the full SHA
    a88a5f4 View commit details
    Browse the repository at this point in the history

  8. I was expecting that one ;). 

    Anbdroid TCs are stuck on GCC 4.9 (Pre-GPL3).
    @NiLuJe
    NiLuJe committed Apr 18, 2019
    Configuration menu
    Copy the full SHA
    fe59473 View commit details
    Browse the repository at this point in the history

  9. *sigh*

    @NiLuJe
    NiLuJe committed Apr 18, 2019
    Configuration menu
    Copy the full SHA
    8a7cad4 View commit details
    Browse the repository at this point in the history

  10. The tests don't build on Android, and we don't care anyway. 

    test/rsa_complex.c:17:23: fatal error: complex.h: No such file or directory
    @NiLuJe
    NiLuJe committed Apr 18, 2019
    Configuration menu
    Copy the full SHA
    accf876 View commit details
    Browse the repository at this point in the history

  11. Fix PHONY targets 

    [skip-ci]
    @NiLuJe
    NiLuJe committed Apr 18, 2019
    Configuration menu
    Copy the full SHA
    22dac0a View commit details
    Browse the repository at this point in the history