#32302: OGRE (Object-Oriented Graphics Rendering Engine) Static Port -----------------------------------+---------------------------------------- Reporter: marin.saric@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: maintainer | Port: ogre, ogre-static -----------------------------------+---------------------------------------- Comment(by marin.saric@…): Definitely! I am going to work with the OGRE team to upstream this so it's ready for Ogre 1.8 which will come out end of this year or early next year. OGRE just very recently switched to CMake (in v1.7.3), so the MacOS X side of the CMake build was still in early development. I made sure my CMakeLists.txt changes don't mess with the existing ports, including the existing MacOS SDK build. It's a kind of a chicken and egg problem, but if I can show them, {{{sudo port install ogre-static}}} and everything magically works, I think it's a powerful demo. The ultimate goal is to make code built with OIS and OGRE able to be recompiled for Linux, MacOS and Windows without any code changes, and I think it can be achieved as early as next release of OGRE. Having this in would help tremendously! Thanks for telling me about the {{{conflicts}}} keyword. I was hoping something like that exists, I knew it was there for variants. I just saw it in the Portfile example in [http://guide.macports.org/#development.practices.rename-replace-port section 4.7.6 Renaming or replacing a port]. It should probably be documented in [http://guide.macports.org/#reference.keywords section 5.1 Global Keywords].. I don't have SVN access yet... I hope to apply soon. Is it OK if you make the "conflicts" change to the Portfile(s)? -- Ticket URL: <https://trac.macports.org/ticket/32302#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS