Mumps Solver for Visual Studio / Blog: Recent posts

Dear Mumps users,

today I will try to explain the differences between the static/dynamic libraries, linking of those and about the compiler options used in this project. The introduction to the libraries is based on my gained knowledge of them and can be missguided. Please check the world wide web for additional information.

Most of you knows about the static and dynamic libraries. The main difference between these two are, that the static library contains only compiled code from the selected source file(s) - it also may contains the compiled code from the linked libraries -, while the dynamic libraries always contains the compiled source code and code from the linked libraries. It is also necessary to know, that source code from static libraries is completly included in the final executable file - even multiple times if different part of a program calls same function -, which can lead to huge executables. This is not the case at dynamic libraries, but here is a different catch. The final program always uses one version of the dynamic library. But if the code compiled is dependable on two different versions of the library program won't work properly. The next two examples will demonstrate what I am saying. ... read more

Dear Mumps Users,

today's first thing to explain will be the testing procedures in the MumpsSolver solution. To execute the testing procedures, compiled executables should be called by "MumpsSolver.exe -test MUMPS_Tests.txt". The MumpsSolver.exe is the name of compiled executable and could differ in some projects. The pre-build and post-build events copy the necessary files (*.mtx and MUMPS_tests.txt) to the directory with a compiled executable. There are two different matricies (general and symmetric) and two different rigth hand side vector files (with one RHS vector and with four RHS vectors) used for testing which defines 8 different solution files (bear in mind the general matrix may be transposed).
The file MUMPS_Tests.txt determines which test type and which capability of the library during a single test will be performed. It looks like ... read more

Dear mumps users,

in this post I will try make a thorough description of a wrapper library VS solution. The solution is available in the code tab. If you want to download it, you can check it out with svn versioning system, or use the button download snapshot.

The solution consist of six projects:
- static wrapper library,
- dynamic wrapper library,
- c++ test program with a static linking,
- c++ test program with a dynamic linking,
- c test program with a static linking,
- c test program with a dynamic linking.... read more

Dear mumps users,

this post will be intended for a more in-depth description of the application for creating visual studio projects (MumpsforWindows.exe).

Let's start with the description of the application MumpsForWindows.exe. It is a C# application, build with .NET 4 client framework and for x86 machines. I have tested it on Win7 Pro 64-bit machine and it works fine. But than again, I know what it should do and by which command, so it can contain bugs. If so, please contact me to repair them.... read more

Dear mumps users,

this post will be about initial commit of this project. I plan to fully describe the presented solution and to upgrade it. The additional WinForm to create visual studio mumps library projects is based on winmumps source code (https://sourceforge.net/projects/winmumps/). That is needed to be said.

In order to use this solution, download the solution to your computer along with MUMPS source code available at http://mumps.enseeiht.fr/. Then all you need to do is to pinpoint the directories (double-click on text box):
Mumps source code directory: where mumps source code unpacked is,
Mumps library Visual Studio projects: where visual studio solution with projects to compile mumps source,
Mumps library Visual studio output: where the mumps libraries will be outputed,
Mumps solver solution directory: where this project is,... read more