On 18/12/11 10:34, martin f krafft wrote:
also sprach Philip Ashmore<cont...@philipashmore.com> [2011.12.18.1041 +0100]:
Being too familiar with a package sometimes has it's drawbacks.
Absolutely. Thank you for your patience!
v3c is a wrapper package that provides a standard means of interacting with
packages by providing "boilerplate" code, programs and scripts, and allowing
you to manipulate a package through "make" targets, such as
.
make check
make dist
make distcheck
make git branch=1.3.5 release debian
make install
make distclean
How about:
v3c is a build framework that ties in with GNU make, providing
"boilerplate" code for the most common use cases of building
software.
I'd say that's enough, no need to enumerate example targets.
Among its capabilities are doxygen documentation integration, Git version
control integration, configurable build modes (for debug and release builds,
for example), and the ability to specify most configurable options in the
top-level makefile.
Good!
It also provides a C++ class library for use in client projects.
Run "make check" to see test/example C++ programs that use it.
Why would I want to use build framework from within C++? Maybe you
can try to answer this question.
The C/C++ library is just another goodie in the goodie-bag.
It would help provide C/C++ developers with most everything they would
need to start out with packages, using the v3c tests/examples as
starting points.
I'm not a huge automake fan, but until something much better comes along,
it's widely used, so here we are.
The note about "make check" should go into the README file, IMHO.
See treedb, meta-treedb, v3c-dcom and v3c-qt as examples of
projects that use the v3c build framework.
Ok. I am still somewhat confused why the project v3c-dcom and v3c-qt
carry the name of the build framework in the package names, but
I suppose I would look at those packages' descriptions to find out
more.
It was either that or name them "dcom", "qt" etc. I've seen a few others
like them.
Treedb and meta-treedb escaped this because they're unique already.
Also, v3c is an easy-to-type, easy-to-read C++ name space.
I'm not on a branding exercise, it just seemed like the thing to do.
Cheers,
So how's this?
v3c is a build framework that ties in with GNU make, providing
"boilerplate" code for the most common use cases of building
software.
.
Among its capabilities are doxygen documentation integration, Git version
control integration, configurable build modes (for debug and release builds,
for example), and the ability to specify most configurable options in the
top-level makefile.
It also provides a general purpose C++ class library for use in client
projects.
.
See treedb, meta-treedb, v3c-dcom and v3c-qt as examples of projects that use
the v3c build framework.
Regards,
Philip Ashmore
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4eedf20b.4020...@philipashmore.com
