build

Ubuntu16.0.4安装OpenCV3.4.2

久未见 提交于 2020-02-25 11:44:34
(1)到官网下载opencv3.4.2,链接:https://opencv.org/releases.html (2)下载opencv_contrib,链接:https://github.com/opencv/opencv_contrib/releases (2)将两个压缩包解压,进入opencv3.4.2目录创建build文件夹备用,创建install目录备用   mkdir build   mkdir install (3)安装依赖库   sudo apt-get install build-essential cmake cmake-qt-gui git libgtk2.0-dev pkg-config libavcodec-dev libavformat-dev libswscale-dev   sudo apt-get install libtbb2 libtbb-dev libjpeg-dev libpng-dev libtiff-dev libjasper-dev libdc1394-22-dev   sudo apt-get install libavcodec-dev libavformat-dev libv4l-dev liblapacke-dev libxvidcore-dev libx264-dev libatlas-base-dev gfortran

在Ubuntu18.04上安装opencv 3.4.1

三世轮回 提交于 2020-02-25 11:44:07
对于安装opencv有的人一次就成功,而有人安装了N多次才成功。我就是那个安装了N多次的人,每次遇到了很多安装错误,只能通过到网上搜教程资料,解决方法;通过一次次的试错,最终完成了安装。再此提醒第一次安装或则安装失败没有头绪的小伙伴,请注重官方安装教程: https://docs.opencv.org/master/d9/df8/tutorial_root.html 安装环境是:ubuntu 18.04 安装的opencv版本为3.4.1(其他版本也行,安装过程类似) opencv安装的依赖包有: Required Packages GCC 4.4.x or later CMake 2.8.7 or higher Git GTK+2.x or higher, including headers (libgtk2.0-dev) pkg-config Python 2.6 or later and Numpy 1.5 or later with developer packages (python-dev, python-numpy) ffmpeg or libav development packages: libavcodec-dev, libavformat-dev, libswscale-dev [optional] libtbb2 libtbb-dev [optional]

Android编译大全(五)

ⅰ亾dé卋堺 提交于 2020-02-25 11:13:36
6.1.2.make文件分类 2 配置类 主要用来配置product、board,以及根据你的Host和Target选择相应的工具以及设定相应的通用编译选项: config文件 说明 build/core/config.mk Config文件的概括性配置 build/core/envsetup.mk generate目录构成等配置 build/target/product 产品相关的配置 build/target/board 硬件相关的配置 build/core/combo 编译选项配置 这里解释下这里的board和product。board主要是设计到硬件芯片的配置,比如是否提供硬件的某些功能,比如说GPU等等,或者芯片支持浮点运算等等。product是指针对当前的芯片配置定义你将要生产产品的个性配置,主要是指APK方面的配置,哪些APK会包含在哪个product中,哪些APK在当前product中是不提供的。 config.mk是一个总括性的东西,它里面定义了各种module编译所需要使用的HOST工具以及如何来编译各种模块,比如说 BUILT_PREBUILT就定义了如何来编译预编译模块。envsetup.mk主要会读取由envsetup.sh写入环境变量中的一些变量来配置编译过程中的输出目录,combo里面主要定义了各种Host和Target结合的编译器和编译选项。 2

edgedb 内部pg 数据存储的探索 (三) 源码包setup.py 文件

好久不见. 提交于 2020-02-25 07:25:19
edgedb 是基于python开发的,同时集成了cython 以下为包的setup.py 配置,从里面我们可以看到关于edgedb 的一些依赖 以及构建过程 setup.py 源码 整体配置不算很多,500 多行,主要是cython extension 配置以及pg 构建配置,以及pg extension 配置,其中添加了关于pg 以及 pg 扩展build 的自定义cmdclass 代码 # # This source file is part of the EdgeDB open source project. # # Copyright 2008-present MagicStack Inc. and the EdgeDB authors. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed

Gradle Module Build Order

倖福魔咒の 提交于 2020-02-25 04:22:06
问题 I have a Gradle root project P with two subprojects P:foo and P:bar . Naturally, Gradle builds them in alphabetical order: bar , foo . But I need foo to be built first when I say gradle build in the P root directory. This is because bar depends on the AAR (Android library) artifact that foo publishes to the local Maven repository. Both bar and foo are such Android-library projects. This looks like an easy problem, but I can't figure it out. I read about evaluationDependsOn , so in bar/build

ionic 打包 报错Execution failed for task ':processDebugResources'. > com.android.ide.common.process.ProcessException: Failed to execute aapt

青春壹個敷衍的年華 提交于 2020-02-25 02:36:15
在platform --> android目录下找到build.gradle文件,打开并在def promptForReleaseKeyPassword() {...}函数前加入以下内容:    完整报错 BUILD FAILED Total time: 19.142 secs ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:ttcIndex FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':processDebugResources'. > com.android.ide.common.process.ProcessException: Failed to execute aapt * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Error: cmd: Command failed with exit code 1 Error output: ERROR: In

conda build ignoring my activated environment?

倖福魔咒の 提交于 2020-02-24 20:53:16
问题 I've created a Python 3 Conda environment, expressly for the purpose of testing whether a particular package could be built, targeting Python 3, as opposed to 2. However, when I launch a conda build from this environment, it appears to want to target Python 2.7: (pybert_py3) Davids-MacBook-Air-2:PyBERT dbanas$ conda build conda.recipe/chaco/ BUILD START: chaco-4.6.1-py27_0 I can find nothing in the meta.yaml file, which is directing the build towards Python 2.7. Does anyone know what's going

Cleanup Strategies after Building Source Code using eg. Git

安稳与你 提交于 2020-02-24 17:37:11
问题 I (mostly) use git to download and compile various projects from their source code, keeping my source in /usr/local/src and installing the binaries in /usr/local/bin . Following the building procedure, usually with ./configure && make && make install , I'm left with a lot of cruft that ends up as 'new' files in my local git repository. To my understanding, make clean , make distclean and possibly also (?) ./configure clean are thinkable procedures in order to trash most leftover files. But in

orzdba工具配置

无人久伴 提交于 2020-02-24 17:33:51
./orzdba -lazy -rt -S /u01/svr/working/my3306/run/mysql.sock mysql -s --skip-column-names -h127.0.0.1 -urep -P3306 -prep123 -Dmysql -S /u01/svr/working/my3306/run/mysql.sock 源代码地址:http://code.taobao.org/p/orzdba/src/trunk/ [root@hank-yoon servers]# chmod +x orzdba 在代码的160行左右,配置自己的MySQL验证信息:username、password、socket、host、port [root@hank-yoon servers]# grep -n 'my $MYSQL' orzdba 160:my $MYSQL = qq{mysql -s --skip-column-names -uroot -pyoon -h127.0.0.1 -P$port }; 先安装tcprstat [root@hank-yoon servers]# ln -sf /export/servers/tcprstat-static.v0.3.1.x86_64 /usr/bin/tcprstat [root@hank-yoon servers]

Cleanup Strategies after Building Source Code using eg. Git

大城市里の小女人 提交于 2020-02-24 17:32:08
问题 I (mostly) use git to download and compile various projects from their source code, keeping my source in /usr/local/src and installing the binaries in /usr/local/bin . Following the building procedure, usually with ./configure && make && make install , I'm left with a lot of cruft that ends up as 'new' files in my local git repository. To my understanding, make clean , make distclean and possibly also (?) ./configure clean are thinkable procedures in order to trash most leftover files. But in