Old version of C binaries called by Julia

[bemilio]

Hi Daniel,

I believe that resolving the Julia interface via the standard package manager makes it loads an old version of the .so binaries.
This creates problems on some AVI problems, as there was a relevant debug commit about 3 months ago.

I attach a problematic AVI (obtained by an MPC problem I am working on), a Project.toml and a debug script used to reproduce the error:
Archive.zip

The AVI is solved correctly when manually compiling the C library and copying libdaqp.so in the Julia interface folder (which overrides the Julia interface looking for a downloaded library), thus making me suspicious that, unless you override it manually, the Julia interface loads an old version of the library.

To reproduce the problem:

• Put the content of the .zip in the subfolder debug of DAQP
• Set the project to development: julia --project=./debug -e 'using Pkg; Pkg.develop(path="./interfaces/daqp-julia")'
• run the script: you should get exitflag = -4 (status = Iteration_Limit)
• build the library with cmake --build build, then copy build/libdaqp.so in the `interfaces/daqp-julia'
• Now the problem should be correctly solved

[darnstrom]

Thanks for reporting this @bemilio! I think this should be better documented.

This is currently how the Julia interface works: It loads binaries from DAQP_jll to avoid having the user build it from source. A problem may then arise when loading a local version of the Julia interface, since what is on master is typically not in sync with the old binaries that are automatically used by DAQP_jll. So the steps that you report are indeed the way to go if the version of the Julia interface is out of synced with the released binaries (which is currently the case)

I will release a new version of DAQP and DAQP_jll in the upcoming days!