The OpenSees Community

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.

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 a...

Just curious... any word or comment from full time OpenSees developers whether or not a GUI will be incorporated in upcoming future builds?

What he means is you have to really get your hands deep and pull the latest and greatest working source code from the database and be very careful in how you add in your modifications to incorporate warping. For instance, a colleague and I worked together a couple years back to incorporate warping a...

Unfortunately I haven't.... I've been trying to hack at it for some time now but not getting anywhere. I'm hoping that at future builds someone will fix this problem and update the .sln file such that full build will be successful at first try.

Hello all, I'm currently trying to do a build with the very latest and greatest source code (R6076). Unfortunately I'm running into an issue with a library file that's trying to be compiled which is throwing me a LNK1104 error message. The .lib in question is denoted as "libifport.lib." Anyone out t...

LINK is not a folder or project part of OpenSees or any source code for that matter. This is a compiler error saying that the analysis project/library isn't being built or something went wrong and hence the OpenSees project can't be linked to it. One thing that comes to mind is that you should make ...

Did you try getting the last stable solution and project files that correspond with the 2.4.5 release? That might help out with your problem.

I've come across this problem multiple times before... it would typically happen when I would move my whole OpenSees folder to a different location and opened up the solution again. In terms of fixing it... don't really have an idea of how to get rid of that problem.

Not sure if your C# code will integrate and work well with the OpenSees solutions seeing that everything is done in C++...

Problem solved! For future reference if anyone else is having this issue: For some reason the project files need to be updated individually under the Win32/proj directory unlike previous releases apparently. Before you were able to open up the solution file and MS VS would ask you if you would like ...

SVN checkout is back up and running like a champ again now. Happy coding and development yall!

Seeing the same problem as sb1966 when I try to do a svn checkout via my terminal. Was able to do it just fine over the weekend and when a friend of mine did it via tortoise svn.

Looks like with some work and minimal effort, using the OpenSeesVC6 file as the solution file gets things running and built just the same... which leads me to my next question. What is the difference between these two solution files?

Anyone having an issue with the solution file not loading either all the projects or even just some of the projects based on which revision of the source code you check out? Seems like I only see this problem occur after the codes corresponding to the 2.4.5 exes but the 2.4.4 solution file seems to ...