|
97205269
|
2016-11-23T18:44:33
|
|
Travis: Fix OS X build
+ migrate to new xcode7.3 image, since xcode7.2 is going away soon.
|
|
|
6abd3916
|
2016-11-15T08:47:43
|
|
Unified CMake-based build system
See #56 for discussion.
Fixes #21, Fixes #29, Fixes #37, Closes #56, Fixes #58, Closes #73
Obviates #82
See also:
https://sourceforge.net/p/libjpeg-turbo/feature-requests/5/
https://sourceforge.net/p/libjpeg-turbo/patches/5/
|
|
|
a949da48
|
2016-10-20T19:17:30
|
|
Merge branch 'master' into dev
|
|
|
2d4b2f14
|
2016-10-20T17:55:55
|
|
Travis: Deploy to S3 rather than SourceForge
This has the following advantages:
-- It doesn't require checking a private SSH key into the repository.
(With SourceForge, an SSH key is the "keys to the kingdom".)
-- If the S3 key is compromised, it is very easy to revoke it and
generate a new one.
-- The S3 bucket is isolated, so even if it becomes compromised, then
the damage that one could do is limited.
-- It's much easier to manage files through S3's web interface than
through SourceForge.
-- The files are served via HTTPS.
-- Travis fully supports S3 as a deployment target, so this simplifies
.travis.yml somewhat.
|
|
|
108b1cd9
|
2016-10-20T01:37:40
|
|
Merge branch 'master' into dev
|
|
|
9366cf0b
|
2016-10-20T01:01:27
|
|
Travis: GPG sign Linux binaries/source tarballs
Since we're still deploying our Linux/macOS CI artifacts to a web server
(specifically SourceForge Project Web Services) that doesn't support
HTTPS, it's a good idea to sign them. But since the private key has to
be checked into the repository, we use a different key for signing the
pre-releases (per project policy, the private signing keys for our
release binaries are never made available on any public server.)
|
|
|
1a8c68ac
|
2016-10-07T12:55:18
|
|
Merge branch 'master' into dev
|
|
|
1ee329d6
|
2016-10-07T12:54:55
|
|
Travis: Fix deployment issue (2nd attempt)
|
|
|
fa3bdfb7
|
2016-10-07T05:47:35
|
|
Merge branch 'master' into dev
|
|
|
b47c5e73
|
2016-10-07T05:34:11
|
|
Travis: Fix deployment issue
"Skipping a deployment with the script provider because this branch is
not permitted"
|
|
|
27f817cd
|
2016-10-07T05:07:11
|
|
Travis: Use existing sandbox for official builds
This eliminates the need to specify the remote repository and branch,
and it prevents the code from being checked out twice.
|
|
|
be908ac0
|
2016-10-05T14:42:35
|
|
Travis CI: Fixes to support AVX2 code
-- Use trusty for SIMD builds. Ubuntu 12.04 is still using NASM 2.09.x,
which isn't new enough to support AVX2.
-- Add a special test for the SSE2 code path, since it is no longer the
default.
|
|
|
6d22430a
|
2016-10-05T14:36:46
|
|
Travis: use correct repo/branch for off. builds
Pass the actual repository and branch that Travis is using into the
builtljt script, so the official builds it generates will come from
the same code base as the other tested builds.
|
|
|
e9e3a2ed
|
2016-10-05T12:38:59
|
|
Travis CI: Use correct key for this repository
|
|
211c69f3
|
2016-10-02T09:13:23
|
|
Add Travis CI config for Un*x pre-release builds
|