chore(wrap): use wrap to manager subprojects

[Decodetalkers]

If use wrap file , then we do not need to clone by ourself

As the project is using meson, meson can use wrap to manager subprojects, then we need not to use clone anymore

Log: use wrap file to manager subprojects

[any1]

This does more than just adding wraps, for which there is already a PR. See #127

[Decodetalkers]

This does more than just adding wraps, for which there is already a PR. See #127

So it is better to find if there is system dependence first right?But I found that you use static to build target, not dylib..But the package in system should be dynamic , so find if there is system depends already is still needed?

Emm , or add option to control it is better?

[any1]

In the current state of affairs, using the system libraries is the fallback. I.e. if no subprojects are found, the system libraries are used.

The current setup suits me well for development purposes and I don't mind that people have to take a few extra steps to build the project if they're building it themselves. It is very little work compared to the work that I've put in. Also, if you're building it yourself so that you can work on the project, then you'll probably want to set things up in a similar way that I have: with symlinks.

[Decodetalkers]

In the current state of affairs, using the system libraries is the fallback. I.e. if no subprojects are found, the system libraries are used.

The current setup suits me well for development purposes and I don't mind that people have to take a few extra steps to build the project if they're building it themselves. It is very little work compared to the work that I've put in. Also, if you're building it yourself so that you can work on the project, then you'll probably want to set things up in a similar way that I have: with symlinks.

I think you are right, then I close this pr