+1 Also, not that I've tried it myself, but to ensure that OIIO can be built against Qt installed as a Framework.
Simon Colin Doncaster <[email protected]> wrote: > > Would it not be easier just to explain to users to specify the QTDIR > environment variables to make sure that CMake finds them? The only > difference between the macports method and yours is that macports will push > the libs and binaries into /usr/local/ vs. some arbitrary location. > > Homebrew is another popular distribution manager for OSX and I think basing > the docs on MacPorts would just muddy the waters vs amending the issue. > Plus, this is likely not just an OSX issue but something that needs to be > considered on all platforms? > > Maybe we're using OIIO in a different context than most ( but I'd be > surprised if that was the case ) but we end up building tools that all rely > on different versions of QT, using macports and/or homebrew assumes you're > only linking against a single version of QT ( there are ways of managing > this, but this is the general case ) which is why we rely heavily on the > QTDIR variable. > > I realize that you're looking for the path of least resistance, but I guess > my point is that being clear on using the QTDIR variable and what that means > for CMake vs. having users rely on macports feels more general and safer - I > think it's fair to assume anyone who's building OIIO should be capable > enough to understand this. > > Cheers > > On 2012-04-09, at 12:11 PM, Daniel Wexler wrote: > > More generally, I think there should be step-by-step instructions which show > how to install all the required dependencies and test images so that you can > build all the OIIO tools and run the tests with no errors. > > The current docs recommend downloading Qt from a broken link. Maybe they > should instead say to install MacPorts and provide instructions? > > Or do we somehow benefit by making this all very difficult for new users? > > > On Mon, Apr 9, 2012 at 10:09 AM, Daniel Wexler <[email protected]> wrote: >> >> Can you provide the exact line required for installation? >> >> I don't use MacPorts except that long ago you told me how to install it. >> Maybe we should put the instructions for installing MacPorts into the >> INSTALL doc and wiki page? I think that's how I magically got a bunch of >> the other requirements, but really I have no idea. >> >> >> On Mon, Apr 9, 2012 at 9:55 AM, Larry Gritz <[email protected]> wrote: >>> >>> I installed Qt with Macports, fire and forget. >>> >>> -- lg >>> >>> >>> On Apr 9, 2012, at 8:35 AM, Daniel Wexler wrote: >>> >>> The Wiki and Google Code docs are a bit light on the external >>> dependencies and build instructions required to enable iv. I think we should >>> have a section in the INSTALL doc and on the wikis that describe the steps >>> needed to download, build and install the dependencies required for iv. I'm >>> happy to make these changes to the wiki (assuming I have permissions), but I >>> wanted to make sure that this is the right way to install and build iv with >>> Qt before I added any instructions. >>> >>> What's the best way to download and install Qt for OSX? >>> >>> The Qt download link is wrong. I think the new link >>> is http://qt.nokia.com/downloads/ >>> >>> But I'm not sure that's the best installer. I used it and it worked, but >>> I wasn't sure if I should use the MacPorts version, and, if so, how to >>> install it (yes, maybe I should know how to install MacPorts packages, but I >>> don't use them for anything at all except OIIO and I have no desire to learn >>> about them, I just want a simple instruction in our docs). Can I delete all >>> the extra crap after installation? Does the MacPorts installation of Qt >>> install a smaller set of stuff? Which one do we want to recommend? >>> >>> Once I had Qt installed, I had to look in the Windows build instructions >>> to figure out how to set the QTDIR. CMake didn't find it in my home >>> directory. Maybe that works better with MacPorts? If not, I think we >>> should add this to the wiki for the OSX build instructions. I set QTDIR in >>> my .profile and added $QTDIR/bin to my path and that seemed to make CMake >>> happy about the QT_INCLUDES but not the QT_LIBRARY, but, despite QT_LIBRARY >>> being blank in the CMake diagnostics, it seems to work. >>> >>> Next I had to download, build and install GLEW, which was pretty simple, >>> but still annoying. We should include a link and simple build and install >>> directions (make; sudo make install). >>> >>> I also think we can do a bit better with the instructions for installing >>> the various external test image directories. You need to look at the CMake >>> output to figure out where to install these images, the JPEG2000 link is >>> busted, and the FITS link has lots of subdirectories with no single TGZ >>> file. >>> >>> >>> Dan >>> _______________________________________________ >>> Oiio-dev mailing list >>> [email protected] >>> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org >>> >>> >>> -- >>> Larry Gritz >>> [email protected] >>> >>> >>> >>> _______________________________________________ >>> Oiio-dev mailing list >>> [email protected] >>> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org >>> >> > > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > > > > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
