Hi Janek, we have misunderstanding here. python3-minieigen is the __binary__ package and it is a bad idea to ship the source code with the package.
Adding minieigen-src binary package is possible, but it looks like very undesired way. As I see, only Yade is using minieigen in the Debian. So, theoretically we can merge it again with Yade. Bot sure, whether it is a good way though.... Yade compiles too slow. Minieigen adds definitely 4-5 compilation minutes and Gigabytes of used RAM. We should really have a look at pybind11 alternative, if it accelerates the compilation. But when I see Serialization.hpp, I am getting crazy from the number of "defines" there. Anton Am Fr., 21. Feb. 2020 um 17:04 Uhr schrieb Janek Kozicki (yade) <jkozicki-y...@pg.edu.pl>: > > Uh Anton, I'm sorry to be so boring: > > I have checked with sid in /etc/apt/sources.list: > > deb-src http://ftp.pl.debian.org/debian/ sid main non-free contrib > > and built the python3-minieigen_0.50.3+dfsg1-12_amd64.deb package. > > There is no /usr/include/minieigen/*pp files inside :( > > For high precision to work, they are necessary. Maybe the proper way > to do this is to introduce python3-minieigen-dev package? I'm not > sure. These sources are needed because of these include  statements. > > I am attaching once again the file python3-minieigen.install which > installs *pp files. Even the *.cpp files are used. If you feel > that *.cpp files are too much, we could duplicate the .cpp files in > yade (they are rather short) and only include the *.hpp files (these > are quite long). But all *pp files in /usr/include/minieigen/ would > be perfect. > > Best regards > Janek _______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : firstname.lastname@example.org Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp