| 91 | | You may also encounter issues with target processor architecture being detected incorrectly, e.g. it being x64 on a x86 computer. A tool like [http://www.gtopala.com/ SIW] may be useful to verify this, especially in case you're building OpenVPN on a virtual machine. |
| | 91 | You may also encounter issues with an incorrect target processor architecture being used by the linker, especially if you're building OpenVPN on a virtual machine: |
| | 92 | |
| | 93 | {{{ |
| | 94 | fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64' |
| | 95 | }}} |
| | 96 | |
| | 97 | You can check the processor architecture with a tool like [http://www.gtopala.com/ SIW]. Once you know the proper target architecture you need to define it manually. If you have integrated OpenVPN to Visual Studio's graphical development environment, you can set in project properties. If you're just running the VC command-line tools, you can either append the correct architecture via [http://msdn.microsoft.com/en-us/library/y0zzbyt4%28v=VS.80%29.aspx linker options[ to the build command-line or define it in environment variables: |
| | 98 | |
| | 99 | * http://msdn.microsoft.com/en-us/library/wk97ab1b%28v=VS.80%29.aspx |
| | 100 | * http://msdn.microsoft.com/en-us/library/y0zzbyt4%28v=VS.80%29.aspx |
