miasm
miasm copied to clipboard
cea-sec
macOS builds with travis
closes #438, closes #875, closes #912
still an issue with gcc tests on macos
https://travis-ci.org/cea-sec/miasm/jobs/478366262#L928
@commial this works, but the gcc test cases seem to be failing (see https://travis-ci.org/cea-sec/miasm/jobs/479469186#L925)
do those have to be working for osx? if not, could you make a MIASM_TEST_EXTRA_ARG variable for https://github.com/cea-sec/miasm/pull/930/files#diff-354f30a63fb0907d4ad57269548329e3R33 so that we could limit to osx job to non gcc cases and get everything passing?
Not sure to understand what you're asking.
If you want to try without gcc, you just have to remove:
-o qemu -t python,llvm
-o gcc -t qemu,long
And replace -o long by -o long -t gcc. -o is whitelisting, -t is blacklisting.
Regarding the necessity of gcc on MacOS X, I'm not sure. If we have at least one of the fast jitter (either CC based or LLVM), it should be OK. Thoughts @serpilliere ?
Note: maybe it could work with Clang or specific options. For instance, on Windows, it is actually using cl with others flags. Options can be customized in JitCore_Gcc.add_block
- Should be rebased I think
- Travis now supports Windows too, so you might extend with it too.
@XVilka : note that we already have windows regressions tests run on appveyor. Do you propose removing appveyor in favor of travis? Can you argu on this ?
