conda-forge / adios2-feedstock Goto Github PK

X-ref ornladios/ADIOS2#3160 by @jychoi-hpc

python -c "import adios2; print(adios2.__file__); print(adios2.__version__)"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'adios2'

on Apple M1 (arm64) as of our 2.8.0 package here.
(Likely already an issue with the 2.7.1 package.)

As long as ornladios/ADIOS2#4148 is still in the current defaults, I would prefer to turn -DADIOS2_USE_Campaign=OFF to avoid creating verbose directories in the current working directory of applications that use ADIOS2 (like WarpX and ImpactX and HiPACE++ on Conda-Forge).

adios and adios2 both ship a bpls CLI tool:

ClobberWarning: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/linux-64::adios-1.13.1-nompi_h476e72a_1121, conda-forge/linux-64::libadios2-2.8.3-nompi_h008eccf_105
  path: 'bin/bpls'

Both packages can be used at the same time, e.g., are so in openpmd-api and in older versions of adios2 itself. But, in case both packages are loaded at the same time, the bpls tool from ADIOS2 should be used, because it is backwards compatible (while bpls from ADIOS1 can only read the its files).

conda-forge/staged-recipes#22171 (comment)

cc @carterbox

Hi @minrk,

I am trying to create a build of openPMD-api with ADIOS 2.9.0 included:
conda-forge/openpmd-api-feedstock#106

but somehow it still pulls in the 2.8.3 ADIOS2 builds. Do you understand why it does that?

Some append (truncate later step) features on Windows will need a C++17 compile in post-ADIOS 2.7.1.

Make sure we compile in C++17 on this platform.

It would be helpful if the ADIOS2 package was split in to a (1) C++ library package and a (2) Python package. The issue is that packages that depend on the ADIOS2 C++ interface/library but not on Python get a transitive dependency on Python. See, for example, conda-forge/fenics-dolfinx-feedstock#15.

Additional comment:

No response

Additional comment:

No response