You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
as discussed by email, I am improving the packaging of the CLD.
I broke down my patch into 3 patches.
* packaging1.diff: add or rename a bunch of files to comply with GNU standards.
* packaging2.diff: small minor fix on a comparison between an int and unsigned
int (was making a warning when compiling with -Wall).
* packaging3.diff: add the autotools files.
Now the library can be installed by the common commands:
$ ./configure
NOTE: the maintainer has to run ./autogen.sh first in order to generate the
configure file. But users don't have to run autogen.sh
$ make
$ make install
The C++ library will be installed (shared lib by default, static lib can be
installed as well with the configure option --enable-static) with libtool and
available through pkg-config as well (so very easy to use and use in a project).
Also the example.cc has been transformed into a package test (though a full
test as for the Python wrapper would be nicer, but did not take the time to
make this yet). In other words, it is run by:
$ make check
There are still a few things I'd like to do, like moving code into a src/
directory (and python wrapper into a separate one), including the run of
setup.py in the same Makefile (to install all in one command as an option, not
mandatory), some test, review some code, maybe make some binary package for
Linux distributions, etc. But that's a first step. :-)
Thanks for this extraction. :-)
Original issue reported on code.google.com by [email protected] on 17 May 2012 at 8:59
Original issue reported on code.google.com by
[email protected]
on 17 May 2012 at 8:59Attachments:
The text was updated successfully, but these errors were encountered: