README.developer: put items about Windows together.

Move the item about MinGW-w64 up after the earlier item about Windows
portability in general.
This commit is contained in:
Guy Harris 2021-11-01 13:38:36 -07:00
parent 4ff22025e8
commit 1cf1684504
1 changed files with 4 additions and 4 deletions

View File

@ -426,10 +426,6 @@ platform-dependent implementations and platform-independent APIs, such
as the routines in epan/filesystem.c, allowing the code that calls it to as the routines in epan/filesystem.c, allowing the code that calls it to
be written portably without #ifdefs. be written portably without #ifdefs.
Wireshark uses Libgcrypt as general-purpose crypto library. To use it from
your dissector, do not include gcrypt.h directly, but use the wrapper file
wsutil/wsgcrypt.h instead.
We support building on Windows using MinGW-w64 (experimental) so be mindful We support building on Windows using MinGW-w64 (experimental) so be mindful
of the difference between an #ifdef on _WIN32 and _MSC_VER. The first tests of the difference between an #ifdef on _WIN32 and _MSC_VER. The first tests
if the platform is some version of Windows and also applies to MinGW. The if the platform is some version of Windows and also applies to MinGW. The
@ -440,6 +436,10 @@ a MinGW toolchain, including MinGW-w64. The same concern applies to CMake
code. Depending on the particular situation you may need to use if(WIN32) or code. Depending on the particular situation you may need to use if(WIN32) or
if(MSVC) or if(MINGW). if(MSVC) or if(MINGW).
Wireshark uses Libgcrypt as general-purpose crypto library. To use it from
your dissector, do not include gcrypt.h directly, but use the wrapper file
wsutil/wsgcrypt.h instead.
2. String handling 2. String handling
Do not use functions such as strcat() or strcpy(). Do not use functions such as strcat() or strcpy().