camel-k
camel-k copied to clipboard
`make build-resources` does not work on Windows
The build on Windows fails because the build-resources target fails. The package name computed in the following location is not correct:
https://github.com/apache/camel-k/blob/8fcf47c258c00ae3671929ba018ba8aeee79772d/cmd/util/vfs-gen/main.go#L117
I was experiencing the same issue and looking for solutions; I'd want to address this because my primary development environment is on a Windows PC. @astefanutti, could you kindly offer a brief description of the prospective solution you want, as well as any references?
@SubhasmitaSw I can see two possible work-around that I'd like to be confirmed:
- Copy the
script/Makefileinto the project root directory and try to run from there - Overwrite the Makefile symlink at the project root directory with one created by
mklink: https://docs.microsoft.com/fr-fr/windows-server/administration/windows-commands/mklink
Another option would be to run the commands from the script directory, but that requires to make all the paths relative to the location of the Makefile, which may not be straightfoward: https://stackoverflow.com/questions/18136918/how-to-get-current-relative-directory-of-your-makefile
@astefanutti could you please assign this to me, I'd start working on it. Thanks!
@SubhasmitaSw great, assigned :)
@astefanutti this issue description should now be changed to address the major problem, isn't it?
@SubhasmitaSw I've updated the issue title and description. Let me know if that's correct.
@astefanutti Yes, It looks good now. One things, is this still to be considered a good-first-issue?
@astefanutti Yes, It looks good now. One things, is this still to be considered a
good-first-issue?
@SubhasmitaSw I was inclined to be optimistic, but I infer from your comment that you suggest it may not qualify :) I trust your feedback and let's remove the label 👍🏼.
This issue has been automatically marked as stale due to 90 days of inactivity. It will be closed if no further activity occurs within 15 days. If you think that’s incorrect or the issue should never stale, please simply write any comment. Thanks for your contributions!
Do we have the lifecycle/frozen state?
@SubhasmitaSw Do you mean status/never-stale?
@tadayosi yes, we should update this issue to this status.
Fixing this issue while looking into #3364
https://github.com/apache/camel-k/pull/3823
According to the last comment, this is solved. Closing.