We present the procedure for obtaining our 64-bit shared library svdComplexDevice2.dll with MinGW GCC toolchain in Eclipse IDE for C/C++ project.

C++ 64-bit shared library svdComplexDEvice2.dll project with MinGW toolchain in Eclipse IDE

1. Launch Eclipse IDE for Java Developers.
   Select File menu, New, then Project.
   New Project panel appears:
   
   
   
   Select C/C++ then C/C++ Project. Click Next > button.
2. New C/C++ Project panel appears. Select C++ Managed Build.
   
   
   Click Next > button.
3. C++ Project panel appears.
   Provide Project name: svdComplexDevice2
   Select Shared Library then Empty Project.
   Select MinGW GCC in Toolchains.
   
   
   Click Finish button.
4. The project folder svdComplexDevice2 appears in Package Explorer of Eclipse.
   Right-click the project folder svdComplexDevice2.
   Select New, then File.
   Create New File panel appears.
   Provide the name for Header file: svdComplexDevice2.h
   Click Finish button.
   
   
   Click Finish button.
5. The empty header svdComplexDevice2.h appears in Package Explorer of Eclipse.
6. Copy and past svdComplexDevice2.h file into the newly created empty header file.
   Press Ctrl S to save svdComplexDevice2.h.
7. Similarly, create the empty file: svdComplexDevice2.cpp
   Copy and past svdComplexDevice2.cpp file into the newly created empty source file.
   Press Ctrl S to save svdComplexDevice2.cpp.
8. Similarly, create the empty file cusolver_utils.h
   Copy and paste the file cusolver_utils.h provided by Sijia Zhou into the newly created empty file.
   
   
   Press Ctrl S to save cusolver_utils.h.

   ---

9. Provide the path of include folder of CUDA to compiler:
   (Include folder contains header files)
   Right click svdComplexDevice2 project in Package Explorer then select Properties.
   Properties for svdComplexDevice2 panel appears.
   Click Settings in C/C++ Build.
   Click Includes for GCC C++ Compiler in Tool Settings tab.
   
   
   Click + symbol in top part of Include Path (/I).
10. Add directory path panel appears.
    Provide "${CUDA_INC_PATH}" for Directory.
    Directory must be enclosed in double quotes because this path contains space characters.
    
    
    Click OK button.
11. 
    
    Click Apply button.
12. Click Libraries for MinGW C++ Linker in Tool Settings tab.
    Provide libraries (cusolver, cublas, and cudart) and their folder location ("${CUDA_LIB_PATH_64}") to the linker.
    
    
    
    Library file names are provided without extension .lib and paths are enclosed in double quotes.
    Click Apply button.
13. Click Build Artifact tab.
    Delete lib in Output prefix.
    
    
    Click Apply and Close button.
    A message appears.
    Click Rebuild Index button.

    ---

14. Select Project menu then Build Project.
    
    
    64-bit svdComplexDevice2.dll file with 628 kbit size is generated in Debug folder.
    A message appears on the CDT Build Console.

Various references

1. Eclipse Foundation:
   It is essential that the installation path does not contain any spaces. Therefore, you cannot install MinGW-w64 in Program Files. We recommend to create a folder mingw-w64 on your system drive (e.g., C:\mingw).
2. Transmissin Zero: Build Windows DLLs with MinGW
3. Cygwin: Building and using DLLs
4. cplusplus: How to create and use DLL's
5. Stratman, Forex Factory: C++ dll tutorials using Eclipse
6. Capsis: A complete Java - C++ connection example with mingw/g++ and JNA under Windows 64 bits
7. Elias Volanakis, Eclipse Source: Shared libraries with Eclipse CDT and cygwin on Windows
   The compiler and linker will not find the header files / library unless you set the appropriate parameters. The compiler needs an include path (-I). The linker needs the library name (-l) and library search path (-L). These settings are scattered in two places in the project properties. Their location is not obvious for a first-time user.
8. Erich Styger, MCU on Eclipse: Eclipse build variables
9. Erich Styger, MCU on Eclipse: Debug vs. release?
10. OpenCV: Using OpenCV with Eclipse (plugin CDT)
11. Microsoft Learn Challenge: visual studio 2022: missing vcruntime.h