Additional thoughts:
1) if it is acceptable for you, you should try to compile the whole of dynare++ only under Linux as it is simpler. 2) for the parts that you port to Dynare Matlab, you should link against the Matlab Lapack libraries, using a scheme similar to the one we have now in ./mex/source/build.m for the existing DLL in Dynare Matlab.
All the best,
Michel
G. Perendia wrote:
Hi
- Do we have a working and tested Dynare++ build environment for both Linux
and Windows binaries a) under Linux b) under MingW/cygwin Windows?
- I have had a rather taxing (sometimes interesting) time trying to
re-build dynare++ on my Windows machine.
In a false expectations that I am just minutes from compiling Dynare ++, and, after so spending days of installing the whole dynare dev environment as suggested at the Dynare++ page ( lapack, cygwin, pthreads and MingW for window ) and recompiling and rebuilding Atlas library (which itself took approx. a day), going all the time forensically, two steps forward and one backward, I hit a few new problems. E.g.:
If I try to compile Dynare++ using MinGW gcc as recommended at the Dynare++ site, it seems to ignore both, the include and library paths specified with either CPATH, LD_LIBRARY_PATH or with individual options -I or -L or -isystem and, e.g. can not find the pthread.h (or the libcatlas libraries) that cygwin gcc (or cc) successfully finds, compiles and links using specified -I and -L options respectively (even with MingW ld).
Does anyone know a solution to this? (Note: ignorance of -L paths was noticed when I tired to link files successfully compiled with cygwin cc using MinGW )
- Also, with building Dynare++ itself: (using cygwin gcc), among other
problems, to be able to compile all files, as a temporary fix, I had to rename one of its functions (gettimeofday() in journal.cpp, by adding prefix D_ ) as it conflicts with a function of the same name in MingW's sys/time.h and same number of parameters.
Best regards
George
Dev mailing list Dev@dynare.org http://www.dynare.org/cgi-bin/mailman/listinfo/dev