Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

job_class_order: Does not Support Linux/Unix Line Endings #1261

Open
acs9307 opened this issue May 5, 2022 · 0 comments
Open

job_class_order: Does not Support Linux/Unix Line Endings #1261

acs9307 opened this issue May 5, 2022 · 0 comments

Comments

@acs9307
Copy link

acs9307 commented May 5, 2022

Following instructions found here.
https://nasa.github.io/trick/documentation/building_a_simulation/Simulation-Definition-File#specifying-scheduled-loop-job-class-order

Defining a job_class_order results in all text between the curly-brackets to be copied and pasted into a 'exec_add_scheduled_job_class' function call in the build/S_source.cpp file. Using example order will result in the following output in S_source.cpp.

job_class_order {
   my_job_class_1 ;
   my_job_class_2 ;
   scheduled ;
   my_job_class_3 ;
}
exec_add_scheduled_job_class("my_job_class_1 ;
my_job_class_2 ;
scheduled ;
my_job_class_3 ;
");

I'm modifying the file on Mac via VIM, and running in a linux docker.

I have been able to work around the issue by switching to windows line endings and removing the semi-colons. I suspect a simple change to the parsing script can fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant