Using stdint.h types and standard C file functions

zzMcGee commented 7 months ago

Suggestions so your wonderful utility also works on Windows/Visual Studio compiler:

Use standard C file functions fopen()/fclose()/fread() instead POSIX open()/close()/read().
Update to use stdint.h uint16_t/uint32_t instead of u_int16_t/u_int32_t
If windows compiler #if defined(MSC_VER) then include winsock2.h; otherwise, include arpa/inet.h and unistd.h.

Suggestion to avoid stack overflow:

For large arrays (e.g., "hcodeIE/hcodeIO/hcodeQE/hcodeQO/BRCn/THIDXn" in packet_decode.c and "tablo" in read_file.c) put them in global (.data/.bss) section instead of allocating on stack, e.g., : (suggested update) static unsigned char tablo[65536]; vs. (original) unsigned char tablo[65536];

Thanks!

jmfriedt commented 7 months ago

I am glad you are enjoying this tool. I do not have access to a proprietary operating system or compiler to check if the updates are functional, but please let me know if commit 956d94e matches your expectations. At least with GNU/Linux I do not see a change in behavior. Thanks.

bigleaffrog commented 1 month ago

Dear Professor,

I would like to study your code, but my working environment is Windows. How should I install your code? It would be best if I could do it in Visual Studio.

I look forward to your reply. Wishing you a pleasant day!

Best regards, Leaf Frog

jmfriedt commented 1 month ago

Some of my students have success running GNU/Linux binaries on WSL2 on the latest releases of MS-Windows, so I believe this would be the best solution. I have no idea how to run or use Visual Studio. Otherwise cygwin https://www.cygwin.com/packages/package_list.html seems to have a gcc and make packages so these might be enough to compile MS-Windows binaries.

jmfriedt / sentinel1_level0

Using stdint.h types and standard C file functions #7