We shouldn't be including the tpp files in any hpps. I would expect there to be an explicit instantiation that handles this. Why is this not an issue on Linux systems? Or phrased differently, why is there no explicit instantiation for the specific case that you need already generated?

So I understand, could you please explain the problem with including top files in hpp files?

I don't know why this only seems to break when I try building with shared libraries on Mac and not on Linux. This was just the first thing I learned how to do that let the shared-libraries-on-Apple-Silicon build succeed.

I'd be happy to change this to adding explicit instantiations, but I wasn't sure where to add them or how many different partial derivatives instantiations I might have to add. Do you have any suggestions?

Ah, sorry! So the idea behind tpps is that you can include them in cpp files to do explicit instantiations. Then by only including hpp files in other places the compiler doesn't have to do implicit instantiations and this should reduce build time.

So I think it should be only 1 per system. Let's chat on the technical call Thursday if you can make it to see if we can find a way that would make it 1) easy to instantiate and 2) solve the issue and allow you to build shared libs :)

Sounds good, Nils! I should be able to make the technical call, and a discussion to find a path forward for this PR would be great.

By the way, I didn't see this coming because many of our hpp's already include tpp's, including the following:

• TimeDependence.hpp
• DgOperator.hpp
• ComputeTimeDerivative.hpp
• EvolveGhBinaryBlackHole.hpp
• EvolveGhSingleBlackHole.hpp
• EvolveGhValenciaDivCleanWithHorizon.hpp
• EvolveM1Grey.hpp
• EvolveScalarTensorSingleBlackHole.hpp
• ConservativeSystem.hpp

You're welcome, @nilsdeppe ! @nilsvu do you still want to take a look at this PR? If so it's ready whenever you get a chance