GVKun编程网logo

【AndroidStudio】找不到android.support.v4 & android.support.v7（androidstudio找不到设备）

4

如果您想了解【AndroidStudio】找不到android.support.v4&android.support.v7的相关知识，那么本文是一篇不可错过的文章，我们将对androidstudio找

如果您想了解【AndroidStudio】找不到android.support.v4 & android.support.v7的相关知识，那么本文是一篇不可错过的文章，我们将对androidstudio找不到设备进行全面详尽的解释，并且为您提供关于android Conflict with dependency 'com.android.support:support-annotations' in project ':app'.、Android Facebook SDK – android.support-v4问题(未找到类android.support.v4.app.Fragment)、Android std and stl support - C++ Library Support、Android Studio 新建项目 gradle 编译错误：Conflict with dependency com.android.support:support-annotations 解决办法的有价值的信息。

本文目录一览：

【AndroidStudio】找不到android.support.v4 & android.support.v7（androidstudio找不到设备）

【AndroidStudio】找不到android.support.v4 & android.support.v7（androidstudio找不到设备）

【问题描述】
在AndroidStudio中导入新的项目，出现无法找到以下两个包的问题：

import android.support.v4.app.ActivityCompat;
import android.support.v7.app.AppCompatActivity;

【解决步骤】
1.点击菜单栏 file > Projects Structure（或者通过快捷键 Ctrl+Alt+Shift+S 快速打开）；

2. 选择 Depandencies > app > 点击 “+”，选择第一个选项“Library Dependencies”

3.在弹出的界面上搜索并添加

4.之后就等Gradle构建完成就ok了。

android Conflict with dependency 'com.android.support:support-annotations' in project ':app'.

android Conflict with dependency 'com.android.support:support-annotations' in project ':app'.

如题所示 只是新建了一个项目就报这个错了。

问题 以后解决了如下：


这样就可以了。但是原因了我还是不知道。我也没有修改或者升级什么东西。。知道原因的大佬请告知一下。

转载自：https://blog.csdn.net/qq_33313551/article/details/80240332


Android Facebook SDK – android.support-v4问题(未找到类android.support.v4.app.Fragment)

Android Facebook SDK – android.support-v4问题(未找到类android.support.v4.app.Fragment)

我无法让Facebook SDK(v3.7)在我的Android Intellij项目中运行.

我按照these steps将Facebook库添加为我的项目的新模块,但我不断收到此错误：

java: cannot access android.support.v4.app.Fragment
class file for android.support.v4.app.Fragment not found

以下是我的模块依赖项的屏幕截图：

这是Facebook模块依赖项的屏幕截图：

当我将v4支持库添加到我自己的模块时,我得到一个不同的错误：

Android Dex: [FunnyGific] com.android.dex.DexException: Multiple dex files define Lcom/facebook/Accesstoken$1;

我尝试使用在facebook-android-sdk-3.7 / facebook / libs文件夹中找到的android-support-v4.jar,也尝试通过Maven导入它,我一直得到同样的错误.这里有什么想法？

我可以让它工作的唯一情况是添加Facebook mvn存储库,但即使在这种情况下,当我尝试显示Facebook LoginButton(java.lang.classNotFoundException：com.facebook.android)时,我会遇到一些奇怪的异常. R $颜色)：

<dependency>
    <groupId>fr.avianey</groupId>
    <artifactId>facebook-android-api</artifactId>
    <version>3.8.0</version>
    <type>aar</type>
</dependency>

没有想法,会喜欢一些帮助,让这个工作.

解决方法:

我刚刚在IdeaU v14中遇到过这个问题：找不到FragmentActivity！

1)图书馆设置：

2)类路径添加

3)找到额外的> Android>支持> v4(或您需要的任何版本)

4)高兴！红色的波浪走开了.

Android std and stl support - C++ Library Support

Android std and stl support - C++ Library Support

Android std and stl support - C++ Library Support

https://developer.android.com/ndk/guides/cpp-support.html


The Android platform provides a very minimal C++ runtime support library (libstdc++).This minimal support does not include, for example:

  • Standard C++ Library support (except a few trivial headers).
  • C++ exceptions support
  • RTTI support

The NDK provides headers for use with this default library. In addition, the NDK provides anumber of helper runtimes that provide additional features. This page provides information aboutthese helper runtimes, their characteristics, and how to use them.

Helper Runtimes

Table 1 provides names, brief explanations, and features of runtimes available inthe NDK.

Table 1. NDK Runtimes and Features.

Name Explanation> Features
libstdc++ (default) The default minimal system C++ runtime library. N/A
gabi++_static The GAbi++ runtime (static). C++ Exceptions and RTTI
gabi++_shared The GAbi++ runtime (shared). C++ Exceptions and RTTI
stlport_static The STLport runtime (static). C++ Exceptions and RTTI; Standard Library
stlport_shared The STLport runtime (shared). C++ Exceptions and RTTI; Standard Library
gnustl_static The GNU STL (static). C++ Exceptions and RTTI; Standard Library
gnustl_shared The GNU STL (shared). C++ Exceptions and RTTI; Standard Library
c++_static The LLVM libc++ runtime (static). C++ Exceptions and RTTI; Standard Library
c++_shared The LLVM libc++ runtime (shared). C++ Exceptions and RTTI; Standard Library

How to set your runtime

Use the APP_STL variable in your Application.mk file to specify the runtime you wish to use. Use the values inthe "Name" column in Table 1 as your setting. For example:

APP_STL := gnustl_static

You may only select one runtime for your app, and can only do inApplication.mk.

Even if you do not use the NDK build system, you can still use STLport, libc++ or GNU STL.For more information on how to use these runtimes with your own toolchain, see Standalone Toolchain.

Runtime Characteristics

libstdc++ (default system runtime)

This runtime only provides the following headers, with no support beyond them:

  • cassert
  • cctype
  • cerrno
  • cfloat
  • climits
  • cmath
  • csetjmp
  • csignal
  • cstddef
  • cstdint
  • cstdio
  • cstdlib
  • cstring
  • ctime
  • cwchar
  • new
  • stl_pair.h
  • typeinfo
  • utility

GAbi++ runtime

This runtime provides the same headers as the default runtime, but adds support for RTTI(RunTime Type Information) and exception handling.

STLport runtime

This runtime is an Android port of STLport(http://www.stlport.org). It provides a complete set of C++standard library headers. It also, by embedding its own instance of GAbi++, provides support forRTTI and exception handling.

While shared and static versions of this runtime are avilable, we recommend using the sharedversion. For more information, see Static runtimes.

The shared library file is named libstlport_shared.so instead of libstdc++.soas is common on other platforms.

In addition to the static- and shared-library options, you can also force the NDK tobuild the library from sources by adding the following line to your Application.mkfile, or setting it in your environment prior to building: 

STLPORT_FORCE_REBUILD := true

GNU STL runtime

This runtime is the GNU Standard C++ Library, (libstdc++-v3). Its shared library file isnamed libgnustl_shared.so.

libc++ runtime:

This runtime is an Android port of LLVM libc++. Itsshared library file is named libc++_shared.so.

By default, this runtime compiles with -std=c++11. As with GNU libstdc++, youneed to explicitly turn on exceptions or RTTI support. For information on how to do this, seeC++ Exceptions and RTTI.

The NDK provides prebuilt static and shared libraries for libc++, but you can force theNDK to rebuild libc++ from sources by adding the following line to yourApplication.mk file, or setting it in your environment prior to building: 

LIBCXX_FORCE_REBUILD := true

Atomic support

If you include <atomic>, it''s likely that you also need libatomic.If you are using ndk-build, add the following line:

LOCAL_LDLIBS += -latomic

If you are using your own toolchain, use:

-latomic

Compatibility

The NDK''s libc++ is not stable. Not all the tests pass, and the test suite is not comprehensive.Some known issues are:

  • Using c++_shared on ARM can crash when an exception is thrown.
  • Support for wchar_t and the locale APIs is limited.

You should also make sure to check the "Known Issues" section of the changelog for the NDKrelease you are using.

Warning: Attempting to change to an unsupported locale willnot fail. The operation will succeed, but the locale will not change and thefollowing message will appear in logcat.

newlocale() WARNING: Trying to set locale to en_US.UTF-8 other than "", "C" or "POSIX"

Important Considerations

C++ Exceptions

In all versions of the NDK later than NDKr5, the NDK toolchain allows you to use C++ runtimesthat support exception handling. However, to ensure compatibility with earlier releases, itcompiles all C++ sources with -fno-exceptions support by default. You can enable C++exceptions either for your entire app, or for individual modules.

To enable exception-handling support for your entire app, add the following line toyour Application.mk file.To enable exception-handling support for individual modules'', add the following line totheir respective Android.mk files.

APP_CPPFLAGS += -fexceptions

RTTI

In all versions of the NDK later than NDKr5, the NDK toolchain allows you to use C++ runtimesthat support RTTI. However, to ensure compatibility with earlier releases, it compiles all C++sources with -fno-rtti by default.

To enable RTTI support for your entire app for your entire application, add the following line toyour Application.mk file:

APP_CPPFLAGS += -frtti
To enable RTTI support for individual modules, add the following line totheir respective Android.mk files: 
LOCAL_CPP_FEATURES += rtti
Alternatively, you can use: 
LOCAL_CPPFLAGS += -frtti

Static runtimes

Linking the static library variant of a C++ runtime to more than one binary may result inunexpected behavior. For example, you may experience:

  • Memory allocated in one library, and freed in the other, causing memory leakage or heapcorruption.
  • Exceptions raised in libfoo.so going uncaught in libbar.so, causing your appto crash.
  • Buffering of std::cout not working properly

In addition, if you link two shared libraries–or a shared library and an executable–against the same static runtime, the final binary image of each shared library includes a copy ofthe runtime''s code. Having multiple instances of runtime code is problematic because of duplicationof certain global variables that the runtime uses or provides internally.

This problem does not apply to a project comprising a single shared library. For example,you can link against stlport_static, and expect your app to behave correctly. If yourproject requires several shared library modules, we recommend that you use the shared libraryvariant of your C++ runtime.

Shared runtimes

If your app targets a version of Android earlier than Android 4.3 (Android API level 18),and you use the shared library variant of a given C++ runtime, you must load the shared librarybefore any other library that depends on it.

For example, an app may have the following modules:

  • libfoo.so
  • libbar.so which is used by libfoo.so
  • libstlport_shared.so, used by both libfoo and libbar

You must load the libraries in reverse dependency order: 

    static {
      System.loadLibrary("stlport_shared");
      System.loadLibrary("bar");
      System.loadLibrary("foo");
    }

Note: Do not use the lib prefix when callingSystem.loadLibrary().

Licensing

STLport is licensed under a BSD-style open-source license. See$NDK/sources/cxx-stl/stlport/README for more details about STLport.

GNU libstdc++ is covered by the GPLv3 license, and not the LGPLv2 or LGPLv3. Formore information, see License on the GCC website.

LLVM libc++is dual-licensed under both the University of Illinois "BSD-Like" license and the MIT license.


Android Studio 新建项目 gradle 编译错误：Conflict with dependency com.android.support:support-annotations 解决办法

Android Studio 新建项目 gradle 编译错误：Conflict with dependency com.android.support:support-annotations 解决办法

Rebuild 一下

关于【AndroidStudio】找不到android.support.v4 & android.support.v7和androidstudio找不到设备的介绍已经告一段落，感谢您的耐心阅读，如果想了解更多关于android Conflict with dependency 'com.android.support:support-annotations' in project ':app'.、Android Facebook SDK – android.support-v4问题(未找到类android.support.v4.app.Fragment)、Android std and stl support - C++ Library Support、Android Studio 新建项目 gradle 编译错误：Conflict with dependency com.android.support:support-annotations 解决办法的相关信息，请在本站寻找。

本文标签：

上一篇android studio教程-bill配套视频代码：3.editview 可编辑框（用android studio做一个视频播放器）

下一篇Android 开发技术周报 Issue#285（安卓开发技术周报）

相关文章