<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">MacPorts’ old (ancient might be a better word) ogre port doesn’t build any more.<div class=""><br class=""></div><div class="">A new version is mostly done, with a nearly workable Portfile <<a href="https://trac.macports.org/ticket/53338" class="">https://trac.macports.org/ticket/53338</a>>, but I don’t use this software.</div><div class=""><br class=""></div><div class="">NOTE: Do not “sudo port install” this Portfile, or you’ll have a mess on your hands. It’s at the “builds, but needs the installation sorted out” stage. You can see how it works if you “sudo port -v destroot” it.</div><div class=""><br class=""></div><div class="">The destrooting of the software looks really messed up using the default install script.</div><div class=""><br class=""></div><div class="">It’s easy enough to rearrange this, but I don’t use this software. Apparently it is used in conjunction with modelling tools, and no doubt these tools have expectations about how things should be installed.</div><div class=""><br class=""></div><div class="">Also, I see the old ogre port took pains to install a static version of the library, which is not the MacPorts “way”.</div><div class=""><br class=""></div><div class="">If there is anyone who does actually use this software and has insight or thoughts into how it should most optimally be laid out, I’d like some input to finish this off for you.</div><div class=""><br class=""></div><div class="">If there is a macports dev who uses this software, please take it over from here if you want to.</div><div class=""><br class=""></div><div class="">Ken</div></body></html>