The OpenSees Community

Sorry, that was nonsense. I thought I have to get the forces like an ElementRecorder.
But this seems to work actually:

Hi, I try to get the moments from ElasticBeam3d elements. I tried the following: const char* args = "globalForce"; StandardStream dummy; Response* theResponse = m_element->setResponse( &args, 1, dummy ); Information &eleInfo = theResponse->getInformation(); const Vector &eleDat...

Thank you for the answer. That sounds very good.

Hi OpenSees developers.
There are many calls to exit ( -1 );
in OpenSees.
This is not a problem while running OpenSees as console application.
But when you link it to a gui program, it kills your whole application.
What do you think of using exceptions instead or returning an error value?

ok, that works. There are errors in some fortran files, especially in arpack. If you delete these files, it compiles and runs fine.
Thank you very much for the help.

I have the Intel Fortran compiler installed and can build LAPACK.lib, ARPACK.lib, BLAS.lib, UmfPack.lib Here is how I tried to compile: The command for LAPACK.lib is: NMAKE /f "OpenSeesFortran.mak" CFG="LAPACK - Win32 Debug" In the "OpenSeesFortran.mak", I added "/...

OpenSees obviously needs libIEPCF90.lib and libF90.lib.
Do you have Multithreaded-dll runtime versions of these libs? Or maybe the sources?

(otherwise it crashes when i link against my multithreaded-dll runtime format .lib files)

maybe i should switch to linux

The Problem is, that I want to link against Qt libraries, which have Multithreaded-dll runtime format.
Can you tell me how to use the .mak file, or how to generate visual studio projects from that?

Can anyone give me a hint how to compile the Fortran part of OpenSees? I have the Intel Fortran Compiler installed, but the OpenSeesFortran.mak makefile does not run (started with "nmake OpenSeesFortran.mak"). Do I first have to create blas.lib, lapack.lib, arpack.lib, umfpack.lib? I tried...

ok, I figured out a solution: always include the OpenSees headers after all other includes, and only in cpp files. In header-files, just write the OpenSees class names instead of header file includes. I'm not a very experienced developer, but I think it's dangerous overriding defines of std namspace...

Hello, I have OpenSees included in my application. Therefore I included the OpenSees header files. In one of them is a define which makes me problems: #define vector BJvector In my own application I want to use an std::vector<...> but the compiler gives me this error: error C2039: 'BJvector': Is not...

Now I made it without compiling fortran. It was just a problem with the runtime library format. OpenSees now works fine in my application.

I still get linking/winheap errors. In my project (an OpenSceneGraph application), the runtime library is "Multithreaded-Debug-DLL (/MDd)". Therefore, I need to compile OpenSees as MDd too. But that doen't work, because of the fortran libs Do I have to compile the fortran stuff by myself (...

Meanwhile I solved the above problem, but I have another one: I need to link to lapack.lib, otherwise I get "unresolved external symbols" errors. But when I link to lapack.lib, there is an error too: LIBCMTD.lib(_file.obj) : error LNK2005: ___iob_func is already defined in MSVCRTD.lib(MSVC...

Hi, the quickMain example from OpenSees runs fine in its main function. But when I try to use it not in the main function but in a method of my own application, it crashes, because I don't have exit(0) after theAnalysis.analyze(numSteps); The debug message is: "Stack around the variable 'theAna...