build

Cleanup Strategies after Building Source Code using eg. Git

由 怎甘沉沦 提交于 2020-02-24 17:32:06
问题 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

ABAP system landscape和vue项目webpack构建的最佳实践

由 匆匆过客 提交于 2020-02-24 11:12:22
基于Netweaver的ABAP transport route一般都有dev，test和prod三种类型的系统。 而Vue前端项目的webpack build设置也类似。 以 SAP成都研究院数字创新空间开发的智能服务 前端实现为例, 在package.json里定义了名为dev和build两个script： "scripts": { "dev": "webpack-dev-server --inline --progress --config build/webpack.dev.conf.js", "start": "npm run dev", "build": "node build/build.js" } 一旦运行npm run dev，会观察到在dev环境下使用了webpack-dev-server这个依赖启动了web服务器 当然webpack-dev-server这个依赖也必须定义在package.json的dependencies区域里： npm install把所有依赖下载到本地后，也能观察到webpack-dev-server.js这个依赖的实现： 执行命令行npm run dev, 实际上执行的命令行为： node "C:Usersi042416Documents_DISCodeSmartServiceFront ode_modules.bin..webpack

Building Cairo for Windows with MinGW (Problems linking libpng)

由 一笑奈何 提交于 2020-02-24 07:00:28
问题 I'm trying to build cairo on Windows using MinGW (and MSYS). I am following the instrucions on Compiling GTK+ 2.16.4 for Windows, except that I'm using the latest versions whenever possible, i.e: zlib-1.2.3 libpng-1.2.42 pixman-0.17.4 cairo-1.8.8 This works pretty well up until when I try to build the actual cairo. The configuration succeeds, but during make cairo seems to have problems linking to my build of libpng. After a little while I get a long list of errors such as this: .libs/cairo

Could not calculate build plan:

由 拈花ヽ惹草 提交于 2020-02-23 13:42:27
问题： Could not calculate build plan: Failure to transfer org.apache.maven.plugins:maven-surefire-plugin:pom:2.7.1 from http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-surefire-plugin:pom:2.7.1 from/to central (http://repo1.maven.org/maven2): Access denied to http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.7.1/maven-surefire-plugin-2.7.1.pom. Error code 407, Proxy

gradle: Skipping task ':compileJava' as it has no source files

由 ぐ巨炮叔叔 提交于 2020-02-23 09:22:10
问题 i try gradle -d compileJava in my try project, and gradle raise "Skipping task ':compileJava' as it has no source files.". the worse thing is that i can't see anything created in build/. i create this project only with running gradle init and creating a "src/Ex.java". my question is: How to load default "compileJava" or define my "compileJava" to fix this warning. 回答1: By default, Java source files need to go into src/main/java (or src/test/java for test sources). Either adapt your directory

Maintain src/ folder structure when building to dist/ folder with Typescript 3

由 安稳与你 提交于 2020-02-23 09:07:56
问题 I have a typescript nodejs server with this structure: tsconfig.json package.json src/ middleware/ utils/ index.ts dist/ middleware/ utils/ index.ts When using Typescript 2, I was able to transpile my project from the src/ to a dist/ folder and have a mirror image of my directory structure to work with. With the release of Typescript 3 they have introduced project references and changed the way code is transpiled into an output directory. Now tsc outputs to the dist/ folder in a nested way

Maintain src/ folder structure when building to dist/ folder with Typescript 3

由 只谈情不闲聊 提交于 2020-02-23 09:06:23
问题 I have a typescript nodejs server with this structure: tsconfig.json package.json src/ middleware/ utils/ index.ts dist/ middleware/ utils/ index.ts When using Typescript 2, I was able to transpile my project from the src/ to a dist/ folder and have a mirror image of my directory structure to work with. With the release of Typescript 3 they have introduced project references and changed the way code is transpiled into an output directory. Now tsc outputs to the dist/ folder in a nested way

python 集成cython 简单测试

由 纵饮孤独 提交于 2020-02-23 09:06:02
实际开发中我们可能需要集成c/c++ 编写的模块，我们可以通过cython 解决类似的问题 以下测试一个简单的c add 方法, 使用venv 同时构建为一个pip 包 环境准备 venv 初始化 python3 -m venv . 添加项目依赖包 pip install click cython 代码结构 ├── Makefile ├── README.md ├── cli │ ├── __init__.py │ └── app.pyx ├── ext │ ├── Makefile │ ├── add.c │ ├── add.h ├── pyvenv.cfg └── setup.py c 项目代码说明 ext 目录为c add 函数同时make 进行项目构建 add.h int add(int first,int second); add.c #include "add.h" int add(int first,int second){ return first+second; } Makefile: 主要是进行静态库的构建 CC = gcc default: libadd.a libadd.a: add.o ar rcs $@ $^ add.o: add.c add.h $(CC) -c $< clean: rm *.o *.a cython 包装c 静态库 lib/app

Linux内核配置make x210ii_qt_defconfig做了什么？

由 依然范特西╮ 提交于 2020-02-23 05:17:27
　　执行make x210ii_qt_defconfi时进入根目录Makefile匹配%config目标，该目标的依赖关系链如下： 　　%config（1） 　　scripts_basic（1.1）outputmakefile（1.2）FORCE（1.3） 　　开始执行1.1，$(Q)$(MAKE) $(build)=scripts/basic 该句执行make -f scripts/Makefile.build 并且定义obj=scripts/basic；先包含scripts/basic/Makefile,默认执行要获得__build,其此时依赖关系链如下： 　　__build（2） 　　scripts/basic/fixdep（2.1） scripts/basic/docproc（2.2） scripts/basic/hash（2.3） 　　2.1，2.2，2.3由scripts/Makefile.host依据scripts/basic材料获得，2为空退出，回到1.2 又1.2 1.3为空则开始1 的命令，$(Q)mkdir -p include/linux include/config创建目录，$(Q)$(MAKE) $(build)=scripts/kconfig $@，该句执行make -f scripts/Makefile.build x210ii_qt

linux kernel make构建分析

由 对着背影说爱祢 提交于 2020-02-23 05:17:10
前言 之前对uboot的构建进行了分析，现在再对linux kernel的构建进行分析。几年前的确也分析过，但是只是停留在笔记层面，没有转为文章，这次下定决定来完善它。 环境 同样，采用的还是zynq平台的linux，从Makefile可以看到版本： VERSION = 3 PATCHLEVEL = 15 SUBLEVEL = 0 EXTRAVERSION = NAME = Shuffling Zombie Juror linux Makefile支持的选项（最常用到的） 选项V，用于开启或者关闭执行make时编译信息的打印 @echo ' make V=0|1 [targets] 0 => quiet build (default), 1 => verbose build' @echo ' make V=2 [targets] 2 => give reason for rebuild of target' ifeq ("$(origin V)", "command line") KBUILD_VERBOSE = $(V) endif ifndef KBUILD_VERBOSE KBUILD_VERBOSE = 0 endif 选项C，用于开启或者关闭静态代码检查 @echo ' make C=1 [targets] Check all c source with $$CHECK
订阅 build