How angle script is set up now, i seems like it is intended to be customized and built into a project, rather then be an external dependency. Assuming it is meant to be an external dependency though, how I had it set up in my own project was, the main library, is one lib to link to, then each addon is it's own individual lib to link to. Is that pretty much what you were thinking WhitchLord?

I mainly think people will want to link statically to the AngelScript library. The add-ons should probably be copied into the actual project of the application rather than being built as libraries.

Ya that's kinda what I was thinking.

So Debian/Ubuntu packaging really might not be necessary.

Probably not. Especially since there might be need for developers to compile the library with different options. For example, some might prefer to compile without multithread support for better performance, etc.

Maintaining a package would also be difficult as AngelScript is still evolving a lot. Almost every couple of months there are some interface changes that require some minor code changes in the application that links with it.

Ya, in light of this discussion, and the fact that I have custom modifications to the script builder, I have even started compiling AS right into my project :P