Based on Dima's comments. Is there any reason we can't just use the Gradle Wrapper? That way each project can use the version of Gradle it works with instead of single version for all projects. The only reason I see to not use Gradle wrapper is because it will download its dependencies and maybe for some reason that's not allowed.
BoofCV does have a complex build system because it auto generates code. So you would need to download the jars the auto generate system needs then build a few classes. Now you're ready to create all the code you need for this library. At this point, you can in theory javac the entire project as Dima suggested. Assuming we don't care about mirroring the jar files that are published on Maven central. This would be equivalent of making one large .so instead of 15 little .so. If the end goal is some of the tools included with BoofCV (e.g. calibration and batch scanning of 2d barcodes) into Debian then that's perfectly fine. My preference is using gradle wrapper since that's the least amount of effort for me to do and it's easy to mangle the existing build system. Peter: if I do the build as described in the instructions, using the > "gradlew" commands, and I grep the log for "javac", would that give me > the bulk of the commands that are needed? What else is needed other than > the "javac" commands? > Hmm been a while since I've used javac directly. Probably the easiest way would be to get a file list using "find" and seeing if it blows up when you give it several hundred files or so. - Peter P.S. I'm going to be a bit erratic when I reply for the next couple of weeks at least. -- "Now, now my good man, this is no time for making enemies." — Voltaire (1694-1778), on his deathbed in response to a priest asking that he renounce Satan.
