Thanks for taking a look at this. I use mpir 2.7.2. I will be glad to assist if I can.
I will try to help. But if you are using the project file from my blog (or the project file I attach in the end of this post) make sure you are in the "Release" build. Because the project file from my blog is set up only for the release build (procedure for setting debug and other build are similar though).
You can copy the headers and binaries in any location you want as long as you refer them properly in the project properties. As an example, let us use relative directory with respect to the project file (so everyone can use it). In the vs_giac directory create a directory ".\mpir\2.7.2\bin\release" and ".\mpir\2.7.2\inc". You can put the .lib and .dll files that you built in release configuration (mpir.dll and mpir.lib) in ".\mpir\2.7.2\bin\release" and you can put all the header files in ".\mpir\2.7.2\inc". The binaries should contain both mpir.dll and mpir.lib because microsoft mangles the method names in a different way than gcc and the lib is necessary when linking. Needless to say, the mpir.dll and mpir.lib should be compiled by the same compiler (i.e. we cannot use a .lib created by gcc and link with msvc).
After choosing an appropriate directory for binaries and headers (let us continue with my above example for directory names), you can set them up in the project properties. You refer the necessary files in project properties in the following way:
Choose Project Properties -> Configuration Properties -> C/C++ -> General
In the field "Additional Include Directories", make sure you add your header directory. For our example: "..\mpir\2.7.2\inc", .. because project file lies in .\vs2008 and we had to go to the root directory. Directory path can also be absolute (in my project file there is an mpfr directory line, perhaps delete this first, because it uses an environment variable specific of my system).
I wanted to created a dll file, apparently the project file in my blog is set to static build, you can set this up
"Configuration Properties -> General and change the filed "Configuration Type" to "Dynamic Library (.dll)"
Choose Project Properties -> Configuration Properties -> Linker -> Input
In the field "Additional Dependencies", make sure you add the full path of the .lib file of mpir. For our example: "..\mpir\2.7.2\bin\release\mpir.lib". File path can also be absolute.
As a side note:
I shared VS2008 project files but they are forward compatible to newer versions of Visual Studio. The project properties can also be changed manually changed in a text editor by editing the vcproj file (which is just an XML-based file format). For instance, "AdditionalIncludeDirectories" is in a "Tool" tag of the "Release" configuration. Similarly to "AdditionalDependencies" (where the .lib files need to be referred).
I also linked to mpfr in a similar fashion.
Please let me know if you could first compile the whole project. If not, please let me know of the errors you encounter.
Visual studio allows a (rather fast) compile of the whole project sources without going through unecessary linking. If that is successful, then we can proceed with the linking/building.
If it helps here
is a project file based on the above example (again make sure you work in Release configuration, VS always first switches to Debug configuration when you open the project file directly). You can replace the project file with the one you downloaded from the blog post. You can save the file from the browser because I cannot seem to set "force download" in this forum if the link is to a text based file.