-
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
make impl Command Not Recognized #21
Comments
Perhaps try executing |
@brhs17: Do you have the Here is what the
|
@timcanham The missing makefile was the problem. |
Closing. |
I tried to add a makefile in my sender directory, however, when I tried |
In your makefile, make sure the line:
Is updated for the location of your module. Also, typically, If this doesn't help, can you post your full makefile here for us to help debug? |
This Makefile expects to see the directory |
Yes, the above makefile is in the |
I think you need to change |
Is the above |
It can't find Cheetah. Based on the path, it looks like you may be trying the Cygwin build? Fix the path in |
Yes, you found the correct file. Comment in line five. |
If you are using cygwin, it would be in your cygwin path, not the Windows install. You need to |
After running a pip install of cheetah from my CYGWIN terminal everything worked. THANK YOU. |
@wr3484 It looks like your |
It also looks like the version encoder doesn't like it if there are no commits yet. Is this just a copy of the source rather than a fork? At any rate, do at least one commit of the code. We should make it more robust to non-git copies, however. |
One of our efforts that will be in a future update for F' will be advancing Python to 3.x, but for now it requires 2.x. I haven't really tried running with both yet. |
Also, Cygwin isn't a supported platform. We support Linux and MacOS. We used to support Cygwin, but in the last year or so switched to WSL for Windows. If you want to do PRs with Cygwin fixes, we'll accept them, but they will be as-is. |
In your |
I fixed that error, but there are more. Is there anyway to figure out where the recipe failed? |
I was able to generate template files for your component after fixing that one error. Are you still having issues generating those files, or are you trying to make something else? Regarding your question, when I first tried running
Maybe try appending |
Some basic questions:
|
Thank you, I forgot to invoke |
Hello Tim,I was trying to set up a virtual environment where I would use fprime, but it seems fprime is pointing to my system-level python dependencies looking for lxml (which fails on run of make because i do t have lxml at the system level). I would rather point it to the virtual environment. Can you point me to the file where I can modify this? Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: Timothy Canham <notifications@github.com> Date: 3/18/19 8:37 AM (GMT-08:00) To: nasa/fprime <fprime@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: Re: [nasa/fprime] make impl Command Not Recognized (#21) Some basic questions:
Did you add CLEMOps to mk/configs/modules/modules.mk?
Did you invoke make gen_make after you added CLEMOps to 1)?
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/nasa/fprime","title":"nasa/fprime","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/nasa/fprime"}},"updates":{"snippets":[{"icon":"PERSON","message":"@timcanham in #21: Some basic questions: \r\n\r\n1) Did you add `CLEMOps` to `mk/configs/modules/modules.mk`?\r\n2) Did you invoke `make gen_make` after you added `CLEMOps` to 1)?"}],"action":{"name":"View Issue","url":"#21 (comment)"}}}
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "#21 (comment)",
"url": "#21 (comment)",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
How do I find errors in my XML files? My debug response tells me which file is wrong, but nothing about where it is wrong, always saying something like |
* 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
My name is Benjamin and I am a new member on Cornell Cislunar Explorers. I have been working thorough the math component tutorial, and at step 2.4.1 I cannot get the make impl command to create any stubs.
I run the command in the Ref/MathSender directory, and get the result:
make: *** No rule to make target 'impl'. Stop.
I built the component without any problems, and have failed to find anything like misnamed files.
The text was updated successfully, but these errors were encountered: