unable to compile due to circular dependencies

[blshkv]

the latest HEAD fails to compile with the following error:

checking for libimobiledevice... no
configure: error: preflight worker support requested but libimobiledevice could not befound

In turn, I'm unable to compile libimobiledevice-1.1.6:

checking for libusbmuxd... no
configure: error: Package requirements (libusbmuxd >= 1.0.9) were not met:
Requested 'libusbmuxd >= 1.0.9' but version of libusbmuxd is 1.0.8

[FunkyM]

Make sure to first compile libusbmuxd (it's a separate package, no longer bundled in usbmuxd).
Then compile libimobiledevice afterward. There is no "recursive" or infact you probably mean "circular" dependency if you do it that way.

[blshkv]

I guess I got confused after some redesign in the latest release. What is the main package?
We used to install libimobiledevice which would pull all deps.
With the last release, the "main" package seems usbmuxd.

[FunkyM]

libplist -> libusbmuxd -> libimobiledevice -> usbmuxd, ifuse, ideviceinstaller, ...

[marksolaris]

The full install... you need to set your PKG_CONFIG_PATH variable to <prefix>/lib/pkgconfig so that each new package you compile can find the latest dependencies.

libplist
libusbmuxd
libimobiledevice
usbmuxd
ifuse
libzip
ideviceinstaller
libirecovery
idevicerestore
libideviceactivation

[Un1Gfn]

libplist -> libusbmuxd -> libimobiledevice -> usbmuxd, ifuse, ideviceinstaller, ...

libusbmuxd depends on usbmuxd, says here

Which one is true for now?

[marksolaris]

libusbmuxd depends on usbmuxd, says here
Which one is true for now?

As the original issue was logged for revision 1.1.6 in March 2014, I'd suggest fetching the June 2020 1.3.0 release and re-testing. There's too much of a difference to answer that question. Try it and see.