I want to embed the EXIP library in my existing Windows-based (Visual C++) software. I understand that the present version of EXIP (v0.5.3) supports build only with GCC via the Makefile. However, I need to build the solution in Visual Studio in one of the two following ways:
1. Either as a library, which could then be referenced/linked with in the existing software.
2. Build the source of EXIP as a part of my existing software (EXIP source + Encoder example source + existing software).
Query:
I would like to understand the feasibility of compiling the EXIP source in Windows/Visual Studio environment. I plan to create the build environment for EXIP ver 0.5.3, by creating a new project (in Visual Studio) and adding the source/header files, and subsequently building the project in one of the two ways as mentioned above.
I would like to understand if this approach is feasible from the following perspectives:
Does the EXIP source have specific dependencies with Linux/GCC headers, which would not be available in Windows/Visual Studio environment?
a. In case there are dependencies, could you please share the respective dependencies and solutions to overcome/workaround the dependencies as well?
After having built the EXIP source successfully in Windows/Visual Studio (porting) I am expecting that the behavior of the algorithm would be identical to that in Linux/GCC. Is my expectation reasonable and valid? In case there would be any challenges, please share them with me.
After creating the build environment in Visual Studio and successfully building/testing the EXIP source, I would also like to contribute back to the project by sharing the Visual Studio build environment for EXIP v0.5.3. Please let me know how I could do the same.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Background & Objective:
I want to embed the EXIP library in my existing Windows-based (Visual C++) software. I understand that the present version of EXIP (v0.5.3) supports build only with GCC via the Makefile. However, I need to build the solution in Visual Studio in one of the two following ways:
1. Either as a library, which could then be referenced/linked with in the existing software.
2. Build the source of EXIP as a part of my existing software (EXIP source + Encoder example source + existing software).
Query:
I would like to understand the feasibility of compiling the EXIP source in Windows/Visual Studio environment. I plan to create the build environment for EXIP ver 0.5.3, by creating a new project (in Visual Studio) and adding the source/header files, and subsequently building the project in one of the two ways as mentioned above.
I would like to understand if this approach is feasible from the following perspectives:
Does the EXIP source have specific dependencies with Linux/GCC headers, which would not be available in Windows/Visual Studio environment?
a. In case there are dependencies, could you please share the respective dependencies and solutions to overcome/workaround the dependencies as well?
After having built the EXIP source successfully in Windows/Visual Studio (porting) I am expecting that the behavior of the algorithm would be identical to that in Linux/GCC. Is my expectation reasonable and valid? In case there would be any challenges, please share them with me.
After creating the build environment in Visual Studio and successfully building/testing the EXIP source, I would also like to contribute back to the project by sharing the Visual Studio build environment for EXIP v0.5.3. Please let me know how I could do the same.