Bug#1006621: ITP: boofcv -- Real-time computer vision library
This is probably a dumb question since I don't know anything about java
build systems, but I'll ask it anyway.
Most build systems think about:
- Which commands are needed to build stuff
- Which commands are needed to rebuild stuff (if some artifacts are
built already or if we're not building everything)
- Obtaining and/or verifying dependencies
When building a package for Debian, we only care about the first one of
these. debian/control defines the Build-Depends, so once the build
system runs, the dependencies are all in place (and if they aren't, we
need to fix debian/control, which is not the build system's
responsibility). And the build happens just once, so we always start at
zero, and we don't need to care about rebuilds.
Given this, would it be reasonable to distro-patch all the gradle stuff
away, and to co-maintain a parallel (and really simple) build that is
mostly a glorified script or better yet, a GNU Makefile, or something?
If everything that gradle does boils down to a bunch of "javac"
invocations and some "cp" commands to install stuff, then this could be
a viable approach. Since this would be a separate, independent build
system, this only makes sense if it's REALLY simple, and I don't know
enough about gradle or boofcv to answer that.
If this doesn't sound too crazy for this project, and if somebody can
tell me how to get the "javac" commands, I can put something together.
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?
Reply to: