Development only package?

[Orcan Ogetbil]

On Fri, Jul 8, 2011 at 12:48 PM, Toshio Kuratomi  wrote:
> On Fri, Jul 08, 2011 at 10:06:56AM -0500, Richard Shaw wrote:
>> I'm working on making a package of OpenImageIO[1] which is used by a
>> new branch of blender, blender-cycles[2], which uses the cycles
>> rendering engine[3].
>>
>> There appears to be one bundled library, pugixml[4] but it's only 3
>> files (1 c, and 2 header files) and doesn't not compile on it's own.
>> It looks to be designed intentionally to be built in to other
>> programs.
>>
> The tarball (I actually downloaded the zip but I hope that upstream made the
> tarball contain identical files :-)  seems to compile fine on its own:
>
> cd scripts
> cmake CMakeLists.txt
> make
> ls -al libpugixml.a
> -rw-rw-r--. 1 badger badger 342992 Jul  8 09:42 libpugixml.a
>

What about the case where the upstream tarball is not directly capable
of generating a dynamic or static library?

This is the situation for a review that I am doing [1]. vmpk bundles
the rtmidi [2], but rtmidi is not available as an independent library.
It consists of 1 source and 2 header files and is designed to be
bundled in other software. Is it okay to bundle rtmidi in our vmpk
package?

Thanks,
Orcan

[1] https://bugzilla.redhat.com/show_bug.cgi?id=710917
[2] http://www.music.mcgill.ca/~gary/rtmidi/