ninja | 易学教程

How to build dynamic (shared) libraries of crashpad?

阅读更多关于 How to build dynamic (shared) libraries of crashpad?

问题 Crashpad is an error reporting system for c++ apps. https://chromium.googlesource.com/crashpad/crashpad/+/HEAD/doc/developing.md build instructions are $ cd ~/crashpad/crashpad $ gn gen out/Default $ ninja -C out/Default I can build predefined static libs but I have not found a way how to use gn or ninja to generate the shared libraries. 回答1: After running gn gen out\Default , you can edit the out\Default\toolchain.ninja file to add extra compiler flags to the command for the cc and cxx rules

How perform Visual studio 2019 Ninja builds with custom CMake version?

阅读更多关于 How perform Visual studio 2019 Ninja builds with custom CMake version?

问题 I'm trying to build a project with Ninja on Visual Studio 2019 from the IDE. I want to use a CMake version different from the one integrated in the VS 2019 distribution. I have set the cmakeExecutable variable in my CMakeSettings.json file to point to my system installation of CMake and the build works fine using the Visual Studio generator. However, if I use Ninja as generator, Visual Studio falls back using the VS-integrated version of CMake. Is there a way to build with Ninja and a custom

Chromium - mini_installer ignores branding

阅读更多关于 Chromium - mini_installer ignores branding

问题 After building chromium from source, you can create a "mini installer" for Windows by running ninja -C out\BuildFolder mini_installer This works fine and creates a mini_installer.exe in out\BuildFolder . see Chromium - How to make an actual installer out of mini_installer.exe for more details. But after running mini_installer.exe , the application ignores my branding and grd resource customizations. It is supposed to use "IDS_PRODUCT_NAME_BASE" which I have definitely customized. Here are the

Fatal Error building the llvm source code in Ubuntu

阅读更多关于 Fatal Error building the llvm source code in Ubuntu

问题 I am trying to build LLVM source code on Ubuntu 16.04. I have tried versions 4.0.1, 4.0.0 and 3.9.0 with sources from here. I have also tried using the source from svn as shown in several tutorials. Here is the error I get : [1480/1747] Linking CXX executable bin/clang-3.9 FAILED: : && /usr/bin/c++ -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wdelete-non-virtual

MSVC Incremental linking with CMake and the Ninja generator

阅读更多关于 MSVC Incremental linking with CMake and the Ninja generator

问题 I build a shared library with CMake and the Ninja generator on Windows. I'd like to use incremental linking to reduce the time required for linking. I tried to set CMAKE_SHARED_LINKER_FLAGS to "/incremental" but this flag is always overridden by a "/INCREMENTAL:NO" which is appended by CMake. I also tried to set MSVC_INCREMENTAL_DEFAULT to ON , but this didn't have any effect. So how can I get incremental linking working with CMake and the Ninja generator? 回答1: Turning my comment into an

CMake with MSVC Ninja gives compiler & test program error

阅读更多关于 CMake with MSVC Ninja gives compiler & test program error

问题 I have the following C++ build setup (using MSVC 2019 + Ninja): build.bat @echo off mkdir build_folder cd build_folder call "C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\CMake\bin\cmake.exe" -G "Ninja" -DCMAKE_CXX_COMPILER:FILEPATH="C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.21.27702/bin/HostX64/x64/cl.exe" -DCMAKE_C_COMPILER:FILEPATH="C:/Program Files (x86)/Microsoft Visual Studio/2019

CMake - compile natively and crosscompile the same code

阅读更多关于 CMake - compile natively and crosscompile the same code

问题 We're writing an application for an embedded ARM/Linux device. Development is performed on a Windows PC, using a crosscompiler, Eclipse and Ninja. CMake currently can create the build scripts that work well for the intended purpose. We have unit tests that run on the embedded device attached to the net, once the project is pushed (over Git) to the server. We're trying to implement unit tests, that would run on the PC, before we try them on the device. That means building natively, using MinGW

Error when try to compile Chromium

阅读更多关于 Error when try to compile Chromium

问题 I try to use the command ninja -C out/Debug chrome to compile Chromium. However the error msg says that: ninja error loading 'build.ninja': the system cannot find the file specified ninja Entering dictory 'out/Debug' Could I know what's the problem? Thanks. 回答1: The out directory and its contents (including build.ninja) are created by running python build\gyp_chromium or gclient runhooks Executing either command from within /src should allow your compile to proceed. 回答2: After the switch to

星云精准测试对安卓底层驱动代码的测试案例分析

阅读更多关于星云精准测试对安卓底层驱动代码的测试案例分析

Android原生底层驱动应用面极广，但一直没有很好的办法进行质量追踪。本文借助星云精准测试的高可靠性的测试技术手段，针对Android原生底层驱动进行分析、插桩、编译、采集数据、数据分析等，逐步讲解精准测试是如何实现android原生底层驱动的对接。在本文中，我们可以清晰地查看到如何进行技术对接的每一步，比如如何使用星云精准测试进行代码插桩、实现测试用例与采集底层驱动运行代码的数据追溯、对最终采集的数据进行一系列分析等。一、安卓源码精准测试流程概述经分析android源码的编译主要依靠Android.bp为纽带连接起来；在编译时，只需要在想要编译的模块目录下执行mm命令即可自动的根据当前目录下的Android.bp文件对其所包含的模块进行编译。主要流程大致为：先将ZOA通信库源码复制进去并加入某一层次的Android.bp中，再通过对包含所有Android.bp编译信息的ninja文件的解析可以得到Shell认可的插桩json文件，Shell通过json文件对对应目录的代码进行插桩，插桩完成后，把对ZOA通信库的引用加入该模块的Android.bp中再放入ZoaInstru.h头文件后就可以正常编译出插桩程序了。二、对安卓源码进行精准测试的准备工具 1．安卓原生8.1.0系统源码，放于/data/source2/目录下 2．shell.tar.gz插桩工具包放于

[xlua] build_xlua_with_libs生成

阅读更多关于 [xlua] build_xlua_with_libs生成

参考地址： https://github.com/chexiongsheng/build_xlua_with_libs 需要注意的是，在windows上编译安卓的时候，运行make_android_lua53.bat会报关于ninja.exe的错。如果用IDEA下载cmake的话就是正常的，参考: https://blog.csdn.net/sailuoatm/article/details/86625886 来源： https://my.oschina.net/diguo2046/blog/3133746