Finally, Visual Studio users should usually do everything in 64bit mode. By default Visual Studio is 32bit, both in its outputs and its own execution, so you have to explicitly
```shell
tell it to use 64bits. Since it's not the 1990s anymore you probably want to use 64bits. Do that with a cmake invocation like this:
source /opt/dtk/env.sh
```
```shell
### 编译安装
cmake .. -G"Visual Studio 14 2015 Win64"-Thost=x64
```
## Compiling your own C++ programs that use dlib
The examples folder has a [CMake tutorial](https://github.com/davisking/dlib/blob/master/examples/CMakeLists.txt) that tells you what to do. There are also additional instructions
#### 使用cmake编译
on the [dlib web site](http://dlib.net/compile.html).
```shell
```shell
vcpkg install dlib
mkdir build;cd build;
```
cmake .. -DCMAKE_CXX_COMPILER=/opt/dtk/bin/hipcc
## Compiling dlib Python API
Before you can run the Python example programs you must compile dlib. Type:
Type the following to compile and run the dlib unit test suite:
Type the following to compile and run the dlib unit test suite:
- 编译单元测试
```shell
```shell
cd dlib/test
cd dlib/test
mkdir build
mkdir build
cd build
cd build
cmake .. -DCMAKE_CXX_COMPILER=/opt/dtk/bin/hipcc
cmake .. -DCMAKE_CXX_COMPILER=/opt/dtk/bin/hipcc
cmake --build.-j16--config Release --verbose
cmake --build.-j16--config Release #--verbose
```
- 进行单元测试
./dtest --runall
```shell
./dtest -d--test_dnn
./dtest --runall# 全部测试
./dtest -d--test_rocblas# 测试单个测试单元
```
```
Note that on windows your compiler might put the test executable in a subfolder called `Release`. If that's the case then you have to go to that folder before running the test.
#### 编译 dlib Python API
This library is licensed under the Boost Software License, which can be found in [dlib/LICENSE.txt](https://github.com/davisking/dlib/blob/master/dlib/LICENSE.txt). The long and
- 使用python安装
short of the license is that you can use dlib however you like, even in closed source commercial software.
This research is based in part upon work supported by the Office of the Director of National Intelligence (ODNI), Intelligence Advanced Research Projects Activity (IARPA) under
- 使用python编译whl包
contract number 2014-14071600010. The views and conclusions contained herein are those of the authors and should not be interpreted as necessarily representing the official
policies or endorsements, either expressed or implied, of ODNI, IARPA, or the U.S. Government.
Finally, Visual Studio users should usually do everything in 64bit mode. By default Visual Studio is 32bit, both in its outputs and its own execution, so you have to explicitly
tell it to use 64bits. Since it's not the 1990s anymore you probably want to use 64bits. Do that with a cmake invocation like this:
```shell
cmake .. -G"Visual Studio 14 2015 Win64"-Thost=x64
```
## Compiling your own C++ programs that use dlib
The examples folder has a [CMake tutorial](https://github.com/davisking/dlib/blob/master/examples/CMakeLists.txt) that tells you what to do. There are also additional instructions
on the [dlib web site](http://dlib.net/compile.html).
```shell
vcpkg install dlib
```
## Compiling dlib Python API
Before you can run the Python example programs you must compile dlib. Type:
Type the following to compile and run the dlib unit test suite:
```shell
cd dlib/test
mkdir build
cd build
cmake .. -DCMAKE_CXX_COMPILER=/opt/dtk/bin/hipcc
cmake --build.-j16--config Release --verbose
./dtest --runall
./dtest -d--test_dnn
```
Note that on windows your compiler might put the test executable in a subfolder called `Release`. If that's the case then you have to go to that folder before running the test.
This library is licensed under the Boost Software License, which can be found in [dlib/LICENSE.txt](https://github.com/davisking/dlib/blob/master/dlib/LICENSE.txt). The long and
short of the license is that you can use dlib however you like, even in closed source commercial software.
## dlib sponsors
This research is based in part upon work supported by the Office of the Director of National Intelligence (ODNI), Intelligence Advanced Research Projects Activity (IARPA) under
contract number 2014-14071600010. The views and conclusions contained herein are those of the authors and should not be interpreted as necessarily representing the official
policies or endorsements, either expressed or implied, of ODNI, IARPA, or the U.S. Government.
