AscentGuidance.cpp : No such file or directory

mstram

Member
Joined
Oct 21, 2008
Messages
47
Reaction score
0
Points
6
Location
Toronto
I just pulled down the repo from svn://svn.code.sf.net/p/shuttleultra/code/trunk

Vis studio 2010 :

AscentGuidance.cpp: No such file or directory

4>LINK : fatal error LNK1104: cannot open file '..\lib\orbiter.lib'

My Library Directories (for EVERY Project !! (is there a global setting somewhere ?) is :
C:\Orbiter2016\Orbitersdk\lib;
C:\Orbiter2016\Orbitersdk\lib\Lua;
$(VCInstallDir)lib;
$(VCInstallDir)atlmfc\lib;
$(WindowsSdkDir)lib;
$(FrameworkSDKDir)\lib

Mike
 
That's because it doesn't exist anymore. :lol:
The VS2010 project files are not being updated anymore (at least not by me). To fix this specific missing file issue (and maybe others) just delete the file entry in the project, and it should compile.

About the lib issue, for what specific project is that? It should all work if you have the "standard" instalation.
 
That's because it doesn't exist anymore. :lol:
The VS2010 project files are not being updated anymore (at least not by me). To fix this specific missing file issue (and maybe others) just delete the file entry in the project, and it should compile.

About the lib issue, for what specific project is that? It should all work if you have the "standard" instalation.
I checked in my updated VS2010 project files so compilation should work smoothly now.
 
Again, I really recommend switching to CMake, for the sake of no longer having the solution file madness unless we want to enforce a special VS version....
 
How are SSU sources organized? There is a lot of VS solutions. Some of them are connected, others looks like separate projects. How should all this projects be build? Into .dlls? Execs?

SSUWorkbench looks like separate application. Atlantis[|_2010|_2013] consists of multiple solutions. Should all of these be build into multiple dlls? Are they connected in one solution only to have all projects in one place?

Thanks in advance for help!
 
Just open the Atlantis solution (*.sln) that corresponds to your VS version (2010 or 2013). Then you should be able to build all the sources in one go.
 
How are SSU sources organized? There is a lot of VS solutions. Some of them are connected, others looks like separate projects. How should all this projects be build? Into .dlls? Execs?

SSUWorkbench looks like separate application. Atlantis[|_2010|_2013] consists of multiple solutions. Should all of these be build into multiple dlls? Are they connected in one solution only to have all projects in one place?

Thanks in advance for help!

In SSU there is a solution with 16 projects (or whatever number it is). A solution is just a "bag" that contains the projects.
Each project builds a vessel: one for the main SSU vessel, another for the ET, the SRBs, etc...
There are 2 versions of the SSU solution (a.k.a "Atlantis"): one for VS2010 and another for VS2013 (I'm only updating this version).

The SSU Workbench is a standalone project with it's own solution.
 
Back
Top