Version 8, last updated by dascandy at May 14, 2010 03:01 UTC
SupportedCompilerOrProcessorCombinations
Legend:
+: Works in every sense
~: Works, basically
$: Costs money to test, but compiles
-: Doesn't work
x: Not applicable
?: Unknown, untested - please test if you have this combination
!: Crashes compiler
| GCC (regular) | GCC (C++0x) | Comeau | MSVC | IAR EWB | |
|---|---|---|---|---|---|
| x86-32 (Linux) | + | + | x | x | x |
| x86-32 (Windows XP) | + | + | $ | + | ? |
| x86-32 (MacOS X) | + | ? | x | x | x |
| ARM7 | ? | x | x | ? | ! |
| ARM9 | + | ? | x | + | x |
| uBlaze | + | ? | x | x | x |
| Nios2 | + | ? | x | x | x |
| SH3 | + | ? | x | x | x |
Sean DeNigris has a short overview on how he got HippoMocks working on his Mac. The general procedure is identical for any other platform not listed above.
As general advice:
- Warnings can be disregarded if the tests run. Most should tell you something about your compiler complaining about needless things, but some indicate flaws in the Hippo Mocks code. I'm always interested to hear about the warnings you receive.
- The IsVirtual test is a spike to see where it works. If this fails, Hippo Mocks itself will work. It tries to derive the function location of a function using a completely different and much less portable mechanic than Hippo Mocks currently uses, but it is slightly more versatile. I'm interested to see where it works and how to get it to work everywhere since it would allow non-virtual functions to be automatically recognised and marked as error or mocked using another mechanism.