-
-
Notifications
You must be signed in to change notification settings - Fork 398
Upload build path is different than output build path #641
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
Labels
status: waiting for information
More information must be provided before work can proceed
Comments
4 tasks
cmaglie
added a commit
that referenced
this issue
Sep 7, 2020
* Remove deprecation from importFile param * Implement --input-file flag * Add comment in --input-file splitting step * Add e2e test for --input-x flags * Refine upload flags testing * Add --input-file file existence check * Use TrimSuffix instead of replace * Restore -i shorthand flag for --input-file and add CLI checkFlagsConflicts function * Improved build path and project name auto-detection This should make the upload command compatibile with all the reasonable usages. See #764 See #641 * Made UploadTest more resilient * upload: sketch is ignored if input-dir or input-file is specified There is no point in overriding the sketch name if the user explicitly give it via command line. * Update go-paths-helper to version 1.3.2 fixes EquivalentTo when used with abs paths * fix TestGetCommandLine * 100% coverage on detectSketchNameFromBuildPath function * Do not git-ignore all *.bin but just inside the client_example folder * slightly simplified function signature (cosmetic) Co-authored-by: Cristian Maglie <[email protected]>
@ardnew |
It should... give it a try and let us know :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Current behavior
The Adafruit nRF52840 core
platform.txt
contains a recipe to generate a bootable DFU .zip package specifying the output path as{build.path}/{build.project_name}.zip
:The upload utility recipe uses the exact same path
{build.path}/{build.project_name}.zip
:Yet when I execute the command pasted above (with a build path given at the command line), the outputs indicate two different paths are used:
If I modify either path pattern I referenced above in
platform.txt
, I can verify the output of both commands uses their respective modified paths, so I'm confident these are the recipes being used.Expected behavior
I would expect the path pattern
{build.path}/{build.project_name}.zip
to resolve to the same path in all recipes, and in particular that path should reflect what's given by command line option--build-path
.Environment
arduino-cli version
):arduino-cli Version: 0.0.0-git Commit: 8759bf46
Ubuntu 18.04.4 LTS
Additional context
The text was updated successfully, but these errors were encountered: