 2020 中国开源年度报告
段有 Artifact Hub、Backstage 等 44 个项⽬。  孵化(incubating):同沙箱流程,所有的例外情况(包括拒绝)均由 TOC 来处理。⽬ 前该阶段的项⽬有 Argo、Buildpacks、CloudEvents、CNI、Contour、Cortex、CRI- O、Dragonfly、Falco、gRPC、KubeEdge、Linkerd、NATS、Notary、Open0 码力 | 46 页 | 4.09 MB | 1 年前3 2020 中国开源年度报告
段有 Artifact Hub、Backstage 等 44 个项⽬。  孵化(incubating):同沙箱流程,所有的例外情况(包括拒绝)均由 TOC 来处理。⽬ 前该阶段的项⽬有 Argo、Buildpacks、CloudEvents、CNI、Contour、Cortex、CRI- O、Dragonfly、Falco、gRPC、KubeEdge、Linkerd、NATS、Notary、Open0 码力 | 46 页 | 4.09 MB | 1 年前3
 Pro Git 2nd Edition 2.1.413directory structure in Git. A SHA-1 hash looks something like this: 24b9da6552252987aa493b52f8696cd6d3b00373 You will see these hash values all over the place in Git because it uses them so much. In signatures if you want to verify your download. Then, compile and install: $ tar -zxf git-2.8.0.tar.gz $ cd git-2.8.0 $ make configure $ ./configure --prefix=/usr $ make all doc info $ sudo make install install-doc depending on which system you’re running: for Linux: $ cd /home/user/my_project for macOS: $ cd /Users/user/my_project for Windows: $ cd C:/Users/user/my_project and type: $ git init This creates0 码力 | 731 页 | 21.49 MB | 1 年前3 Pro Git 2nd Edition 2.1.413directory structure in Git. A SHA-1 hash looks something like this: 24b9da6552252987aa493b52f8696cd6d3b00373 You will see these hash values all over the place in Git because it uses them so much. In signatures if you want to verify your download. Then, compile and install: $ tar -zxf git-2.8.0.tar.gz $ cd git-2.8.0 $ make configure $ ./configure --prefix=/usr $ make all doc info $ sudo make install install-doc depending on which system you’re running: for Linux: $ cd /home/user/my_project for macOS: $ cd /Users/user/my_project for Windows: $ cd C:/Users/user/my_project and type: $ git init This creates0 码力 | 731 页 | 21.49 MB | 1 年前3
 Pro Git 2nd Edition 2.1.413or directory structure in Git. A SHA-1 hash looks something like this: 24b9da6552252987aa493b52f8696cd6d3b00373 You will see these hash values all over the place in Git because it uses them so much. In signatures if you want to verify your download. Then, compile and install: $ tar -zxf git-2.8.0.tar.gz $ cd git-2.8.0 $ make configure $ ./configure --prefix=/usr $ make all doc info $ sudo make install install-doc depending on which system you’re running: for Linux: $ cd /home/user/my_project for macOS: $ cd /Users/user/my_project for Windows: $ cd C:/Users/user/my_project and type: $ git init This creates0 码力 | 501 页 | 17.96 MB | 1 年前3 Pro Git 2nd Edition 2.1.413or directory structure in Git. A SHA-1 hash looks something like this: 24b9da6552252987aa493b52f8696cd6d3b00373 You will see these hash values all over the place in Git because it uses them so much. In signatures if you want to verify your download. Then, compile and install: $ tar -zxf git-2.8.0.tar.gz $ cd git-2.8.0 $ make configure $ ./configure --prefix=/usr $ make all doc info $ sudo make install install-doc depending on which system you’re running: for Linux: $ cd /home/user/my_project for macOS: $ cd /Users/user/my_project for Windows: $ cd C:/Users/user/my_project and type: $ git init This creates0 码力 | 501 页 | 17.96 MB | 1 年前3
 Pro Git 2nd Edition 2.1.413 directory structure in Git. A SHA-1 hash looks something like this: 24b9da6552252987aa493b52f8696cd6d3b00373 You will see these hash values all over the place in Git because it uses them so much. In signatures if you want to verify your download. Then, compile and install: $ tar -zxf git-2.8.0.tar.gz $ cd git-2.8.0 $ make configure $ ./configure --prefix=/usr $ make all doc info $ sudo make install install-doc depending on which system you’re running: for Linux: $ cd /home/user/my_project for macOS: $ cd /Users/user/my_project for Windows: $ cd C:/Users/user/my_project and type: $ git init This creates0 码力 | 691 页 | 13.35 MB | 1 年前3 Pro Git 2nd Edition 2.1.413 directory structure in Git. A SHA-1 hash looks something like this: 24b9da6552252987aa493b52f8696cd6d3b00373 You will see these hash values all over the place in Git because it uses them so much. In signatures if you want to verify your download. Then, compile and install: $ tar -zxf git-2.8.0.tar.gz $ cd git-2.8.0 $ make configure $ ./configure --prefix=/usr $ make all doc info $ sudo make install install-doc depending on which system you’re running: for Linux: $ cd /home/user/my_project for macOS: $ cd /Users/user/my_project for Windows: $ cd C:/Users/user/my_project and type: $ git init This creates0 码力 | 691 页 | 13.35 MB | 1 年前3
 Pro Git 中文版 第2版 2.1.6640 个十六进制字符(0-9 和 a-f)组 成的字符串,基于 Git 中文件的内容或目录结构计算出来。 SHA-1 哈希看起来是这样: 24b9da6552252987aa493b52f8696cd6d3b00373 Git 中使用这种哈希值的情况很多,你将经常看到这种哈希值。 实际上,Git 数据库中保存的信息都是以文件内 容的哈希值来索引,而不是文件名。 Git 一般只添加数据 你执行的 GitHub 上的是最新版本,但 kernel.org 上包含有文件下载签 名,如果你想验证下载正确性的话会用到。 接着,编译并安装: 24 $ tar -zxf git-2.8.0.tar.gz $ cd git-2.8.0 $ make configure $ ./configure --prefix=/usr $ make all doc info $ sudo make install install-doc 来控制它,那么首先需要进入该项目目录中。 如果你还 没这样做过,那么不同系统上的做法有些不同: 在 Linux 上: $ cd /home/user/my_project 在 macOS 上: $ cd /Users/user/my_project 在 Windows 上: $ cd /c/user/my_project 之后执行: $ git init 该命令将创建一个名为 .git 的子目录,这个子目录含有你初始化的0 码力 | 501 页 | 19.30 MB | 1 年前3 Pro Git 中文版 第2版 2.1.6640 个十六进制字符(0-9 和 a-f)组 成的字符串,基于 Git 中文件的内容或目录结构计算出来。 SHA-1 哈希看起来是这样: 24b9da6552252987aa493b52f8696cd6d3b00373 Git 中使用这种哈希值的情况很多,你将经常看到这种哈希值。 实际上,Git 数据库中保存的信息都是以文件内 容的哈希值来索引,而不是文件名。 Git 一般只添加数据 你执行的 GitHub 上的是最新版本,但 kernel.org 上包含有文件下载签 名,如果你想验证下载正确性的话会用到。 接着,编译并安装: 24 $ tar -zxf git-2.8.0.tar.gz $ cd git-2.8.0 $ make configure $ ./configure --prefix=/usr $ make all doc info $ sudo make install install-doc 来控制它,那么首先需要进入该项目目录中。 如果你还 没这样做过,那么不同系统上的做法有些不同: 在 Linux 上: $ cd /home/user/my_project 在 macOS 上: $ cd /Users/user/my_project 在 Windows 上: $ cd /c/user/my_project 之后执行: $ git init 该命令将创建一个名为 .git 的子目录,这个子目录含有你初始化的0 码力 | 501 页 | 19.30 MB | 1 年前3
 Pro Git 中文版 第2版 2.1.6640 个十六进制字符(0-9 和 a-f)组成的字符串,基于 Git 中文件的内容或目录结 构计算出来。 SHA-1 哈希看起来是这样: 24b9da6552252987aa493b52f8696cd6d3b00373 Git 中使用这种哈希值的情况很多,你将经常看到这种哈希值。 实际上,Git 数据库中保存的信息都是以文件内容的哈希值来索引,而不是文件名。 Git 一般只添加数据 你执行的 GitHub 上 的是最新版本,但 kernel.org 上包含有文件下载签名,如果你想验证下载正 确性的话会用到。 接着,编译并安装: $ tar -zxf git-2.8.0.tar.gz $ cd git-2.8.0 $ make configure $ ./configure --prefix=/usr $ make all doc info $ sudo make install install-doc 来控制它,那么首先 需要进入该项目目录中。 如果你还没这样做过,那么不同系统上的做法有些 不同: 在 Linux 上: $ cd /home/user/my_project 在 macOS 上: $ cd /Users/user/my_project 在 Windows 上: $ cd /c/user/my_project 之后执行: $ git init 该命令将创建一个名为 .git 的子目录,这个子目录含有你初始化的0 码力 | 670 页 | 13.59 MB | 1 年前3 Pro Git 中文版 第2版 2.1.6640 个十六进制字符(0-9 和 a-f)组成的字符串,基于 Git 中文件的内容或目录结 构计算出来。 SHA-1 哈希看起来是这样: 24b9da6552252987aa493b52f8696cd6d3b00373 Git 中使用这种哈希值的情况很多,你将经常看到这种哈希值。 实际上,Git 数据库中保存的信息都是以文件内容的哈希值来索引,而不是文件名。 Git 一般只添加数据 你执行的 GitHub 上 的是最新版本,但 kernel.org 上包含有文件下载签名,如果你想验证下载正 确性的话会用到。 接着,编译并安装: $ tar -zxf git-2.8.0.tar.gz $ cd git-2.8.0 $ make configure $ ./configure --prefix=/usr $ make all doc info $ sudo make install install-doc 来控制它,那么首先 需要进入该项目目录中。 如果你还没这样做过,那么不同系统上的做法有些 不同: 在 Linux 上: $ cd /home/user/my_project 在 macOS 上: $ cd /Users/user/my_project 在 Windows 上: $ cd /c/user/my_project 之后执行: $ git init 该命令将创建一个名为 .git 的子目录,这个子目录含有你初始化的0 码力 | 670 页 | 13.59 MB | 1 年前3
 BlenderVR User Manual
Release 0.1SVN Tortoise (Windows only). To check which samples are available visit the Samples Repository. $ cd $INSTALL_DIR $ mkdir -p samples $ svn checkout https://github.com/BlenderVR/samples/trunk/basic/basic your terminal. If you are in Windows we recommend you to use Power Shell or similar. On OSX/Linux: $ cd $INSTALL_DIR $ pip3 install virtualenv $ pyvenv venv $ source venv/bin/activate $ pip3 install -r source/requirements Linux: If pyvenv command fails due to mising ensurepip module, try this script . On Windows: $ cd $INSTALL_DIR $ pip3 install virtualenv $ virtualenv venv $ .\venv\Scripts\activate $ pip3 install -r0 码力 | 56 页 | 860.89 KB | 1 年前3 BlenderVR User Manual
Release 0.1SVN Tortoise (Windows only). To check which samples are available visit the Samples Repository. $ cd $INSTALL_DIR $ mkdir -p samples $ svn checkout https://github.com/BlenderVR/samples/trunk/basic/basic your terminal. If you are in Windows we recommend you to use Power Shell or similar. On OSX/Linux: $ cd $INSTALL_DIR $ pip3 install virtualenv $ pyvenv venv $ source venv/bin/activate $ pip3 install -r source/requirements Linux: If pyvenv command fails due to mising ensurepip module, try this script . On Windows: $ cd $INSTALL_DIR $ pip3 install virtualenv $ virtualenv venv $ .\venv\Scripts\activate $ pip3 install -r0 码力 | 56 页 | 860.89 KB | 1 年前3
 BlenderVR User Manual
Release 0.1samples are available visit the Samples Repository [https://github.com/BlenderVR/samples.git]. $ cd $INSTALL_DIR $ mkdir -p samples $ svn checkout https://github.com/BlenderVR/samples/trunk/basic/basic Power Shell [https://technet.microsoft.com/en-us/scriptcenter/default] or similar. On OSX/Linux: $ cd $INSTALL_DIR $ pip3 install virtualenv $ pyvenv venv $ source venv/bin/activate $ pip3 install -r module, try this script [https://gist.github.com/uranusjr/d03a49767c7c307be5ed] . On Windows: $ cd $INSTALL_DIR $ pip3 install virtualenv $ virtualenv venv $ .\venv\Scripts\activate $ pip3 install -r0 码力 | 75 页 | 861.11 KB | 1 年前3 BlenderVR User Manual
Release 0.1samples are available visit the Samples Repository [https://github.com/BlenderVR/samples.git]. $ cd $INSTALL_DIR $ mkdir -p samples $ svn checkout https://github.com/BlenderVR/samples/trunk/basic/basic Power Shell [https://technet.microsoft.com/en-us/scriptcenter/default] or similar. On OSX/Linux: $ cd $INSTALL_DIR $ pip3 install virtualenv $ pyvenv venv $ source venv/bin/activate $ pip3 install -r module, try this script [https://gist.github.com/uranusjr/d03a49767c7c307be5ed] . On Windows: $ cd $INSTALL_DIR $ pip3 install virtualenv $ virtualenv venv $ .\venv\Scripts\activate $ pip3 install -r0 码力 | 75 页 | 861.11 KB | 1 年前3
 Kicad 5.1 Pluginslet’s create a project directory and the FindPackage script: mkdir demo && cd demo export DEMO_ROOT=${PWD} mkdir CMakeModules && cd CMakeModules cat > FindKICAD.cmake << _EOF find_path( KICAD_INCLUDE_DIR To configure and build the tutorial code we will use CMake and create a CMakeLists.txt script file: cd ${DEMO_ROOT} cat > CMakeLists.txt << _EOF # declare the name of the project project( PLUGIN_DEMO ) dependencies other than the compiler defaults. We start by creating a source directory: cd ${DEMO_ROOT} mkdir src && cd src export DEMO_SRC=${PWD} Now we create the plugin source itself: s3d_plugin_demo10 码力 | 48 页 | 44.28 KB | 1 年前3 Kicad 5.1 Pluginslet’s create a project directory and the FindPackage script: mkdir demo && cd demo export DEMO_ROOT=${PWD} mkdir CMakeModules && cd CMakeModules cat > FindKICAD.cmake << _EOF find_path( KICAD_INCLUDE_DIR To configure and build the tutorial code we will use CMake and create a CMakeLists.txt script file: cd ${DEMO_ROOT} cat > CMakeLists.txt << _EOF # declare the name of the project project( PLUGIN_DEMO ) dependencies other than the compiler defaults. We start by creating a source directory: cd ${DEMO_ROOT} mkdir src && cd src export DEMO_SRC=${PWD} Now we create the plugin source itself: s3d_plugin_demo10 码力 | 48 页 | 44.28 KB | 1 年前3
 Kicad 4.0 Pluginslet’s create a project directory and the FindPackage script: mkdir demo && cd demo export DEMO_ROOT=${PWD} mkdir CMakeModules && cd CMakeModules cat > FindKICAD.cmake << _EOF find_path( KICAD_INCLUDE_DIR To configure and build the tutorial code we will use CMake and create a CMakeLists.txt script file: cd ${DEMO_ROOT} cat > CMakeLists.txt << _EOF # declare the name of the project project( PLUGIN_DEMO ) dependencies other than the compiler defaults. We start by creating a source directory: cd ${DEMO_ROOT} mkdir src && cd src export DEMO_SRC=${PWD} Now we create the plugin source itself: s3d_plugin_demo10 码力 | 48 页 | 66.10 KB | 1 年前3 Kicad 4.0 Pluginslet’s create a project directory and the FindPackage script: mkdir demo && cd demo export DEMO_ROOT=${PWD} mkdir CMakeModules && cd CMakeModules cat > FindKICAD.cmake << _EOF find_path( KICAD_INCLUDE_DIR To configure and build the tutorial code we will use CMake and create a CMakeLists.txt script file: cd ${DEMO_ROOT} cat > CMakeLists.txt << _EOF # declare the name of the project project( PLUGIN_DEMO ) dependencies other than the compiler defaults. We start by creating a source directory: cd ${DEMO_ROOT} mkdir src && cd src export DEMO_SRC=${PWD} Now we create the plugin source itself: s3d_plugin_demo10 码力 | 48 页 | 66.10 KB | 1 年前3
共 394 条
- 1
- 2
- 3
- 4
- 5
- 6
- 40














 
 