OpenSEES Compilation Errors in Visual Studio 2017 - Resolved

For developers writing C++, Fortran, Java, code who have questions or comments to make.

Moderators: silvia, selimgunay, Moderators

Post Reply
polimeruvijay
Posts: 43
Joined: Fri Jan 29, 2016 10:20 pm

OpenSEES Compilation Errors in Visual Studio 2017 - Resolved

Post by polimeruvijay » Wed Jan 09, 2019 4:06 am

Dear Community Members,

I am trying to compile OpenSEES in VS 2017, The source code which I am trying to compile is successfully compiling in VS 2010, but when I am compiling in the newer version VS 2017, I am getting the errors shown in the image linked below (Link - 1).

Link - 1 - (https://drive.google.com/file/d/1y1-DS4 ... sp=sharing)

While going through the previous topics on this, I found that similar errors have been popping up due to lack of Intel FORTRAN Compiler and resolved successfully after installing it (Please follow Link - 2 to see the topic). Hence I installed Intel Parallel Studio XE (Which consists Intel FORTRAN Compiler), but still getting errors. Also, It did not require any Intel FORTRAN Compiler, when I compiled the source code successfully in VS 2010.

Kindly Help to debug the errors, thereby the source code is compiled successfully in VS 2017 (Enterprise Edition).

Link - 2 - (http://opensees.berkeley.edu/community/ ... ib#p106438)


Thanks and regards...
Last edited by polimeruvijay on Wed Feb 06, 2019 8:59 pm, edited 1 time in total.

polimeruvijay
Posts: 43
Joined: Fri Jan 29, 2016 10:20 pm

Re: OpenSEES Compilation Errors in VS 2017 - Resolved

Post by polimeruvijay » Tue Jan 15, 2019 9:23 pm

Dear Community Members,

Finally the source is compiled in VS 2017, it seems those errors are coming from some corrupted files in the source code. It seems VS 2010 treated those files (mentioned in the image in Link-1, of the question in opensees forum) as good files, whereas VS 2107 treated them as corrupted ones. What I did is, I downloaded the latest Opensees source code form SVN, and replaced those old ones with the latest ones. Then the compilation was successful. If anybody need the VS 2017 compatible source code please drop your email here. I will send you...

Thanks and regards

mujtabaamin
Posts: 4
Joined: Wed May 16, 2018 9:19 pm

Re: OpenSEES Compilation Errors in Visual Studio 2017

Post by mujtabaamin » Fri Jan 25, 2019 11:49 pm

Dear polimeruvijay, please send me the source to this email,

m.amin@kpu.edu.af

polimeruvijay
Posts: 43
Joined: Fri Jan 29, 2016 10:20 pm

Re: OpenSEES Compilation Errors in Visual Studio 2017

Post by polimeruvijay » Sat Jan 26, 2019 6:36 am

Hi Mujtabaamin...

Please follow the below link to download the source code which is compilable in VS 2017, if you face any errors, please post here...

(https://www.dropbox.com/s/55lqp14z276my ... 7.rar?dl=0)

mujtabaamin
Posts: 4
Joined: Wed May 16, 2018 9:19 pm

Re: OpenSEES Compilation Errors in Visual Studio 2017

Post by mujtabaamin » Mon Jan 28, 2019 1:20 am

Dear, Mr.polimeruvijay,

Thanks for sharing the source code,
could please tell me how to come up with these errors?
____________________________________-
Severity Code Description Project File Line Suppression State
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\stringcontainer.cpp 98
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\binaryfilestream.cpp 121
Error C4996 'sprintf': This function or variable may be unsafe. Consider using sprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\binaryfilestream.cpp 573
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\datafilestream.cpp 51
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\datafilestream.cpp 69
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\datafilestream.cpp 135
Error C4996 'sprintf': This function or variable may be unsafe. Consider using sprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\datafilestream.cpp 700
Error C4996 'sprintf': This function or variable may be unsafe. Consider using sprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\element.cpp 423
Error C4996 'sprintf': This function or variable may be unsafe. Consider using sprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\element.cpp 432
Error C4996 'sprintf': This function or variable may be unsafe. Consider using sprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\element.cpp 443
Error C4996 'sprintf': This function or variable may be unsafe. Consider using sprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\element.cpp 453
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\file.cpp 105
Error C4996 'strcat': This function or variable may be unsafe. Consider using strcat_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\file.cpp 106
Error C4996 'strcat': This function or variable may be unsafe. Consider using strcat_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\file.cpp 107
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\file.cpp 110
Error C4996 'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\file.cpp 126
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\file.cpp 127
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\file.cpp 130
Error C4996 'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\file.cpp 148
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\file.cpp 149
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\file.cpp 163
Error C4996 'strcat': This function or variable may be unsafe. Consider using strcat_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\file.cpp 164
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\file.cpp 166
Error C4996 'strcat': This function or variable may be unsafe. Consider using strcat_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\file.cpp 167
Error C1083 Cannot open include file: 'EigenSOE.h': No such file or directory ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\incrementalintegrator.cpp 41
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\information.cpp 175
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\information.cpp 179
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\information.cpp 183
Error C4996 'sprintf': This function or variable may be unsafe. Consider using sprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\node.cpp 1756
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\renderer.cpp 94
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 49
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 50
Error C4996 'ctime': This function or variable may be unsafe. Consider using ctime_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 101
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 102
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 109
Error C4996 'ctime': This function or variable may be unsafe. Consider using ctime_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 121
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 122
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 146
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 166
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 186
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 206
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 226
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 246
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 385
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\simulationinformation.cpp 390
Error C4996 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\standardstream.cpp 40
Error C4996 'strtok': This function or variable may be unsafe. Consider using strtok_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\uniaxialmaterial.cpp 239
Error C4996 'strtok': This function or variable may be unsafe. Consider using strtok_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\uniaxialmaterial.cpp 240
Error C4996 'strtok': This function or variable may be unsafe. Consider using strtok_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\uniaxialmaterial.cpp 247
Error C4996 'strtok': This function or variable may be unsafe. Consider using strtok_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\core\uniaxialmaterial.cpp 248
Warning C4244 'argument': conversion from 'double' to 'int', possible loss of data ElasticPPcpp c:\users\mujtaba amin\desktop\opensees vs2017\opensees vs2017\developer\material\cpp\elasticppcpp.cpp 289

polimeruvijay
Posts: 43
Joined: Fri Jan 29, 2016 10:20 pm

Re: OpenSEES Compilation Errors in Visual Studio 2017

Post by polimeruvijay » Tue Jan 29, 2019 12:37 am

Please post the screenshot of errors list like this (https://drive.google.com/file/d/1y1-DS4 ... DRfwK/view)

mujtabaamin
Posts: 4
Joined: Wed May 16, 2018 9:19 pm

Re: OpenSEES Compilation Errors in Visual Studio 2017

Post by mujtabaamin » Fri Feb 01, 2019 12:59 am

Dear polimeruvijay,

Thanks for the reply,

Please see the following errors, it shows these kind of errors for both versions (VS 2010/VS2017)
https://drive.google.com/file/d/16dG4O7 ... sp=sharing
https://drive.google.com/file/d/1Gk3JDJ ... sp=sharing

polimeruvijay
Posts: 43
Joined: Fri Jan 29, 2016 10:20 pm

Re: OpenSEES Compilation Errors in Visual Studio 2017

Post by polimeruvijay » Fri Feb 01, 2019 11:09 pm

In VS 2017,

1. I am not sure why you are getting the that error due to ";" in capplasiticty.cpp, I have corrected the file. No problem, just double click on the error in the error list, it will take you to the location of error, and show you a red color mark, just please correct the syntax it will go away.

2. Second error is very clear "DoddRestropo.lib" file is missed, just download and add that file from any opensees source code.

3. errors in "Winnt.h" and "Processthreadsapi.h" are coming due to the Operating system incompatibility, if you are using Windows 7 or 8.1, please change the sdk version to "8.1" instead of some "10.104.XXX".

Where as in VS 2010, please upload the "Error list" screenshot instead of Output Window screenshot, because error list provides more info than the output window. I will try to see what can be done.

Thanks and regards...

PaniCesar
Posts: 8
Joined: Tue Aug 25, 2015 9:03 am
Location: UNAM

Re: OpenSEES Compilation Errors in Visual Studio 2017

Post by PaniCesar » Sat Feb 02, 2019 10:31 am

Dear polimeruvijay,

have you tried to compile the version 3.0.0??
I wanted to build a 32 version but it looks like tcl8.6 is needed and, as far as I know it is only available in 64 bits version. Do you have any advise to succeed in this task?

Best regards

polimeruvijay
Posts: 43
Joined: Fri Jan 29, 2016 10:20 pm

Re: OpenSEES Compilation Errors in Visual Studio 2017

Post by polimeruvijay » Mon Feb 04, 2019 3:25 am

Hi PaniCesar

I have not compiled Opensees 3.0.0. Active Tcl/tk 86 is only available in 64bit, 32 bit version is not available as of now. But, you can try with

1. IronTcl (Tcl/tk), 32bit version can be downloaded from the following link (https://www.irontcl.com/).
2. MagicSplat (Tcl/tk), 32bit version can be downloaded from the following link (https://www.magicsplat.com/tcl-installe ... #downloads).

Please let me know, whether these tcl/tk versions worked or not??

Also, if you want to use Opensees 3.0.0, it demands for Python version also, What version of Python are you using? can you provide the links to download the Python files??

Thanks and regards...

PaniCesar
Posts: 8
Joined: Tue Aug 25, 2015 9:03 am
Location: UNAM

Re: OpenSEES Compilation Errors in Visual Studio 2017 - Reso

Post by PaniCesar » Tue Feb 12, 2019 9:04 pm

Thanks for your kind response, polimeruvijay,

I wasn't able to use the IronTcl or MagicSplat to compile OpenSees 3.0.0. I think I will stick to OS 2.5.0 while they release ActiveTcl 8.6 in OS download page. Nevertheless, in the process a new query appeared and I want to resolve it:

1.- in OS/win32/lib/debug there are some .lib files, but if I make changes in the project some of them become obsolete (feap.lib for example) since new definitions appear, and the solution does note make them each time I build (opposite of the case of material.lib and others). Do you have any clue on how to reconstruct this kind of files??

Hope you can help me.
Best regards!!

davidepellecchia
Posts: 2
Joined: Thu Jan 24, 2019 1:10 am
Location: Federico II di Napoli

Re: OpenSEES Compilation Errors in Visual Studio 2017 - Reso

Post by davidepellecchia » Mon Apr 22, 2019 7:55 am

Dear polimeruvijay,

I need your help. I compiled your source code (https://www.dropbox.com/s/55lqp14z276my ... 7.rar?dl=0), compilable in VS 2017, but I'm having many errors.

This is the screenshot of a part of errors list: https://www.dropbox.com/s/ucxc16thjc1bj ... s.png?dl=0

this is the file .txt of errors list: https://www.dropbox.com/s/66v4w3515of7d ... s.txt?dl=0

and finaly this is the log file of output: https://www.dropbox.com/s/rvdf9ay72nljh ... e.txt?dl=0

Thank you very much for your attention

davidepellecchia
Posts: 2
Joined: Thu Jan 24, 2019 1:10 am
Location: Federico II di Napoli

Re: OpenSEES Compilation Errors in Visual Studio 2017 - Reso

Post by davidepellecchia » Wed Apr 24, 2019 1:13 am

Dear polimeruvijay,

What version of TCL have you used?

polimeruvijay
Posts: 43
Joined: Fri Jan 29, 2016 10:20 pm

Re: OpenSEES Compilation Errors in Visual Studio 2017 - Reso

Post by polimeruvijay » Tue May 28, 2019 9:52 pm

Dear davidepellecchia

Thanks for writing to me.

I hope the errors are resolved. It seems your errors are mostly related to missing tcl files. I am using "ActiveTcl8.5.18.0.298892-win32-x86_64-threaded.exe" version of tcl. At present this is not available. You can download it from here (https://www.dropbox.com/s/etrz71to889e8 ... d.exe?dl=0). After installing please add the paths of tcl include and library directories to the opensees project properties in visual studio.

drmaoye
Posts: 1
Joined: Sun Jun 23, 2019 10:55 pm
Location: Guangzhou University

Re: OpenSEES Compilation Errors in Visual Studio 2017 - Reso

Post by drmaoye » Wed Jun 26, 2019 7:07 pm

Dear polimeruvijay, please send me the source to this email,
yemao@gzhue.edu.cn
thank you very much

Post Reply