[deal.II] Re: linking to lapacke

You are right, Denis. In fact, though, sinocos/FindLAPACK.cmake introduces some conflicts, besides the need of FindBLAS.cmake which is

Re: [deal.II] Re: linking to lapacke

Dear Alberto, Using CMake modules is generally the best approach to take, because it means that you do not hard-code the library locations into your program setup, and it thus remains portable for both code distribution and when you update any libraries that you use. Furthermore, if this

Re: [deal.II] Re: linking to lapacke

Thank you, Jean-Paul, it was very useful. It works well. Alberto *Alberto Salvadori* Dipartimento di Ingegneria Civile, Architettura, Territorio, Ambiente e di Matematica (DICATAM) Universita` di Brescia, via Branze 43, 25123 Brescia Italy tel 030 3711239 fax 030 3711312 e-mail:

[deal.II] Re: linking to lapacke

Hi Alberto, So, if I understand correctly, you've made modifications to the CMakeLists.txt that governs your modified example problem as opposed to linking deal.II itself directly to Lapack. I would say that the most simple (although time-consuming) way to get the correct linker line would be