microsoft / windows-rust-driver-samples Goto Github PK

View Code? Open in Web Editor NEW

199.0 14.0 16.0 74 KB

Rust port of the official Windows Driver Samples on Github. Leverages windows-drivers-rs

Home Page: https://github.com/microsoft/windows-drivers-rs

License: Apache License 2.0

Rust 100.00%

drivers rust samples windows

windows-rust-driver-samples's Introduction

Rust Driver Samples

This is a Rust port of the driver samples from the original Windows Driver Samples on Github.

The repository provides examples and best practices for Windows driver development in Rust using crates from windows-drivers-rs.

Getting Started

Pre-requisites

Required

Set up EWDK Build Environment
- Easy install option:
  - Install the latest version from link
    - https://learn.microsoft.com/en-us/legal/windows/hardware/enterprise-wdk-license-2022
  - Expand the ISO image to c:\ewdk
  - Start Environment by running in command prompt:
    - c:\ewdk\LaunchBuildEnv.cmd
Install Clang
- Easy install option:
  - winget install LLVM.LLVM
Install Rust
- Easy install option for x64 systems:

Invoke-RestMethod -Uri "https://static.rust-lang.org/rustup/dist/x86_64-pc-windows-msvc/rustup-init.exe" -OutFile "$env:USERPROFILE\Downloads\rustup-init.exe"
& "$env:USERPROFILE\Downloads\rustup-init.exe" -y

Rust Setup

Run the following commands after setting up Rust.

cargo install cargo-make --no-default-features --features tls-native

Note on arm64: ARM64 support for ring is not released yet, so TLS features must be disabled until arm64 is officially supported by ring (probably in 0.17.0 release)

Optional

These are not-required, but may make it easier to work in a rust environment:

cargo install cargo-expand cargo-edit cargo-workspaces

Documentation

cargo doc --document-private-items --open

Build and Test

Build

From an EWDK development command prompt, run:

cargo make

If build is successful, this will stamp the INF and create a CAT file placed with driver binary and INF in Package folder.

Install

One Time PC Setup

If Bitlocker is enabled, suspend Bitlocker Example: manage-bde -protectors -disable C:
Turn off Secure Boot via your UEFI/BIOS Settings Example: shutdown -r -o -t 0 then pick Advanced -> UEFI Settings
If Bitlocker is enabled, suspend Bitlocker again Example: manage-bde -protectors -disable C:
Turn on test signing bcdedit /set testsigning on
Reboot shutdown -r -t 0
Copy the following to the DUT (Device Under Test: the computer you want to test the driver on):
1. The driver package folder located in the Cargo Output Directory. The Cargo Output Directory changes based off of build profile, target architecture, etc.
- Ex. <REPO_ROOT>\target\x86_64-pc-windows-msvc\debug\package, <REPO_ROOT>\target\x86_64-pc-windows-msvc\release\package, <REPO_ROOT>\target\aarch64-pc-windows-msvc\debug\package, <REPO_ROOT>\target\aarch64-pc-windows-msvc\release\package, <REPO_ROOT>\target\debug\package, <REPO_ROOT>\target\release\package
1. The version of devgen.exe from the WDK Developer Tools that matches the archtecture of your DUT
- Ex. C:\ewdk\Program Files\Windows Kits\10\Tools\10.0.22621.0\x64\devgen.exe
Install the Certificate on the DUT:
1. Double click the certificate
2. Click Install Certificate
3. Store Location: Local Machine -> Next
4. Place all certificates in the following Store -> Browse -> Trusted Root Certification Authorities -> Ok -> Next
5. Repeat 2-4 for Store -> Browse -> Trusted Publishers -> Ok -> Next
6. Finish
Install the driver from Admin Command Prompt:
1. In the package directory, run: pnputil.exe /add-driver echo_2.inf /install
Create a software device from Admin Command Prompt:
1. In the directory that devgen.exe was copied to, run: devgen.exe /add /hardwareid "root\ECHO_2"

Test

To capture prints:
- Start DebugView
  1. Enable Capture Kernel
  2. Enable Enable Verbose Kernel Output
- Alternatively, you can see prints in an active Windbg session.
  1. Attach WinDBG
  2. ed nt!Kd_DEFAULT_Mask 0xFFFFFFFF

Usage

The echo driver can be tested by using the included sample app.

cargo run --bin echoapp
- Send single write and read request synchronously
cargo run --bin echoapp -- -Async
- Send 100 reads and writes asynchronously

Exit the app anytime by pressing Ctrl-C

Windows driver development

Windows Driver Kit (WDK)

Take a look at the compilation of the new and changed driver-related content for Windows 11. Areas of improvement include camera, print, display, Near Field Communication (NFC), WLAN, Bluetooth, and more.

Find out what's new in the WDK

Windows Driver Frameworks

The Windows Driver Frameworks (WDF) are a set of libraries that make it simple to write high-quality device drivers.

WDF driver development guide

Samples

Use the samples in this repo to guide your Windows driver development. Whether you're just getting started or porting an older driver to the newest version of Windows, code samples are valuable guides on how to write drivers.

For information about important changes that need to be made to the WDK sample drivers before releasing device drivers based on the sample code, see the following topic:

From Sample Code to Production Driver - What to Change in the Samples

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

windows-rust-driver-samples's People

Contributors

Stargazers

Watchers

Forkers

mihaimaganu17 gmh5225 ellen2015 sfudally wmmc88 jpshivakavi panjiancai radk2 lj20240101 asafmah cuiyixin555 nated-msft legendsaber shabbirhasan1 vrn11

windows-rust-driver-samples's Issues

Digital Signature Problem

Hello

Everything seems to compile up just fine on my Windows 10 (x64) system but seem to run into a problem in Step 8 for "Install the Driver from the Admin Prompt"

D:\Win-rust-driver-samples\test\target\debug>pnputil.exe /add-driver echo_2.inf /install

Microsoft PnP Utility

Adding driver package:  echo_2.inf
Failed to add driver package: The third-party INF does not contain digital signature information.

Total driver packages:  1
Added driver packages:  0

It fails to add the driver with the as the INF does not contain digital signature information.

How to correct this?

Thanks as I think that everything is very close to working, now.

driver not loaded

Running a recent VM Ware Windows 11 VM to test the driver. Also using up-to-date SDKs.
I can build the driver and the sample application. I repeated all the steps mentioned in the repo. Yet, the driver doesn't seem to get loaded after installing it (which also installs it without any errors). What am I missing here? Since I am new to driver development, what else can I do to debug what's going on? Besides output from the installation and device creation stuff.

pnputil

PS C:\Users\guy\Desktop\New folder> pnputil.exe /add-driver .\echo_2.inf /install
Microsoft PnP Utility

Adding driver package:  echo_2.inf
Driver package added successfully.
Published Name:         oem8.inf
Driver package installed on device: SWD\DEVGEN\{5a3f9cb9-29c5-4349-badd-48ba5a0c1477}

Total driver packages:  1
Added driver packages:  1

devgen

PS C:\Users\guy\Desktop> .\devgen.exe /add /hardwareid "root\ECHO_2"
Microsoft Device Generator

Device successfully created. Device Instance ID: SWD\DEVGEN\{5a3f9cb9-29c5-4349-badd-48ba5a0c1477}

The test app only returns:

Error: "Error: No active device interfaces found.  Is the sample driver loaded?"

And yes i tried turning my pc off and on again multiple times :D

error

**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.7.4
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'

C:\Program Files\Microsoft Visual Studio\2022\Enterprise>cd /d D:\code\rust\code\windows\Windows-rust-driver-samples

D:\code\rust\code\windows\Windows-rust-driver-samples>cargo build
   Compiling wdk-sys v0.1.0
error: failed to run custom build command for `wdk-sys v0.1.0`

Caused by:
  process didn't exit successfully: `D:\code\rust\code\windows\Windows-rust-driver-samples\target\debug\build\wdk-sys-109708047c4dbb69\build-script-build` (exit code: 101)
  --- stderr
  thread 'main' panicked at 'WDKContentRoot should be able to be detected. Ensure that the WDK is installed, or that the environment setup scripts in the eWDK have been run.', C:\Users\Administrator\.cargo\registry\src\index.crates.io-6f17d22bba15001f\wdk-build-0.1.0\src\lib.rs:111:64
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

D:\code\rust\code\windows\Windows-rust-driver-samples>

is there code for hard driver ?

thanks

Installing the sample driver causes an error - invalid parameter for service or function

The error on the device:

Windows cannot initialize the device driver for this hardware. (Code 37)

An invalid parameter was passed to a service or function.

There is this event:

Device ROOT\SAMPLE\0000 had a problem starting.

Driver Name: oem24.inf
Class Guid: {78a1c341-4539-11d3-b88d-00c04fad5171}
Service: ECHO_2
Lower Filters: 
Upper Filters: 
Problem: 0x25
Problem Status: 0xC000000D

System:
-Windows 10 VM
-DriverCertificate has been installed on the machine
-Did all the steps - including driver signing.

Issue with fresh "cargo make"

Hi!

I've tried to compile the example code on Windows 11 ARM, but it fails with the following error message:

As user:

**********************************************************************
** Enterprise Windows Driver Kit (WDK) build environment
** Version ni_release_svc_prod1.22621.2428
**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.1.5
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************
C:\Users\x\repos\Windows-rust-driver-samples>cargo make
[cargo-make] INFO - cargo make 0.37.10
[cargo-make] INFO - Execute Command: "rust-script" "target\\_cargo_make_temp\\persisted_scripts\\D4060E7434B3779E78A683E8BA00D06A5D08BE8C95BC432359E22F06CB30EF1C.rs"
[cargo-make] INFO - Calling cargo metadata to extract project info
[cargo-make] INFO - Cargo metadata done
[cargo-make] INFO - Build File: Makefile.toml
[cargo-make] INFO - Task: default
[cargo-make] INFO - Profile: development
[cargo-make] INFO - Running Task: legacy-migration
[cargo-make] INFO - Running Task: workspace
C:\Users\x\repos\Windows-rust-driver-samples
[cargo-make][1] INFO - Execute Command: "rust-script" "C:\\Users\\x\\repos\\Windows-rust-driver-samples\\target\\_cargo_make_temp\\persisted_scripts\\D4060E7434B3779E78A683E8BA00D06A5D08BE8C95BC432359E22F06CB30EF1C.rs"
[cargo-make][1] INFO - Calling cargo metadata to extract project info
[cargo-make][1] INFO - Cargo metadata done
[cargo-make][1] INFO - Project: echoapp
[cargo-make][1] INFO - Build File: Makefile.toml
[cargo-make][1] INFO - Task: default
[cargo-make][1] INFO - Profile: development
[cargo-make][1] INFO - Skipping Task: legacy-migration
[cargo-make][1] INFO - Running Task: build
[cargo-make][1] INFO - Execute Command: "cargo" "build"
    Finished dev [unoptimized + debuginfo] target(s) in 0.02s
echoapp does not contain a package.metadata.wdk section in its manifest. Skipping package-driver task.
[cargo-make][1] INFO - Skipping Task: package-driver-flow
[cargo-make][1] INFO - Running Task: default
[cargo-make][1] INFO - Build Done in 1.14 seconds.
[cargo-make][1] INFO - Execute Command: "rust-script" "C:\\Users\\x\\repos\\Windows-rust-driver-samples\\target\\_cargo_make_temp\\persisted_scripts\\D4060E7434B3779E78A683E8BA00D06A5D08BE8C95BC432359E22F06CB30EF1C.rs"
[cargo-make][1] INFO - Calling cargo metadata to extract project info
[cargo-make][1] INFO - Cargo metadata done
[cargo-make][1] INFO - Project: echo-2
[cargo-make][1] INFO - Build File: Makefile.toml
[cargo-make][1] INFO - Task: default
[cargo-make][1] INFO - Profile: development
[cargo-make][1] INFO - Skipping Task: legacy-migration
[cargo-make][1] INFO - Running Task: build
[cargo-make][1] INFO - Execute Command: "cargo" "build"
   Compiling wdk-sys v0.2.0
memory allocation of 26306674688 bytes failed132: wdk-sys(build)
[cargo-make][1] ERROR - Error while executing command, exit code: -1073740791
[cargo-make][1] WARN - Build Failed.
[cargo-make] ERROR - Error while running duckscript: Source: Unknown Line: 8 - Error while executing command, exit code: 1
[cargo-make] WARN - Build Failed.

I guessed that A required privilege is not held by the client. may mean that administrator rights are needed, to I re-ran it in an admin prompt.

As admin user:

**********************************************************************
** Enterprise Windows Driver Kit (WDK) build environment
** Version ni_release_svc_prod1.22621.2428
**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.1.5
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************

C:\Users\x\repos\Windows-rust-driver-samples>cargo make
[cargo-make] INFO - cargo make 0.37.10
[cargo-make] INFO - Execute Command: "rust-script" "target\\_cargo_make_temp\\persisted_scripts\\D4060E7434B3779E78A683E8BA00D06A5D08BE8C95BC432359E22F06CB30EF1C.rs"
[cargo-make] INFO - Calling cargo metadata to extract project info
[cargo-make] INFO - Cargo metadata done
[cargo-make] INFO - Build File: Makefile.toml
[cargo-make] INFO - Task: default
[cargo-make] INFO - Profile: development
[cargo-make] INFO - Running Task: legacy-migration
[cargo-make] INFO - Running Task: workspace
C:\Users\x\repos\Windows-rust-driver-samples
[cargo-make][1] INFO - Execute Command: "rust-script" "C:\\Users\\x\\repos\\Windows-rust-driver-samples\\target\\_cargo_make_temp\\persisted_scripts\\D4060E7434B3779E78A683E8BA00D06A5D08BE8C95BC432359E22F06CB30EF1C.rs"
[cargo-make][1] INFO - Calling cargo metadata to extract project info
[cargo-make][1] INFO - Cargo metadata done
[cargo-make][1] INFO - Project: echoapp
[cargo-make][1] INFO - Build File: Makefile.toml
[cargo-make][1] INFO - Task: default
[cargo-make][1] INFO - Profile: development
[cargo-make][1] INFO - Skipping Task: legacy-migration
[cargo-make][1] INFO - Running Task: build
[cargo-make][1] INFO - Execute Command: "cargo" "build"
   Compiling proc-macro2 v1.0.78
   Compiling unicode-ident v1.0.12
   Compiling windows_aarch64_msvc v0.52.0
   Compiling once_cell v1.19.0
   Compiling windows-targets v0.52.0
   Compiling windows-sys v0.52.0
   Compiling quote v1.0.35
   Compiling syn v2.0.48
   Compiling uuid-macro-internal v1.7.0
   Compiling uuid v1.7.0
   Compiling echoapp v0.1.0 (C:\Users\x\repos\Windows-rust-driver-samples\general\echo\kmdf\exe)
    Finished dev [unoptimized + debuginfo] target(s) in 5.53s
echoapp does not contain a package.metadata.wdk section in its manifest. Skipping package-driver task.
[cargo-make][1] INFO - Skipping Task: package-driver-flow
[cargo-make][1] INFO - Running Task: default
[cargo-make][1] INFO - Build Done in 6.56 seconds.
[cargo-make][1] INFO - Execute Command: "rust-script" "C:\\Users\\x\\repos\\Windows-rust-driver-samples\\target\\_cargo_make_temp\\persisted_scripts\\D4060E7434B3779E78A683E8BA00D06A5D08BE8C95BC432359E22F06CB30EF1C.rs"
[cargo-make][1] INFO - Calling cargo metadata to extract project info
[cargo-make][1] INFO - Cargo metadata done
[cargo-make][1] INFO - Project: echo-2
[cargo-make][1] INFO - Build File: Makefile.toml
[cargo-make][1] INFO - Task: default
[cargo-make][1] INFO - Profile: development
[cargo-make][1] INFO - Skipping Task: legacy-migration
[cargo-make][1] INFO - Running Task: build
[cargo-make][1] INFO - Execute Command: "cargo" "build"
   Compiling proc-macro2 v1.0.78
   Compiling windows_aarch64_msvc v0.48.5
   Compiling windows_aarch64_msvc v0.52.0
   Compiling once_cell v1.19.0
   Compiling windows-targets v0.52.0
   Compiling windows-sys v0.52.0
   Compiling serde v1.0.196
   Compiling anstyle v1.0.6
...
   Compiling wdk-panic v0.2.0
   Compiling wdk v0.2.0
   Compiling echo-2 v0.1.0 (C:\Users\x\repos\Windows-rust-driver-samples\general\echo\kmdf\driver\DriverSync)
   Compiling wdk-sys v0.2.0
memory allocation of 26306674688 bytes failed132: wdk-sys(build)
[cargo-make][1] ERROR - Error while executing command, exit code: -1073740791
[cargo-make][1] WARN - Build Failed.
[cargo-make] ERROR - Error while running duckscript: Source: Unknown Line: 8 - Error while executing command, exit code: 1
[cargo-make] WARN - Build Failed.

Any ideas what went wrong?

error: linking with `link.exe` failed: exit code: 1120

D:\code\rust\code\windows\Windows-rust-driver-samples\general\echo\kmdf\driver\DriverSync>cargo +nightly make
[cargo-make] INFO - cargo make 0.37.1
[cargo-make] INFO - Calling cargo metadata to extract project info
[cargo-make] INFO - Cargo metadata done
[cargo-make] INFO - Project: echo-2
[cargo-make] INFO - Build File: Makefile.toml
[cargo-make] INFO - Task: default
[cargo-make] INFO - Profile: development
[cargo-make] INFO - Running Task: legacy-migration
[cargo-make] INFO - Execute Command: "cargo" "fmt"
[cargo-make] INFO - Skipping Task: format-toml-conditioned-flow
[cargo-make] INFO - Execute Command: "cargo" "build" "--all-features"
   Compiling proc-macro2 v1.0.67
   Compiling unicode-ident v1.0.12
   Compiling windows_x86_64_msvc v0.48.5
   Compiling winapi v0.3.9
   Compiling once_cell v1.18.0
   Compiling glob v0.3.1
   Compiling rustversion v1.0.14
   Compiling lazy_static v1.4.0
   Compiling libc v0.2.148
   Compiling rustix v0.38.13
   Compiling prettyplease v0.2.15
   Compiling clang-sys v1.6.1
   Compiling bitflags v2.4.0
   Compiling regex-syntax v0.7.5
   Compiling log v0.4.20
   Compiling windows-targets v0.48.5
   Compiling windows-sys v0.48.0
   Compiling memchr v2.6.3
   Compiling minimal-lexical v0.2.1
   Compiling serde v1.0.188
   Compiling quote v1.0.33
   Compiling syn v2.0.33
   Compiling nom v7.1.3
   Compiling thiserror v1.0.48
   Compiling bindgen v0.68.1
   Compiling libloading v0.7.4
   Compiling either v1.9.0
   Compiling serde_json v1.0.107
   Compiling wdk-build v0.1.0
   Compiling windows-core v0.51.1
   Compiling itoa v1.0.9
   Compiling regex-automata v0.3.8
   Compiling rustc-hash v1.1.0
   Compiling shlex v1.2.0
   Compiling errno v0.3.3
   Compiling home v0.5.5
   Compiling cexpr v0.6.0
   Compiling which v4.4.2
   Compiling lazycell v1.3.0
   Compiling ryu v1.0.15
   Compiling peeking_take_while v0.1.2
   Compiling windows v0.51.1
   Compiling cfg-if v1.0.0
   Compiling tracing-core v0.1.31
   Compiling overload v0.1.1
   Compiling thread_local v1.1.7
   Compiling regex v1.9.5
   Compiling tracing-log v0.1.3
   Compiling nu-ansi-term v0.46.0
   Compiling sharded-slab v0.1.4
   Compiling smallvec v1.11.0
   Compiling spin v0.5.2
   Compiling paste v1.0.14
   Compiling tracing-subscriber v0.3.17
   Compiling wdk-panic v0.1.0
   Compiling serde_derive v1.0.188
   Compiling thiserror-impl v1.0.48
   Compiling wdk-macros v0.1.0
   Compiling wdk-sys v0.1.0
   Compiling wdk v0.1.0
   Compiling echo-2 v0.1.0 (D:\code\rust\code\windows\Windows-rust-driver-samples\general\echo\kmdf\driver\DriverSync)
   Compiling wdk-alloc v0.1.0
    Finished dev [unoptimized + debuginfo] target(s) in 3m 05s
[cargo-make] INFO - Execute Command: "cargo" "test" "--all-features"
   Compiling spin v0.5.2
   Compiling wdk-panic v0.1.0
   Compiling lazy_static v1.4.0
   Compiling wdk-sys v0.1.0
   Compiling wdk-alloc v0.1.0
   Compiling wdk v0.1.0
   Compiling echo-2 v0.1.0 (D:\code\rust\code\windows\Windows-rust-driver-samples\general\echo\kmdf\driver\DriverSync)
error: linking with `link.exe` failed: exit code: 1120
  |
  = note: "C:\\Program Files\\Microsoft Visual Studio\\2022\\Enterprise\\VC\\Tools\\MSVC\\14.37.32822\\bin\\HostX64\\x64\\link.exe" "/NOLOGO" "C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\rustcmf3ZsW\\symbols.o" "D:\\code\\rust\\code\\windows\\Windows-rust-driver-samples\\target\\debug\\deps\\echo_2-dfe775342f36be9b.test-4e25e9a00f55b6b4.test.23704e6cc03fe591-cgu.0.rcgu.o.rcgu.o" "/LIBPATH:D:\\code\\rust\\code\\windows\\Windows-rust-driver-samples\\target\\debug\\deps" "/LIBPATH:C:\\Program Files (x86)\\Windows Kits\\10\\Lib\\10.0.22621.0\\km\\x64" "/LIBPATH:C:\\Program Files (x86)\\Windows Kits\\10\\Lib\\wdf\\kmdf\\x64\\1.33" "/LIBPATH:C:\\Users\\Administrator\\.rustup\\toolchains\\nightly-x86_64-pc-windows-msvc\\lib\\rustlib\\x86_64-pc-windows-msvc\\lib" "C:\\Users\\Administrator\\.rustup\\toolchains\\nightly-x86_64-pc-windows-msvc\\lib\\rustlib\\x86_64-pc-windows-msvc\\lib\\libcompiler_builtins-6856e76ba99f7e60.rlib" "kernel32.lib" "kernel32.lib" "advapi32.lib" "bcrypt.lib" "kernel32.lib" "ntdll.lib" "userenv.lib" "ws2_32.lib" "kernel32.lib" "ws2_32.lib" "kernel32.lib" "msvcrt.lib" "BufferOverflowFastFailK.lib" "ntoskrnl.lib" "hal.lib" "wmilib.lib" "WdfLdr.lib" "WdfDriverEntry.lib" "/NXCOMPAT" "/LIBPATH:C:\\Users\\Administrator\\.rustup\\toolchains\\nightly-x86_64-pc-windows-msvc\\lib\\rustlib\\x86_64-pc-windows-msvc\\lib" "/OUT:D:\\code\\rust\\code\\windows\\Windows-rust-driver-samples\\target\\debug\\deps\\echo_2-dfe775342f36be9b.exe" "/OPT:REF,NOICF" "/DEBUG" "/NATVIS:C:\\Users\\Administrator\\.rustup\\toolchains\\nightly-x86_64-pc-windows-msvc\\lib\\rustlib\\etc\\intrinsic.natvis" "/NATVIS:C:\\Users\\Administrator\\.rustup\\toolchains\\nightly-x86_64-pc-windows-msvc\\lib\\rustlib\\etc\\liballoc.natvis" "/NATVIS:C:\\Users\\Administrator\\.rustup\\toolchains\\nightly-x86_64-pc-windows-msvc\\lib\\rustlib\\etc\\libcore.natvis" "/NATVIS:C:\\Users\\Administrator\\.rustup\\toolchains\\nightly-x86_64-pc-windows-msvc\\lib\\rustlib\\etc\\libstd.natvis" "/NXCOMPAT" "/DYNAMICBASE" "/MAP" "/MAPINFO:EXPORTS" "/OPT:REF,ICF" "/INTEGRITYCHECK" "/MANIFEST:NO" "/DRIVER" "/NODEFAULTLIB" "/SUBSYSTEM:NATIVE" "/KERNEL" "/ENTRY:FxDriverEntry"
  = note: msvcrt.lib(tlssup.obj) : warning LNK4257: 未对内核模式编译对象文件；映像可能不会运行
          msvcrt.lib(std_type_info_static.obj) : warning LNK4257: 未对内核模式编译对象文件；映像可能不会运行
          msvcrt.lib(delete_scalar_size.obj) : warning LNK4257: 未对内核模式编译对象文件；映像可能不会运行
          msvcrt.lib(delete_scalar.obj) : warning LNK4257: 未对内核模式编译对象文件；映像可能不会运行
          msvcrt.lib(gs_support.obj) : warning LNK4257: 未对内核模式编译对象文件；映像可能不会运行
          msvcrt.lib(guard_support.obj) : warning LNK4257: 未对内核模式编译对象文件；映像可能不会运行
          msvcrt.lib(gs_cookie.obj) : warning LNK4257: 未对内核模式编译对象文件；映像可能不会运行
          msvcrt.lib(loadcfg.obj) : warning LNK4257: 未对内核模式编译对象文件；映像可能不会运行
          echo_2-dfe775342f36be9b.test-4e25e9a00f55b6b4.test.23704e6cc03fe591-cgu.0.rcgu.o.rcgu.o : error LNK2019: 无法解析的外部符号 floor，函数 _ZN52_$LT$$u5b$f64$u5d$$u20$as$u20$test..stats..Stats$GT$9quartiles17h70ec751af0614305E 中引用了该符号
          echo_2-dfe775342f36be9b.test-4e25e9a00f55b6b4.test.23704e6cc03fe591-cgu.0.rcgu.o.rcgu.o : error LNK2019: 无法解析的外部符号 _CxxThrowException，函数 __rust_start_panic 中引用了该符号
          msvcrt.lib(delete_scalar.obj) : error LNK2019: 无法解析的外部符号 free，函数 "void __cdecl operator delete(void *)" (??3@YAXPEAX@Z) 中引用了该符号
          D:\code\rust\code\windows\Windows-rust-driver-samples\target\debug\deps\echo_2-dfe775342f36be9b.exe : fatal error LNK1120: 3 个无法解析的外部命令


error: could not compile `echo-2` (lib test) due to previous error
[cargo-make] ERROR - Error while executing command, exit code: 101
[cargo-make] WARN - Build Failed.

D:\code\rust\code\windows\Windows-rust-driver-samples\general\echo\kmdf\driver\DriverSync>