Hi Karl, Karl Rupp <r...@iue.tuwien.ac.at> writes: > In your case you just want to create a shared/static library, in which > case you just ultimately link the two together. You can also split > things up based on the operations, e.g. operations_sparse.cpp and > operations_dense.cpp in order to reduce the number of instantiations in > one compilation unit.
Yep. In fact, this is what I've been planning on doing for a while. I've got quite a few EXPORT_BLAH macros, and these are expanded out to do instantiations for the different numeric types / matrix layouts / template arguments / etc. So my plan is just to split these various combinations out into different files, quite like you suggest. The tricky part comes from Boost.Python, which by default scopes things as "one file = one extension", so I'd need to play around with making sure the contents of the different object files all end up in the same namespace. It's feasible, but fiddly (hence why I've not done it till now). Cheers, Toby ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
