Plugin dependency management about library HOT 3 CLOSED

If the plugin developer can find a git repo, use git submodules. If not, and the license allows it, simply include the files in the plugin's repo.

There is virtually nothing a makefile can't do. Plugin developers should add pre-build scripts if needed. I'm sure there's a better way, but you could do

build:
    <shell commands>
    $(MAKE)

acceptable for make dep to install

No, definitely not. That would be grounds for deletion, since I consider it malware.

from library.

Right, I use Makefiles a lot and rarely are they inferior to a shell script.

Now, I would think that for consistency in execution of the build, you would want the, let's call it build interface to be consistent.

Meaning that a plugin developer should use either make dep or include any preparatory steps in the main target itself executed when just calling make and not have a magic build-my-stuff.sh in a folder in the repo somewhere (unless it is executed from the Makefile).

The expectation is that the plugin builds with a simple make. Do you agree?

from library.

Closing since make cleandep and make dep is what my build scripts do now. If it doesn't work, I build manually.

from library.