This subforum is specifically to discuss packaging issues on different platforms (windows, mac, linux), and using different packaging systems (conda, etc...)
triplus wrote: ↑Sun Apr 26, 2020 6:38 pm
Sometimes on Linux such outcome signals a borked build, starting fresh usually helps.
Already tried 3 times. I guess it's a problem of VisualStudio setup on azure or it is related to the used compiler-package. The update I wanted to make is not very important. Only pinning netgen tightly to smesh to make sure smesh doesn't pull a newer version of netgen if we update netgen. I tried updating netgen recently (6.2.1808 ->6.2.2004) but netgen changed the interface which makes smesh incompatible...
I guess the question is why are we talking about a 32 bit network oriented library in the first place. I would say try what @sgrogan suggested if you have "settings dialog" at your disposal? Reading this:
Ensure that the build environment links to the Winsock Library file Ws2_32.lib.
This is therefore indeed what is likely missing. If the actual file is missing, then it is likely a part or some SDK, or you would need to define ws2_32.lib somewhere, as a dependency. Just guessing, as i have no experience with such toolchain.
DLL_HEADER extern int OCCGenerateMesh(OCCGeometry&, shared_ptr<Mesh>&, MeshingParameters&);
Whats the easiest way to align to the new interface? Does it make sense? Or should we use the python bindings they provide to interface the meshing functionality?
looo wrote: ↑Mon Apr 27, 2020 4:33 pm
Whats the easiest way to align to the new interface?
An option might be to add an implementation of OCCGenerateMesh to NETGENPlugin_Mesher.cxx in order to reduce the amount of changes. It could look like this: