zoukankan      html  css  js  c++  java
  • 关于windows mobile 驱动的编译(和wince 有什么差异?)

    Developing a Device Driver > Device Driver Development Concepts > Troubleshooting a Device Driver

    The following table shows descriptions and resolutions of problems you may encounter while building your driver.

    DescriptionResolution
    The build cannot find files you expected it to include. Ensure that the paths to the files are specified with the INCLUDES macro in the sources file.
    The C_DEFINES and RCOPTIONS macros in your sources file are not working. Use the CDEFINES and RDEFINES macros instead. The C_DEFINES and RCOPTIONS macros are only appropriate on a Windows-based desktop platform.
    You cannot compile Miniport.rc because the build cannot find Windows.h. Add the Windows.h file location to the RDEFINES macro in the sources file.
    Your object files are not building. Check the arguments you are passing to the build utilities. Ensure that you did not accidentally pass an empty argument when using a switch.
    The build cannot find a static library or you receive an error compiling your .def file because it cannot find Deffile.inc. Do not copy files to the location that the build utility is searching. Instead, run the Master Build tool (Cebuild.bat) from %_WINCEROOT% with the proper build environment settings. Running Cebuild.bat with the proper build environment settings generates the proper library and include directories for your build environment. Run Cebuild.bat from %_WINCEROOT% for every build configuration that you use to build your driver. For more information on Cebuild.bat, see Master Build Tool.
    You do not have a proper build environment for your driver. Create a project. Then, from the Build menu, choose Open Build Release Directory. This opens a command-line interface with the correct environment variables. You can then navigate to the directory where your driver resides, and then run the Build tool (Build.exe). For more information on Build.exe, see Build Tool.
    You do not want to use a project. Use the Windows CE Build Environment tool (Wince.bat). For more information on Wince.bat, see Windows CE Build Environment Tool.
    You want to put your driver into the %_FLATRELEASEDIR% directory of your project. From the command line, type set WINCEREL=1. The build utility will move your driver to the %_FLATRELEASEDIR% directory. If it is a debug build, the .dll, .pdb, and .map files move to the %_FLATRELEASEDIR% directory as well.
    You want to change your %_FLATRELEASEDIR% environment variable. Type set _FLATRELEASEDIR=MyFlatReleaseDir. MyFlatReleaseDir is a placeholder for the flat release directory you choose. For more information on changing environment variables, see SET (Command Processor) World Wide Web link.
    The compiler behaves as if some structures and macros in header files do not exist, even though they do. Ensure that WINCEOEM=1 is in your sources file. This is often set in a Sources.cmn file so you may run into this issue if you copy a driver from the Public directory and try to build it in another location.
    Sources files with NMAKE conditionals in them do not build properly. NMAKE understands conditionals, but Build.exe does not. Do not use conditionals in your sources files.
  • 相关阅读:
    JavaScript的alert()突然出现中文乱码
    对ie CSS hack总结和理解
    getBoundingClientRect()获取元素相对浏览器视窗的坐标值
    typeof和instanceof的区别
    转载:Dos命令行下,关闭占用80端口的进程 (~~~这个比较实用!)
    关于JS浮点数计算误差问题和二进制浮点数表示法的思考
    callee与caller,apply与call的区别和作用
    [Javascript权威指南笔记01]后自增/后自减运算符的副作用 和 运算符的结合性
    转载:关于zindex的那些事(~~~比较理论的描述 堆栈上下文)
    西游东去 (~~创意?创新?恶搞?不置可否,不过有点意思)
  • 原文地址:https://www.cnblogs.com/gooogleman/p/2036818.html
Copyright © 2011-2022 走看看