Lines Matching full:be
37 cross-compiling from Linux to MinGW/Windows. It should also be
46 wpa_supplicant can be built with Microsoft Visual C++ compiler. This
49 can also be used by creating a project that includes the files and
51 files are included in vs2005 subdirectory. This can be used as a
55 WinPcap development package is needed for the build and this can be
57 default nmake.mak expects this to be unpacked into C:\dev\WpdPack so
58 that Include and Lib directories are in this directory. The files can be
61 used, these Include and Lib directories need to be added to project
64 OpenSSL source package can be downloaded from
67 support will be included in the wpa_supplicant, OpenSSL needs to be
69 nmake.mak file expects OpenSSL to be installed into C:\dev\openssl, but
70 this directory can be modified by changing OPENSSLDIR variable in
73 If you do not need EAP-FAST support, you may also be able to use Win32
90 wpa_supplicant can be built for cygwin by installing the needed
97 CONFIG_DRIVER_NDIS. In addition, include directories may need to be
100 to be installed in compiler/linker default directories or their
101 location will need to be adding to .config when building
104 Othen than this, the build should be more or less identical to Linux
106 additional tool, win_if_list.exe, can be built by running "make
113 wpa_gui uses Qt application framework from Trolltech. It can be built
115 be used to build the binary in the Qt 4 Command Prompt:
129 should be applicable for most parts. In addition, there is another
130 version of wpa_supplicant, wpasvc.exe, which can be used as a Windows
135 be used (see wpa_supplicant.conf for more information).
138 will be needed when starting wpa_supplicant. Alternatively, the
139 adapter description can be used as the interface name which may be
141 format. win_if_list.exe can be used to find out the proper interface
160 "\Device\NPF_" prefix can be removed). In other words, wpa_supplicant
161 would be started with the following command:
166 needed). It can be left out if debugging information is not needed.
188 scanning; this allows APs with hidden SSIDs to be used)
191 wpa_cli.exe and wpa_gui.exe can be used to interact with the
196 interface. Anyway, this variable has to be included in the configuration
208 are for flags and object GUIDs, none of which should be required in this
219 (close to wide open, but you have to be a valid user on
228 users) -- this is *not* recommended, since named pipes can be attached
237 that can be used for principal names.
248 wpa_supplicant can be started as a Windows service by using wpasvc.exe
252 of a text file and command line parameters. In addition, it can be
253 registered as a service that can be started automatically or manually
262 This program can be run either as a normal command line application,
264 Service need to be registered with 'wpasvc.exe reg <full path to
265 wpasvc.exe>'. Alternatively, 'wpasvc.exe reg' can be used to register
267 can be started like any other Windows service (e.g., 'net start wpasvc')
268 or it can be configured to start automatically through the Services tool
269 in administrative tasks. The service can be unregistered with
274 be a long (half a minute or so) delay in starting up wpa_supplicant
279 Monitor Driver" can be configured to be started sooner by setting its
298 parameters in registry. It can also be imported to registry as a