Thanks Georg, and thanks Greg for hitting that one issue Schorsch raised there. Other replies below...
On 3/9/16, 7:27 PM, "Georg Mischler" <schor...@schorsch.com> wrote: > >It might be nice to be able to cross-compile at least for the >companion bit-architecture of the same platform, which should be >possible to do. >On the other hand, I'm not sure if its really worth the effort. >How many people are still running Radiance on 32 bit systems? >But at least the possibility should be kept open, so we won't >need another redesign when the first 128 bit systems come out in >a few years... We gave up on providing 32-bit Mac and Linux packages here at NREL, but do still make 32-bit Windows packages, only because we include Radiance with OpenStudio and we are still supporting 32-bit Windows for OpenStudio users (I forget why, but we just do). I was making universal Mac binaries, but it was a PITA to maintain the tifflib and the packages are 2x as large, so I dropped it. >On Windows, everything without third-party dependencies builds >fine with the current VC 2015 "Community" compiler. >I haven't yet gotten around to fetching the Windows dev packages >of Tifflib and QT, so those parts need some more work. >X11 is probably not worth the hassle (though there might be ways). > >The tifflib included with the NREL binaries didn't work, which >means they used a different compiler. In fact, they must be using >gcc on Windows, because I found (and fixed) some non-standard >allocation magic in src/cv/bsdftrans.cpp that only gcc accepts. I am "they". =) Not sure what didn't work for you, Georg. I use a 32-bit windows tifflib from the interwebs (http://gnuwin32.sourceforge.net/packages/tiff.htm), and rolled my own 64-bit when we started making 64-bit Windows packages. I do believe I used gcc, but I can't remember and can't find my notes. Please let me know if there's a better recommended way. >I haven't looked at qtrvu very closely. But even on a cursory >glance it looks straightforward to build. This should not be a >problem for SCons and MSCC, once all the dependencies are in place. >Ah... can we standardize on a file name extension for C++ files in >Radiance? Right now we have both *.cxx and *.cpp. Maybe when you have time, you can look at qtrvu and help make it better. The GUI was modeled after your Windows rvu, included with Rayfront. The folks at Kitware wrote it, but only implemented the bits I felt were absolutely necessary (limited budget). I haven't had access to Rayfront's 'rvu' in a while but I do recall there were some things we left out. As far as the multiple filename extensions, I had no idea. =) I ASSumed .cxx was for headers or some shit. Pretty sure you're the first person to look at that code besides me since it was written! If it's a major deal, I guess we can change it, but it doesn't seem to be hurting anyone except for the anal retentive types here. =) So good to see your name in my inbox again, Schorsch! - Rob _______________________________________________ Radiance-dev mailing list Radiance-dev@radiance-online.org http://www.radiance-online.org/mailman/listinfo/radiance-dev
