arch

g++ on MacOSX doesn't work with -arch ppc64

匿名 (未验证) 提交于 2019-12-03 01:34:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 由 翻译 强力驱动 问题: I am trying to build a Universal binary on MacOSX with g++. However, it doesn't really work. I have tried with this simple dummy code: #include <iostream> using namespace std ; int main () { cout << "Hello" << endl ; } This works fine: % g ++ test . cpp - arch i386 - arch ppc - arch x86_64 - o test % file test test : Mach - O universal binary with 3 architectures test ( for architecture i386 ): Mach - O executable i386 test ( for architecture ppc7400 ): Mach - O executable ppc test ( for architecture x86_64 ): Mach - O 64 - bit

Howto prepare QTCreator for linux driver &amp; kernel development

匿名 (未验证) 提交于 2019-12-03 01:29:01
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: i tried a few IDEs on linux to develop driver in C. QtCreator suits best for me. I need the IDE just for the intellisence (codecompletion, jump to functions on click.. etc.) for quicker coding. Has anyone configured QTCreator for such needs. E.g. what do i have to do to get intellisence for a struct? regards camelord. 回答1: A better solution is to import the linux source with "Import Existing Project". Add all the files your ARCH requires. Once created edit the .includes file and remove all the include dirs listed. Then just add the few that

React Native XCode Project Product Archive Fails with duplicate symbols for architecture arm64

匿名 (未验证) 提交于 2019-12-03 01:26:01
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: Strangely, I can't seem to get Archive to work in XCode but the build succeeds without the errors on duplicate symbols if I do not attempt to Archive but simply build a release version. The project builds properly on devices as well. I have searched up on this topic and tried disabling testability, and setting the 'No Common Blocks' in the project settings to NO as well but no luck so far. The Project is a React Native 0.40 based project with CocoaPods installed as well. PodFile is this # You Podfile should look similar to this file. React

Unable to find CMake in android studio

匿名 (未验证) 提交于 2019-12-03 01:26:01
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I need to add C/C++ code in my android program for which I needed LLDB, CMake, and NDK. I found LLDB and NDK in SDK manager but CMake is missing from there. I tried manually downloading it from CMake official site and found out that for android we need SDK customized CMake. As you can see there is no option such as CMake. Can anyone help to find version of CMake for android? Thanks in advance. UPDATE Edit: I have tried CMake from the website and one I found in ndk-bundle/build folder, but both are giving the same error as below. Please take

Cross-compile Autotools-based Libraries for Official iPhone SDK

匿名 (未验证) 提交于 2019-12-03 01:07:01
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 由 翻译 强力驱动 问题: Background I am writing a program that targets several different phones, including the iPhone. The program depends on several thirdparty libraries. I am having difficulty cross-compiling these thirdparty libraries for the iPhone and iPhone simulator. The libraries include the Apache Portable Runtime and GNUTLS, as well as their dependencies. I would like the built libraries to end up in the prefixes "/opt/iphone-3.1", "/opt/iphone-3.0", "/opt/iphone-2.2.1", "/opt/iphone-simulator-3.1", and "/opt/iphone-simulator-3.0", respectively.

Multiple dex files define Landroid/arch/lifecycle/LiveData$LifecycleBoundObserver;

匿名 (未验证) 提交于 2019-12-03 01:06:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: when run app it show error Error:Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'. java.lang.RuntimeException: com.android.builder.dexing.DexArchiveMergerException: Unable to merge dex build.gradle dependencies { implementation 'com.android.support.constraint:constraint-layout:1.0.2' compile('com.mapbox.mapboxsdk:mapbox-android-navigation-ui:0.6.2') { transitive = true } compile 'com.mapbox.mapboxsdk:mapbox-android-navigation:0.6.2' compile 'com.google.firebase:firebase-auth:11.6.0' compile 'com.google

Caffe与NVIDIA Docker不兼容的问题

匿名 (未验证) 提交于 2019-12-03 00:37:01
文章作者:Tyan 博客: noahsnail.com CSDN 简书 今天在使用Dockerfile构建Caffe Docker Image时碰到了一个Caffe与NVIDIA Docker不兼容的问题,我使用的NVIDIA Docker为 FROM nvidia/cuda:9.0-cudnn7-devel-ubuntu16.04 ,出现的错误为: nvcc fatal : Unsupported gpu architecture 'compute_20 ' 解决方案: # 在Dockerfile中添加 ENV CUD A_ARCH _BIN "35 52 60 61 70" ENV CUD A_ARCH _PTX "52 70" # 在CMake时添加参数 -DCUD A_ARCH _NAME=Manual -DCUD A_ARCH _BIN=${CUD A_ARCH _BIN} -DCUD A_ARCH _PTX=${CUD A_ARCH _PTX} 注意: 35 52 60 61 70 是CUDA显卡的计算能力。 CUDA_ARCH_BIN 参数指定的是显卡的计算能力, CUDA_ARCH_PTX 是PTX代码生成的对应库文件,与显卡计算能力对应。 CUDA_ARCH_PTX 必须包含你的显卡,否则会报错。错误如下: Check failed: error ==

u-boot-2018.05之make编译过程分析

匿名 (未验证) 提交于 2019-12-03 00:29:01
综述 u-boot 自 v2014.10 版本开始引入 KBuild 系统,同更改前的编译系统相比,由于 Kbuild 系统的原因,其 Makefile 变得更加复杂。 u-boot的编译跟kernel编译一样,分两步执行: 第一步:配置,执行 make xxx_defconfig 进行各项配置,生成 .config 文件 第二部:编译,执行 make 进行编译,生成可执行的二进制文件u-boot.bin或u-boot.elf Makefile的核心是依赖和命令。对于每个目标,首先会检查依赖,如果依赖存在,则执行命令更新目标;如果依赖不存在,则会以依赖为目标,先生成依赖,待依赖生成后,再执行命令生成目标。 博客《》详尽解释了第一步的操作,在这一步中,u-boot执行配置命令 make xxx_defconfig 时先搜集所有默认的 Kconfig 配置,然后再用命令行指定的 xxx_defconfig 配置进行更新并输出到根目录的 .config 文件中。 配置完成后执行make命令生成二进制文件的过程,由于涉及的依赖和命令很多,也将make编译过程分析分为两部分,目标依赖和命令执行。 博客《》中描述了 make 过程中的依赖关系 本篇主要分析 make 过程中的通过命令生成各个目标的依赖,从而一步一步更新目标,直至更新并生成顶层目标 u-boot.bin 。 第二部分

ArcGIS水文分析实战教程(16) ArcHydro 修正地形

匿名 (未验证) 提交于 2019-12-03 00:22:01
本章导读:前面的十几个章节几乎都是通过使用 DEM 数据进行水利数据的提取,水利数据都是基于地形进行衍生。但现实中一般很难得到非常精确的 DEM 数据,如果 DEM 的精度不能确保,那么提取出来的数据很难与其他现有的矢量数据进行叠加使用。本章通过 ArcHydro 工具对地形进行修正,修正后的地形则可以与现有的矢量数据进行叠加使用,更加贴合实际情况。 BY 李远祥 前面十几个章节的内容几乎都是围绕 DEM 数据衍生出诸如河流、流域等水利要素。这种做法有它的好处也有它的弊端。 好处是利用地形能够快速的生成河流和流域,便于从自然角度上圈出对应的水文范围;DEM 本身带有地形起伏的信息,而经过流向分析之后,提取出来的自然河流本身带准确的流向,这样可以为后期水文信息化提供了精细而准确的数据来源。 弊端也是非常明显。首先地形数据本身很难获取(至少在国内是这样的情况),包括等值线、高程控制点或者原始的 DEM 数据,这给基于地形的水文分析带来了一定的困扰。虽然网上也可以下载到全球免费的 DEM 数据,但 30 米精度的 DEM 对于大江大河没有太大的问题,对于小河流和小流域,那是在不敢恭维。其次,很多水文单位已经有固定的河流矢量数据(这些河流一般都是通过实际测绘进行标绘的),并且所有的断面数据均基于这些现有的矢量河流数据进行标绘,所以,不论是 DEM 提取的河流还是出水口、河源

Qt的pro文件里如何判断系统是32位或64位

匿名 (未验证) 提交于 2019-12-03 00:19:01
转载自:http://shitou7630.blog.163.com/blog/static/3269953620161126105156562/ 1、解决方案1 QT_ARCH 32 64 32-bit i386 contains(QT_ARCH, i386) { 2、解决方案2 貌似也有人用QMAKE_TARGET.arch进行判断,但是可能只适用windows,不适合跨平台。 win32 { ## Windows common build here QMAKE_HOST .arch, x86_64) { ## Windows x86 (32bit) specific build here ## Windows x64 (64bit) specific build here } 3、解决方案3 利用自定义的字符变量进行判断。 Qt allows you to pass arbitrary config parameters which you can use to separate the targets. By having a conditional config in your project file: CONFIG(myX64, myX64|myX32) { } else { } qmake CONFIG+=myX64 you get the wanted