Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better packaging with autotools. #9

Open
GoogleCodeExporter opened this issue Jul 9, 2015 · 6 comments
Open

Better packaging with autotools. #9

GoogleCodeExporter opened this issue Jul 9, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link

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

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant