On Tue, Jun 30, 2009 at 3:52 PM, Ondrej Certik<ond...@certik.cz> wrote: > Hi Brian! > > On Tue, Jun 30, 2009 at 1:13 PM, Brian Granger<ellisonbg....@gmail.com> wrote: >> >> Ondrej, >> >> So I heard back from the VisIt devs and thankfully, they keep really >> good records of how they build everything. What they go through to >> build VisIt is insane. But here are the references that I think could >> help you... > > Many thanks for this! Some comments below: > >> >> Here is their main page for information about building VisIt: >> >> https://wci.llnl.gov/codes/visit/source.html >> >> Here is the "build_visit" shell script that will build visit from >> source (check it out, it is 10000 lines long and crazy!) >> >> https://wci.llnl.gov/codes/visit/1.11.2/build_visit > > This is crazy. We can surely do better. They have one script for > everything, that's bad. The way to go is to just make sure every > single spkg package builds fine on all platforms. > >> >> Most relevant to your situation are the build note for different platforms: >> >> https://wci.llnl.gov/codes/visit/1.11.2/BUILD_NOTES >> https://wci.llnl.gov/codes/visit/1.11.2/BUILD_NOTES_MacOSX >> >> The Mac build notes have a good description of how to build Mesa + VTK >> on OS X. It is non-trivial and requires patching VTK and its build >> system. > > So if you look how they install mesa, it's crazy too. Look at how I > install mesa: > > > cd src > ./configure --prefix="$SAGE_LOCAL" --with-driver=xlib --disable-glut > --disable-glw --enable-gl-osmesa > make > cp lib/* $SAGE_LOCAL/lib > cp -r include/* $SAGE_LOCAL/include >
Ok, it's not that different to what they do. Ondrej --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
