I believe the Parallel/vecpack.cpp is some kind of "quick and dirty" solution, and it actually creates some kind of circular-dependency between shared libraries, I changed that in the windows version because such kind of binding cannot even pass the Visual Studio linker:-)
In the current esys windows version I combined the Model and Parallel into one big shared library ParallelModel because there seems to be a lot of circular-dependencies between the two libs and difficult to "entangle" them.
My two cents:
I believe the Parallel/ vecpack. cpp is some kind of "quick and dirty" solution, and it actually creates some kind of circular-dependency between shared libraries, I changed that in the windows version because such kind of binding cannot even pass the Visual Studio linker:-)
In the current esys windows version I combined the Model and Parallel into one big shared library ParallelModel because there seems to be a lot of circular- dependencies between the two libs and difficult to "entangle" them.
Feng