[Radiance-dev] Radiance compiled with mingw gcc (windows)
Georg Mischler
schorsch at schorsch.com
Tue Sep 13 13:52:53 CEST 2005
Francesco Anselmo wrote:
> I've just noticed I forgot to mention that I've also added
> libws2_32 (-lws2_32) to the list of linked libraries to get
> some programs compiled.
What does this do? Is this a compatility layer added by mingw?
I just added a mingw specific config file to CVS:
ray/platform/mingw.cfg:
----------------------------------------------------
# platform specific settings for Windows (mingw)
# where you want everything
[install]
RAD_BASEDIR: c:\radiance3.6a
RAD_BINDIR: bin
RAD_RLIBDIR: share\lib
RAD_MANDIR: share\man
# shouldn't need any changes
[build]
CC: gcc
CPPDEFINES: _WIN32 NDEBUG _CONSOLE _MBCS HDSUF=.exe
CCFLAGS: -O2
LINKFLAGS: -lws2_32
[debug]
CC: gcc
CPPDEFINES: _WIN32 _DEBUG _CONSOLE _MBCS HDSUF=.exe
CCFLAGS: -g
LINKFLAGS: -lws2_32
# never touch below this
[code]
RAD_SPEED: -DSPEED=200
RAD_ARGSCOMPAT: fixargv0.c
RAD_MATHCOMPAT: erf.c
RAD_MEMCOMPAT:
RAD_PROCESS: win_process.c win_popen.c
----------------------------------------------------
I moved some of your stuff to (hopefully) more appropriate lines,
and also corrected the other Windows config (VC6 and cygwin) in
the same way.
> I've tried all of them, and they compile. What is strange is that
> if I use both -f somefile.cal and -o somefile.dat, the program
> exits nicely without writing the file, but if I remember well
> only with windows, not with linux ... strange!
Nothing obvious that I can see here, but of course things could
go wrong in many different ways.
> BTW It looks like the mingw developer are going to add support for large
> file system files at some point, probably later than sooner ...
How are they planning to do this? They would have to extend the
system libraries, as far as I can tell.
-schorsch
--
Georg Mischler -- simulations developer -- schorsch at schorsch com
+schorsch.com+ -- lighting design tools -- http://www.schorsch.com/
More information about the Radiance-dev
mailing list