![]() Blueprints separate the concerns of programming (C, IDL, MATLAB, etc), from domain (space flight, orbital mechanics). We’re marrying a very powerful toolkit (SPICE) to a very powerful authoring platform (Blueprints). All that is highly desirable.Īnd, think about it for a sec. That exact library is used to drive real-life space missions. The nice thing about using the library is it comes pre-built and tested/validated by NAIF. NAIF supplies a pre-built static library for a few relevant platforms - Win32, Win64, Mac. Who knows, maybe your project will need an approach we don’t implement in this series, so let’s touch on them all. We’re going to discuss all of these options. Just put all the CSPICE source code into a UE module and link directly to it.Re-build the static library via the UE build system.Re-build the static library ourselves outside of UE and link to that.Put the pre-built library into a DLL and add that as a project dependency.Integrate the CSPICE pre-built static library into our project.There are a few alternate approaches we can consider. (Which, we won’t be using here.)Īnd of course we’ll need access to the C header files to actually call the library. There’s another library ( csupport.lib) but mostly it’s just a helper library for the standalone CSPICE executable utility apps. ![]() This is the library containing all the compiled code we need. We really only need two things from the SPICE toolkit:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |