On Sat, Jul 9, 2011 at 5:48 AM, Richard Shaw <[email protected]> wrote:
> I've now created a shared library, libpugixml.so, package with a
> soname. I'm actually learning a lot about cmake now as the original
> makefile was building a static library without a soname. I've
> submitted a patch upstream.
>
> $ rpm -qlp pugixml-1.0-1.fc14.x86_64.rpm
> /usr/lib64/libpugixml.so.1.0
> /usr/share/doc/pugixml-1.0
> /usr/share/doc/pugixml-1.0/readme.txt
Sounds good, I'm addressing the install directory structure to make it more
standard and configurable, just need to find the time to finish it off. If you
could send your version of the pugixml cmake file that would be handy so that I
can get OIIO building with it.
Larry, about the docs, which parts do you think we need to install by default?
Currently we install:
* openimageio.pdf
* Doxygen html documentation
* CLA-INDIVIDUAL CLA-CORPORATE
* LICENSE, CHANGES, INSTALL
* And now the new man pages (unix only)
IMO there's no point installing some of the more development-centric stuff like
the CLAs because OIIO developers will presumably be using the repository
version of the source.
I propose we install:
* openimageio.pdf
* Doxygen html documentation
* LICENSE, CHANGES
* man pages (unix only)
It seems to me that there's two overall structures for the install directory
(1) for installation into the unix standard system locations and
(2) for installation into oiio's own directory.
I'll try to make sensible defaults for these two variants. (2) is basically
what we have now, and apart from being relevant for studio packaging it makes
sense on windows. (1) can be the default from-source build if you're not using
the makefiles.
Sound ok?
~Chris
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
