-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Custom Component Questions #28
Comments
Is there a list of tasks that need to be done to make a component? This would be very helpful so we could just work down the list instead of trying to get an implied list from the math tutorial. |
|
Hi, I'm Sarah Sposato and I am also working on the math components tutorial.
All of the other steps have been somewhat successful. |
Hi Sarah -- You'll want to run |
Ah I see. Thank you for explaining that! I was getting a similiar "make: *** No rule to make target `testcomp'. Stop." So I figured I was in the wrong place? |
It is similar to the above comment. Running Assuming you put MathSender under 'Ref':
We will update the tutorial to make it more clear. |
Note: In order for these to run properly, the mk/config/modules/modules.mk must be updated to add the path |
Also note that since |
Last updated in April. Closing. |
* Create tutorial-support.yml * Update tutorial-support.yml GpsApp tutorial to be pulled for build test and submodules to be pulled recursively * Implementation of tutorial workflow * typo in repo address * Added missing github action file * Changed workflow path * Changed dir paths * Work around for workflow * work around * troubleshooting * troubleshoot * troubleshoot * Performance update * Path correction * troubleshoot * Dockerfile correction * path change * path change * path fix * path fix * path fix * path fix * paht fix * Revert to changes * Completed workflow for tutorial support * troubleshoot * Build path error * Optimization of workflow * Path fix * Path fix * Path fix #1 * path fix #2 * path check * Workflow test * Workflow test #2 * Added logging feature * Logs Troubleshoot * Typo fix * Troubleshoot #1 * Troubleshoot #2 * Corrected typo on path * Troubleshoot #3 * Troubleshoot #4 * Troubleshoot #5 * Removed log archive feature * Changed repo path to conform pull request merge * Test run #1 * test #2 * test #3 * added branch for workflow test * test #4 * test #4 * test #5 * test #6 * Test #7 * test #8 * test #8 * Test #9 * Test #9 * Test #10 * Test #11 * Test #12 * Test #13 * Test #14 * Test #15 * Test #16 * Test #17 * Test #18 * Test #20 * Test #21 * Test #22 * Test #23 * Test #24 * Test #25 * Split test files * Split tests #2 * Added executable permissions * Delete RPI.bash * Delete Ref.bash * Delete Framework.bash * exe files * Make Framework.bash executable * Make RPI.bash and Ref.bash executable * Test #26 * Test #27 * Test #28 * Attached Integration test to Ref test * Test #29 * Test #30 * Test #31 * Test #32 * Test #33 * Test #34 * Test #35 * Test #35 * Test #37 * Test #38 * Test #39 * Test #40 * Test #41 * Test #42 * Test #43 * Test #43 * Test #44 * Test #45 * Cleaned up files to remove commented code * Remove CI test branch from workflow * Incorporated comments for PR * Modified path for framework job test * Incoporate reviewer comment for PR * Incoporated reviewer comment for PR * Was using incorrect directory for the test * Revised args call for jobs * Passing args #1 * Define entrypoint directly from workflow * Changed entrypoint method * Changed entrypoint method #2 * Corrected test path * Syntax correction * Path Test #1 * Path test #2 * Path Test #4 * Path Test $5 * Test Path #6 * Path Test #6 * Path Test #7 * Path Test #8 * Refactored scripts to remove master.bash * Corrected test path * Fixed log problems * Entrypoint alternative * Bypassed master.bash file * Added line for better CI error messages
I've started trying to make my own component based on the math tutorial component, but have gotten confused by the names of seemingly similar sections of code:
<enum name="MathOp">
<enum name="Operation">
<enum name="MathOperation">
Also, Is there a way to have components and ports two layers below Ref? I tried by putting a mod.mk file in the directory in Ref that had
SUBDIRs = nextLayer
, but this didn't work.The text was updated successfully, but these errors were encountered: