I don't know details of Windows linking, but presume this is something like the library soname on Linux, which is set by libpetsc_soname.
``make V=1` should help with debugging -- you'll be able to see what is being passed to the linker. Sam Guo <[email protected]> writes: > Hi Jed, > On windows, changing those lines allows me to link petsc with my > application but failed at loading the library. I can only load the petsc > lib by using libpetsc.dll and petsc.lib (instead of libpetsc_real.dll and > petsc_real.lib). > > Thanks, > Sam > > On Mon, Oct 26, 2020 at 12:29 PM Sam Guo <[email protected]> wrote: > >> Thanks, Jed. I'll give it a try/ >> >> On Mon, Oct 26, 2020 at 12:20 PM Jed Brown <[email protected]> wrote: >> >>> See libpetsc_shared and the following 2-3 lines in gmakefile. >>> >>> Sam Guo <[email protected]> writes: >>> >>> > Dear PETSc team, >>> > I like to change petsc lib name to petsc_real or petsc_complex to >>> > distinguish real vs complex version. Simply copy of libpetsc to >>> > libpetsc_real does not help. I need to update PETSc makefile to >>> recompile >>> > but I have troubles to figure out where PETSc makefile decides the lib >>> > name. >>> > >>> > Thanks, >>> > Sam >>> >>
