<Library>atomstruct</Library> sufficient to build for Linux and Mac, but not Windows

[Tristan Croll]

Minor in the grand scheme of things, but annoyingly fiddly to work out what's missing. When building a bundle for Mac and Linux, simply declaring atomstruct as a library dependency in bundle_info.xml is sufficient, but in Windows this leads to unresolved symbol errors - I have to further specify element, arrays and pyinstance for ISOLDE to build correctly. Worked that out some time back, but just stumbled over it again with Clipper (which is now using the atomstruct API for a few tasks). Would be great if all three platforms were consistent with this.

[Conrad Huang]

Unfortunately, that's a Microsoft compiler idiosyncrasy. On Linux and Mac, the gcc/llvm/whatever compiler pulls in the dependent libraries (perhaps because we specify the directory where the libraries sit?); MS Visual C++ does not seem to do the same thing, and, last time I looked, there were no obvious flags to set for finding additional libraries/DLLs. Technically, all those libraries should be specified, and it only happens to work on Linux and Mac (he said, quibbling about semantics).