Is there a particular reason you prefer SuperLU? Just to confirm: the functionality you need is not part of Boost's uBLAS? If it was included, then it would not introduce any new dependencies.
Out of the choices you listed, I'd lean towards Eigen myself: it's nice that it exists as headers only, seems widely used by many other projects, their docs are very clear that BSD projects can use it, and it seems that many package installers support it (Macports, Ubuntu, Fedora, etc.). I think it's best to assume it's installed on the system. Look at how src/cmake/externalpackages.cmake handles WEBP, for example -- search for the key header in the usual system places as well as THIRD_PARTY_TOOLS. Make it optional; if not found, you can use the EIGEN_FOUND to exclude compilation of the ImageBufAlgo source files that depend on it. We can also add a USE_EIGEN flag to the Makefile and src/CMakeLists.txt so that it's really easy to exclude these sections for people who don't want to compile it. I can set this part up for you if you want. Or just to it really basically, and we'll fix it up later. On May 27, 2012, at 11:55 AM, Łukasz Maliszewski wrote: > Returning to the sparse linear system solver topic. If there are no > objections I would like to use SuperLU. > General information: http://crd-legacy.lbl.gov/~xiaoye/SuperLU/ > The license of SuperLU can be found here: > http://crd-legacy.lbl.gov/~xiaoye/SuperLU/License.txt > > I've easily compiled it on mac osx using info from README.txt. The > next step is to add it to the compilation/linking process. Are there > any instructions about it I should follow? > -- Larry Gritz l...@larrygritz.com _______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
