trying to compile develop version with MSVC

[jbensabat]

Hello
I am trying to build the MSVC version using the solution pestpp.sln in \pestpp\src
i am trying to build but nothing happens (as if it was built) tried rebuilding nothing happens either.

any help would be appreciated.

best
jac

[jtwhite79]

What configuration is shown at the top of VS?:

I think only x64 Release and x64 Debug are setup. If its not the configuration, then what is being reported in the output window when you select "build" -> "Build Solution"?

[jbensabat]

good morning and thanks for your message
I only build X64 configurations. the intel version compiles (I have not seen yet the end result) but the MSVC version seems locked.
Also I tried building using CMAKE. one project does not build pestpp-pso because a bunch of PANTHER functions are missing, in the file rmsubs.f90.
I tried to look for this lib over the net without success.

on another subject, is there a tutorial for pestpp, i.e., how to build an example step by step ?
best
jac

[jtwhite79]

I just tried the msvc sln on win10 and it works fine for me. Not sure what's happening on your machine, especially if the Intel sln works.

pestpp-pso is not setup to build with cmake but everything else is (pso is the only fortran piece and most of its functionality is now in pestpp-mou). Check out the bat files in the scripts/ dir

There are several fully worked examples around on how to setup for using pest and pest++. Check out the benchmarks/ directory and the pest and pest++ users guides for details. Also the gmdsi jupyter notebooks show a lot of the functionality within a python framework

[jbensabat]

Hi
I am working with MSVC 2022 under windows 11
I have reinstalled the package and now it works.
so pestpp-pso is not supposed to be built ?
thanks
jac

[jtwhite79]

correct - no pestpp-pso

[jbensabat]

hi
I as actually able to build pespp-pso from the supplied sln.
There is only one issue with this sln, the link to mkl lapack and blas libs. If you set the linker switch for mkl and then the exe is created.

I have another question. Does the provided sln allow for the generation of dll's instead of static libs ?
How can I identify the functions that are exported ?
thanks
jac

[jtwhite79]

No dlls. pestpp is a set of statically linked executables. Is there any specific functionality or usecase you are looking for?

[jbensabat]

I am building rainfall-runoff models, based on the NCAR WRFHYDRO package, so the aim is to conduct sensitivity analysis and parameter identification.
the issue with the dlls is that the executables are smaller, but not a real issue.
right now as you can see from my questions I am learning
best
jac

[jtwhite79]

@mnfienen might have some words of wisdom in this setting...

[jbensabat]

thanks
jac

[jbensabat]

Another question :)
there is one workspace, inscheckpp, that does not build
there are no source code files
best
jac

[jtwhite79]

That's a relic of a utility we had planned for but ended moving the utility support to python...so can be ignored

[jbensabat]

thanks
jac