You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am opening another issue since it is completely unrelated from the first that I made today.
DFNWorks is fantastic but I find it a bit cumbersome to install and use pydfnworks.
All the different components to compile locally in multiple machines and OSs takes quite a bit of time. I was wandering if you ever considered to organize and compact the pip package by including precompiled binaries of lagrit, DFGen etcetc. You could do this by including the binaries in a folder inside the package itself (so for example in pydfnworks>builds).
This would firstly simplify a lot the path management. Since the precompiled libraries are in a folder within the library there won't be the need to use the .dfnworksrc file. Secondly, with a bit of work, it could be possible to make DFNWorks crossplatform!
Implementation of this should not be that difficult because It would require to add the paths of the precompiled libraries in the package_data dict in setup.py like this:
Thank you kindly for the recommendations. For those interested in simpler installation, we provide a docker container. If you would like to test this and submit a pull request, you're most welcome to. Thanks!
Hi again!
I am opening another issue since it is completely unrelated from the first that I made today.
DFNWorks is fantastic but I find it a bit cumbersome to install and use pydfnworks.
All the different components to compile locally in multiple machines and OSs takes quite a bit of time. I was wandering if you ever considered to organize and compact the pip package by including precompiled binaries of lagrit, DFGen etcetc. You could do this by including the binaries in a folder inside the package itself (so for example in pydfnworks>builds).
This would firstly simplify a lot the path management. Since the precompiled libraries are in a folder within the library there won't be the need to use the .dfnworksrc file. Secondly, with a bit of work, it could be possible to make DFNWorks crossplatform!
Implementation of this should not be that difficult because It would require to add the paths of the precompiled libraries in the
package_data
dict insetup.py
like this:and then add in the init.py a way to get the internal path (that is also the the
dfnworks_PATH
). Something like this:The difficult part would be to automate the compilation of the different libraries (maybe using github actions?).
Let me know your thoughts about this!
Thank you again!
The text was updated successfully, but these errors were encountered: