Julien LEMOINE <[EMAIL PROTECTED]> writes: > Hello, > I am packaging a generic image processing library. > > This library has no .a or .so files, it's a template library, > so there is only .hh abd .hxx files for compilation (and the > code is included in the final binary) > Strange. Can you point me to the homepage of the library? I'd think there should be some code in form of .cc files, or otherwise the headers will blast each app that uses them with the same code. For instance, in the STL, they instantiate the two major uses of the basic_string template class: basic_sting<char> and basic_string<wchar_t>, so this code is shared between all apps using the STL.
> I envisage to make : > - libolena-dev for .hh and hxx file(in /usr/include/oln) > - libolena-doc and libolena-doc-html for documentations > - libolena-demo for binary of demonstration (/usr/bin) and sources of > demonstration (/usr/share/doc/libolena/demo) > > Is this the correct choice ? > This seems fine. Andy -- Andreas Rottmann | [EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
