You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello all!
I'm trying to install a fully functional Scheduler application, according to exercise 7 in the presentation https://ntrs.nasa.gov/api/citations/20205011588/downloads/TM%2020205000691%20REV%201.pdf
When I trying to build, errors occur: In file included from ~/cFS/apps/sch/fsw/src/sch_api.c:26:0:
~/cFS/apps/sch/fsw/public_inc/sch_api.h:85:1:error: unknown type name ‘boolean’; did you mean ‘bool’?
boolean SCH_GetProcessingState (void); ...
After trying to fix the types to bool, many other errors appear.
Please, can anyone suggest how to properly integrate the Scheduler application into the cFS system?
(The lab scheduler worked well.)
Per the VDD at https://github.com/nasa/SCH/blob/master/docs/SCH_v2.2.2_VersionDescriptionDocument.pdf the current release is compatible with cFE 6.6. An update is in the works for SCH compatibility with the Caelum bundle. Options are to use a compatible version of cFE, utilize the new release once available, or update the software to work with whatever bundle version you are using.
Hello all!
I'm trying to install a fully functional Scheduler application, according to exercise 7 in the presentation https://ntrs.nasa.gov/api/citations/20205011588/downloads/TM%2020205000691%20REV%201.pdf
When I trying to build, errors occur: In file included from ~/cFS/apps/sch/fsw/src/sch_api.c:26:0:
~/cFS/apps/sch/fsw/public_inc/sch_api.h:85:1:error: unknown type name ‘boolean’; did you mean ‘bool’?
boolean SCH_GetProcessingState (void); ...
After trying to fix the types to bool, many other errors appear.
Please, can anyone suggest how to properly integrate the Scheduler application into the cFS system?
(The lab scheduler worked well.)
Ubuntu 18.04
cFS installed from Core Flight System - BUNDLE (https://github.com/nasa/cfs).
Igor
The text was updated successfully, but these errors were encountered: