Am 2016-03-10 18:05, schrieb Guglielmetti, Robert:
Thanks Georg, and thanks Greg for hitting that one issue Schorsch
raised
there. Other replies below...
This is one of the last mailing lists where people still seem to value
the old art of citation editing... ;)
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 suspected as much. I'm usually way behind the curve in terms of
hardware, and even I have thrown out the last 32bit box last year.
I assume it will still build on 32bit anyway, but we don't need to go
the extra mile for that.
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.
Lovely Windows...
I later noticed that I was compiling single-threaded, while the default
on Windows seems to be multi-threaded - whether you need it or not.
Which means you're actually linking to a different system library
(there's about a dozen of them). I've now built my own tifflib, also for
the headers, but had the same problem with that one at first.
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 old Winrview actually came from LBNL (for Desktop Radiance), and I
just fixed it to actually work as intended. I don't think that one has
ever been published in source. Would that fall under the Radiance
licence?
Then maybe we could at least pick it for ideas. I remember I had to
apply
some hacks to be able to stop a running simulation from the UI thread.
I also have something called "winimage" sitting on a disk, but no idea
of
its state of maturity (Rayfront uses an image viewer in Python). It has
the
same LBNL copyright, so we might be able to play with it as well.
What package do I need to fetch for the qt libraries?
Qtrvu looks nice, but playing around with it revealed a few glitches.
Getting the window size right is probably simple, why it always wants
you to hit "enter" twice remains to be seen.
I have no idea how much time I'll have for those things in the near or
not so near future, so don't hold your breath. I just saw an opportunity
in the past few weeks (starting with temporary access to Revit), so I
jumped on the topic again a bit.
Ah... can we standardize on a file name extension for C++ files in
Radiance? Right now we have both *.cxx and *.cpp.
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. =)
Not a big issue, but confusing and distracting. The size and complexity
of
the Radiance sources already makes them confusing enough...
The only counter example is src/cv/bsdftrans.cpp, and a (generated?)
file
in CMakeFiles/.
Some people apparently do use .cxx, to distinguish the shortcut from
"CPP"
for the preprocessor. Out in the wild though, .cpp seems to be about 5
times more popular. I suggest to decide on a standard now (no matter
which),
while the "problem" is still not really one. We should expect the number
of C++ files to grow in the future.
-schorsch
--
Georg Mischler -- simulations developer -- schorsch at schorsch com
+schorsch.com+ -- lighting design tools -- http://www.schorsch.com/
_______________________________________________
Radiance-dev mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-dev
