HomeSort by relevance Sort by last modified time
    Searched full:workaround (Results 51 - 75 of 1504) sorted by null

1 23 4 5 6 7 8 91011>>

  /ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/mpl/
integral_c_fwd.hpp 17 #include <boost/mpl/aux_/config/workaround.hpp>
  /ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/mpl/list/aux_/
include_preprocessed.hpp 16 #include <boost/mpl/aux_/config/workaround.hpp>
  /ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/numeric/conversion/
conversion_traits.hpp 14 #include "boost/detail/workaround.hpp"
  /ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/range/
config.hpp 14 #include <boost/detail/workaround.hpp>
  /ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/test/utils/basic_cstring/
basic_cstring_fwd.hpp 19 #include <boost/detail/workaround.hpp>
  /prebuilts/tools/common/proguard/proguard4.7/bin/
proguardgui.sh 14 # We're using the -D option as a workaround.
  /external/eigen/cmake/
language_support.cmake 6 # This additional function definition is needed to provide a workaround for
19 # My workaround is to invoke cmake twice. If both return codes are zero,
  /external/guava/guava-gwt/src/com/google/common/annotations/
Annotations.gwt.xml 13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
  /external/guava/guava-gwt/src/com/google/common/base/
Base.gwt.xml 13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
  /external/guava/guava-gwt/src/com/google/common/cache/
Cache.gwt.xml 13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
  /external/guava/guava-gwt/src/com/google/common/collect/
Collect.gwt.xml 13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
  /external/guava/guava-gwt/src/com/google/common/escape/
Escape.gwt.xml 13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
  /external/guava/guava-gwt/src/com/google/common/html/
Html.gwt.xml 19 Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none.
21 (I hope that this workaround does not cause its own problems in the future.)
  /external/guava/guava-gwt/src/com/google/common/io/
Io.gwt.xml 13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
  /external/guava/guava-gwt/src/com/google/common/math/
Math.gwt.xml 13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
  /external/guava/guava-gwt/src/com/google/common/primitives/
Primitives.gwt.xml 13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
  /external/guava/guava-gwt/src/com/google/common/util/concurrent/
Concurrent.gwt.xml 13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
  /external/guava/guava-gwt/src/com/google/common/xml/
Xml.gwt.xml 19 Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none.
21 (I hope that this workaround does not cause its own problems in the future.)
  /external/guava/guava-gwt/src/com/google/thirdparty/publicsuffix/
PublicSuffixPatterns.gwt.xml 19 Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none.
21 (I hope that this workaround does not cause its own problems in the future.)
PublicSuffixType.gwt.xml 19 Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none.
21 (I hope that this workaround does not cause its own problems in the future.)
  /external/guava/guava-gwt/test/com/google/common/collect/testing/
Testing.gwt.xml 13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
  /external/guava/guava-gwt/test/com/google/common/escape/testing/
Testing.gwt.xml 19 Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none.
21 (I hope that this workaround does not cause its own problems in the future.)
  /external/guava/guava-gwt/test/com/google/common/testing/
Testing.gwt.xml 13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
  /ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/type_traits/
add_reference.hpp 13 #include <boost/detail/workaround.hpp>
97 // agurt, 07/mar/03: workaround Borland's ill-formed sensitivity to an additional
  /ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/detail/
workaround.hpp 8 // Compiler/library version workaround macro
13 // // workaround for eVC4 and VC6
14 // ... // workaround code here
30 // which the workaround was known to have been required. When
33 // the workaround for any version of the compiler. When

Completed in 429 milliseconds

1 23 4 5 6 7 8 91011>>