compile opensees with 2015

[keqiliu]

Dear fmk,

I want to use some features of c++11. So I was trying to use vc2015 to compile opensees, but I was faced with many compiling errors, such as "error LNK2019: unresolved external symbol vsprintf" and "error LNK2001: unresolved external symbol _iob_func".

Would you kindly tell me if opensees can be compiled with vc2012， vc2013 or vc2015. And how to resolve the error?

Thanks a lot.

[fmk]

the person who keeps the windows projects updated uses 2012

[blaiman]

I'm pretty much stuck with the same problem... Everything ran very well when compiling and building in MSVS 2010 even with my new code and modifications. The moment I ported over to MSVS 2015 and it updated all my projects, I get the exact same link errors as keqiliu. I gotta play around with this and see how I can do a workaround or maybe ask someone at my office since we ported over our development work from MSVS 2010 to MSVS 2015 also.

Anyone else on here running into the same type of snag and found solutions? Would be greatly appreciated!

[fmk]

sorry but until i can get a machine with 2015 installed i can only provide suggestions .. have you tried google for a possible solution .. there are a few here:

http://stackoverflow.com/questions/3105 ... -dxerr-lib

[huyuntian]

Hi~
I also faced the same errors.

In VS2015, the stdio is defined by:

_ACRTIMP_ALT FILE* __cdecl __acrt_iob_func(unsigned);
#define stdin (__acrt_iob_func(0))
#define stdout (__acrt_iob_func(1))
#define stderr (__acrt_iob_func(2))

but in VS10/12/13 that is defined by :

_CRTIMP FILE * __cdecl __iob_func(void);
#define stdin (&__iob_func()[0])
#define stdout (&__iob_func()[1])
#define stderr (&__iob_func()[2])

but i dont know how to solve this problem, i hope fmk could give some idea?

so, lets find out how to fix it....

[fmk]

you can't use 15 until I can get a current version of the intel compiler and update all the fortran libraries. at the moment i don't have the funds to do so.

[idealzeng]

I compile opensees with vs2017 successfully

[blaiman]

idealzeng wrote:
> I compile opensees with vs2017 successfully

Which revision of the code did you pull to get it to work on MSVS? I pulled the 6236 release code and have 775 errors after I converted to 2017 and tried to do a re-build.