Home Explore Help
Sign In
SoftwareDesign
/
csu3_am335x
8
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Branch: master
Branches Tags
csu3_am335x
/
EVSE
/
GPL
/
open-plc-utils-0.3
/
docbook
/
ch03s08.html

ch03s08.html 5.2 KB
Permalink History Raw

12345678910111213141516171819202122232425262728 
  1. <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Microsoft Solution Files</title><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><meta name="keywords" content="Intellon, Atheros, Qualcomm, HomePlug, powerline, communications, INT6000, INT6300, INT6400, AR7400, AR7420"><link rel="home" href="index.html" title="Qualcomm Atheros Open Powerline Toolkit"><link rel="up" href="ch03.html" title="Chapter 3.  Software"><link rel="prev" href="ch03s07.html" title="Compilation with Visual Studio .NET 2003"><link rel="next" href="ch03s09.html" title="Header Files"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">
    2. 

  2. 					Microsoft Solution Files
    3. 

  3. 					</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s07.html">Prev</a> </td><th width="60%" align="center">Chapter 3. 
    4. 

  4. 		Software 
    5. 

  5. 		</th><td width="20%" align="right"> <a accesskey="n" href="ch03s09.html">Next</a></td></tr></table><hr></div><div class="section" title="Microsoft Solution Files"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="software-solution-files"></a>
    6. 

  6. 					Microsoft Solution Files
    7. 

  7. 					</h2></div></div></div><p>
    8. 

  8. 				The Atheros <span class="application">Open Powerline Toolkit</span> includes a <span class="productname">Visual Studio .NET</span>™ solution file, <code class="filename">./VisualStudioNET/plc-utils.sln</code>,  that will build the toolkit on <span class="application">Windows XP SP2</span> from the Linux code base. The following information may be helpful to developers wanting to modify or extend the solution or port it to another version of Microsoft <span class="application">Visual Studio</span>:
    9. 

  9. 				</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
    10. 

  10. 						All projects are WIN32 Console Projects.
    11. 

  11. 						</p></li><li class="listitem"><p>
    12. 

  12. 						All projects have pre-compiled headers suppressed.
    13. 

  13. 						</p></li><li class="listitem"><p>
    14. 

  14. 						All projects should globally define preprocessor constant <code class="constant">MAKEFILE</code> to prevent proliferation of "already defined" link errors. See <a class="link" href="ch03s05.html" title="Stand-alone Compiling on GNU/Linux">Stand-alone Compiling on GNU/Linux</a> for an explanation of this constant.
    15. 

  15. 						</p></li><li class="listitem"><p>
    16. 

  16. 						All projects search folder <code class="filename">..\include</code> for <a class="ulink" href="stdint.h.html" target="_top">stdint.h</a> and <a class="ulink" href="unistd.h.html" target="_top">unistd.h</a> because Microsoft does not provide them. These header files are customized or abbreviated versions of their POSIX counterparts and should be used when originals are available.
    17. 

  17. 						</p></li><li class="listitem"><p>
    18. 

  18. 						Projects that perform raw Ethernet I/O should globally define preprocessor constant <code class="constant">WINPCAP</code> to enable appropriate code segments. Preprocessor error statements should (but may not) alert you if <code class="constant">WINPCAP</code> is not defined on <span class="productname">Windows</span>™ platforms.						</p></li><li class="listitem"><p>
    19. 

  19. 						Projects that perform raw Ethernet I/O search folder <code class="filename">..\include</code> for <span class="application">WinPcap</span> header files. These files are taken from the <span class="application">WinPcap</span> development package and may require periodic updates.  Header files <a class="ulink" href="pcap.h.html" target="_top">pcap.h</a>, <a class="ulink" href="pcap-stdinc.h.html" target="_top">pca-stdinc.h</a>, <a class="ulink" href="pcap-bpf.h.html" target="_top">pcap-bpf.h</a>,  <a class="ulink" href="ipv6_misc.h.html" target="_top">ipv6_misc.h</a> and <a class="ulink" href="bittypes.h.html" target="_top">bittypes.h</a> belong in folder <code class="filename">VisualStudioNET\include</code>. Other header files belong in folder <code class="filename">VisualStudioNET\include\pcap</code>.
    20. 

  20. 						</p></li><li class="listitem"><p>
    21. 

  21. 						Projects that perform raw Ethernet I/O should include folder <code class="filename">..\library</code> for core <span class="application">WinPcap</span> libraries.
    22. 

  22. 						</p></li><li class="listitem"><p>
    23. 

  23. 						Projects that perform raw Ethernet I/O should link to libraries <code class="filename">ws2_32.lib</code>,  <code class="filename">packet.lib</code> and <code class="filename">wpcap.lib</code>. The first library is the Microsoft <span class="application">Winsock2</span> library. The others are core <span class="application">WinPcap</span> libraries.
    24. 

  24. 						</p></li></ul></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s07.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s09.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">
    25. 

  25. 				Compilation with Visual Studio .NET 2003
    26. 

  26. 				 </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 
    27. 

  27. 				Header Files 
    28. 

  28. 				</td></tr></table></div></body></html>
    29.