I just checked in a fix for the fseeko macro warning, but I doubt it's related to the errors you're seeing.
Did you run xform on its own to see what it spits out for this file? We should figure out if it's xform rather than oconv that is screwing up. Cheers, -Greg > From: Nathaniel Jones <nathaniel...@gmail.com> > Date: December 22, 2016 8:42:49 AM PST > > Well, the fseeko macro is only used by rcontrib, even though it appears in a > header that gets used almost everywhere. So that's unlikely to be the problem. > > For what it's worth, I had no problem running that triangle through my > compiled oconv. The error seems to indicate some problem reading the real > arguments. Does everything work if you remove that triangle from the model? > Or is this a problem with reading all polygons? > > It's hard to imagine that something like this would change depending on the > MVSC version, but I guess if you've eliminated all the other possibilities... > > Nathaniel > > On Thu, Dec 22, 2016 at 11:08 AM, Victor LRG <rio...@gmail.com> wrote: > Nathaniel/Robert, > > I've tried compiling 5.0.a.12 and I also get the same C4005 'fseeko' macro > definition warning (no more erf/erfc warnings though). Annoyingly, > xform/oconv are still giving me the same problems, but I'am not sure if that > is related to these warnings. > > For now I am still using MVSC2015 and Cmake 3.7.1. I wonder if it is worth > trying the older versions you are using. It is a bit of work to remove and > reinstall MVSC... > > Cheers, > > Victor > > On 22 December 2016 at 15:11, Nathaniel Jones <nathaniel...@gmail.com> wrote: > "Roll your own" has been working fine for me with the GitHub combined branch > head, VS2013, CMake 3.3.1, Qt 5.5, and the libtiff rolled from the source > files included in the repo. I haven't seed any problems with evalglare, and I > believe the erf and erfc warnings were fixed a few months ago. I do get this > warning with all the projects now: > > 1>D:\nljones\Radiance\src\common\platform.h(24): warning C4005: 'fseeko' : > macro redefinition > 1> command-line arguments : see previous definition of 'fseeko' > > Nathaniel > > On Thu, Dec 22, 2016 at 10:00 AM, Jan Wienold <jan.wien...@epfl.ch> wrote: > Hi Rob, > > just a short question : is the evalglare-compilation bug for windows solved > for the 5.0.a.12 ? > > if not, just let me know if you need help for solving. Also give me a hint > when a new "big" release is planned. > > FYI: I away from 29.12 to 15.12 without access to email 8-) > > best, > > Jan > > > > On 22/12/16 15:39, Guglielmetti, Robert wrote: > What¹s the vintage of the source code? There were a couple of minor > patches to the 5.0 official release (Mid-September), and the last tag that > builds for Windows for me is the 'NREL 5.0.a.12¹ tag: > > https://github.com/NREL/Radiance/releases/tag/5.0.a.12 > > > You could try the Windows installers we have, which seem to be working: > > https://github.com/NREL/Radiance/releases/download/5.0.a.6/radiance-5.0.a.6 > -win64.exe > https://github.com/NREL/Radiance/releases/download/5.0.a.6/radiance-5.0.a.6 > -win32.exe > > I also Œget¹ wanting to roll your own, though. Again you¹d need to make > sure your source aligns with this commit, or earlier: > https://github.com/NREL/Radiance/commit/0c842736bf2b0908ba0ea42963ea8f4680c > d1fc5 > > And for the record, that NREL Windows build used Cmake 3.3.2, MSVC 12 > 2013, a libtiff I rolled myself with 4.0.4-beta, and Qt5.3. > > The NREL packages aren¹t bulletproof, I¹m finding, but xform and oconv > seem to work fine. It¹d be potentially mutually beneficial for you to try > the NREL package on your input and see what happens. Or, send me your test > input and we can go from there. > > - Rob > > > On 12/22/16, 5:15 AM, "Victor LRG" <rio...@gmail.com> wrote: > > Dear all, > > I amtrying to compile Radiance 5R0 for Windows using Cmake 3.7.1 x86 and > MVSC 2015 v14 with libtiff 3.8.2 and qt-x86-2.0.4. The compilation > finished with no errors (although some 1700 warnings), but when I am > trying a simple test > I get the following error with ovonv: fatal - (!xform > objects/cage_sphere2.rad): bad arguments for polygon "311s1m134f". This > object has the following description, which seems right to me: > > > cage_sphere polygon 311s1m134f > 0 > 0 > 9 -0.833925170898 0.506038208008 0.096073600769 > -0.819481933594 0.473128112793 0.0903565139771 > -0.853187255859 0.492587890625 0.0980178833008 > > > > In VS I can see the following warnings regarding oconv and xform: > > > C4273 'erf': inconsistent dll linkage > C4273 'erfc': inconsistent dll linkage > > > > They both refer to rtmath.h file, which I guess they should refer to > erf.c as well? Actually, this warning also appears for most projects. > I've compiled and used the same package in linux before with no problem. > > > Any ideas? > > > Thanks > > > Victor Lopez-Rioboo Gil > >
_______________________________________________ Radiance-dev mailing list Radiance-dev@radiance-online.org http://www.radiance-online.org/mailman/listinfo/radiance-dev
