Windows下适用的Unix-POSIX工具链及非跨平台C/C++库VS链接咨询

Hey there, let's tackle your two questions step by step, just like we would on Stack Overflow:

If you're working on Windows and need a Unix-POSIX compliant toolchain, here are the most reliable options, each tailored to different use cases:

• MinGW-w64: The go-to choice for most developers. It provides GCC/G++ toolchains that support both 32-bit and 64-bit Windows, while sticking closely to POSIX standards. You can pick between posix and win32 thread models—opt for posix if you need full Unix-like thread support. It generates native Windows executables/libraries without relying on a heavy compatibility layer.
• Cygwin: A full Unix-like environment for Windows, complete with a POSIX-compliant toolchain and system libraries. It’s great if you need to replicate a full Unix workflow, but programs compiled with Cygwin depend on cygwin1.dll, which adds a runtime dependency that might not be ideal for seamless Visual Studio integration.
• Windows Subsystem for Linux (WSL): Run a full Linux distribution directly within Windows, using its native GCC/Clang toolchains. Perfect for projects that heavily depend on Unix-specific features. You can cross-compile Windows-targeted libraries using mingw-w64 within WSL, then access the compiled files via the WSL file system (\\wsl$\<DistroName>).
• Clang/LLVM for Windows: A modern, POSIX-compliant toolchain that integrates smoothly with Visual Studio. It can generate Windows-native object files and libraries, and supports most Unix-POSIX features you’d need.

Unix-native libraries typically use Makefiles or autotools, so we need to adapt the build process to generate libraries compatible with Visual Studio (.lib for static libraries, .dll + .lib for dynamic libraries). Here’s how to do it with the most practical toolchains:

Using MinGW-w64 (Best for Direct VS Integration) #

1. Install MinGW-w64: Choose the posix thread model during installation, and make sure the bin directory is added to your system PATH.
2. Configure the Library: Navigate to the library’s source directory in Command Prompt or PowerShell. Run the configure script with a Windows target:

   ./configure --prefix=C:/path/to/install --host=x86_64-w64-mingw32
   

   To build static libraries only, add --enable-static --disable-shared; for dynamic libraries, use --enable-shared --disable-static. You may also need to add Windows-specific defines:

   CFLAGS="-DWIN32 -D_WIN32" CXXFLAGS="-DWIN32 -D_WIN32" ./configure --prefix=C:/path/to/install --host=x86_64-w64-mingw32
   

3. Compile and Install: Run make followed by make install. This will generate .a (static) or .dll + .dll.a (dynamic) libraries in your specified install directory.
4. Convert to VS-Compatible Format:
   • Static Libraries: Extract object files from the MinGW .a file, then repackage them into a VS .lib:

     ar x library.a
     lib /machine:x64 /out:library.lib *.o
     

   • Dynamic Libraries: Generate a .def file from the .dll, then create a VS-compatible import library:

     gendef library.dll
     lib /machine:x64 /def:library.def /out:library.lib
     

Using WSL to Cross-Compile #

1. Set Up WSL: Install a Linux distribution (e.g., Ubuntu) and install the cross-compilation toolchain:

   sudo apt update && sudo apt install gcc-mingw-w64-x86-64
   

2. Configure and Compile: In WSL, navigate to the library source and run:

   ./configure --prefix=/tmp/library-install --host=x86_64-w64-mingw32
   make && make install
   

3. Transfer to Windows: Copy the compiled libraries from /tmp/library-install/lib to your Windows machine via \\wsl$\Ubuntu\tmp\library-install (adjust the path for your distro), then convert them to VS format using the steps above.

CMake-Based Libraries (Easier Integration) #

If the library uses CMake, you can skip cross-compilation tools entirely:

1. Open Command Prompt, navigate to the library source, and run:

   cmake -G "Visual Studio 17 2022" -A x64 -DCMAKE_INSTALL_PREFIX=C:/path/to/install ..
   

2. Open the generated .sln file in Visual Studio, build the INSTALL target, and you’ll get VS-compatible libraries directly.

Key Tips for Success #

• Check for Prebuilt Ports: Many popular Unix libraries already have Windows ports or prebuilt VS-compatible binaries—search first to save time.
• Header Files: Copy the library’s header files to your Visual Studio project’s include directory, and add the path to your project’s C/C++ > General > Additional Include Directories.
• Linking in VS: Add the converted .lib file to your project’s Linker > Input > Additional Dependencies.

内容的提问来源于stack exchange，提问作者Francis Cugler