diff options
| author |  epoger@google.com <epoger@google.com@2bbb7eff-a529-9590-31e7-b0007b416f81> | 2011-05-17 17:36:59 +0000 |
|---|---|---|
| committer | epoger@google.com <epoger@google.com@2bbb7eff-a529-9590-31e7-b0007b416f81> | 2011-05-17 17:36:59 +0000 |
| commit | 2047f00e4698f83499ab91911999a65c21a951c9 (patch) | |
| tree | 404b1c30d3f764fa05e3770c09fc1e43449a4d65 /include/config | |
| parent | d31cbc465088a253b5574b0305e09f9301b2bf81 (diff) | |
get tests closer to passing for SKIA_SCALAR=fixed
http://codereview.appspot.com/4532064/
git-svn-id: http://skia.googlecode.com/svn/trunk@1351 2bbb7eff-a529-9590-31e7-b0007b416f81
Diffstat (limited to 'include/config')
| -rw-r--r-- | include/config/SkUserConfig.h | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/include/config/SkUserConfig.h b/include/config/SkUserConfig.h index aa2e6cf40b..c56d8cfa78 100644 --- a/include/config/SkUserConfig.h +++ b/include/config/SkUserConfig.h @@ -54,7 +54,7 @@ /* Somewhat independent of how SkScalar is implemented, Skia also wants to know if it can use floats at all. Naturally, if SK_SCALAR_IS_FLOAT is defined, - then so muse SK_CAN_USE_FLOAT, but if scalars are fixed, SK_CAN_USE_FLOAT + SK_CAN_USE_FLOAT must be too; but if scalars are fixed, SK_CAN_USE_FLOAT can go either way. */ //#define SK_CAN_USE_FLOAT @@ -151,4 +151,3 @@ #endif #endif - |