Hi Charles, > Just adding my opinion here as I have been following this thread. Would > it be possible to have both the .so library and header only options > available or is it a strictly 'this-or-that' scenario?
a header-only version should be possible, but exposes the user to all kinds of compiler flags. One example: In order to provide AVX-enabled code, the user has to pass the respective compilation flags when using a header-only model. Many users don't want that, or may not even be in the position to do that (e.g. if ViennaCL is part of a larger software stack). Ideally, ViennaCL contains AVX- and non-AVX code in the same binary, selecting the appropriate code path based on the actual CPU features *available* rather than relying on the user passing the correct optimization flags. Best regards, Karli ------------------------------------------------------------------------------ _______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
