-
Notifications
You must be signed in to change notification settings - Fork 22
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
Fail creating a cdep package for upload #25
Comments
The messages from SnakeYAML take a little getting used to. The relevant piece is this: in 'reader', line 14, column 3: The following messages look like fallout from the failed parse, so that may be the only issue in the file. I hope this helps. I'll leave this thread open in case there are followup issues in creating your package. |
Thx. I know have that error:
Does it mean it cannot find the lib: armeabi/libjni-framework.a inside the zip file ? |
You should put one ABI lib per zip. The reason is that CDep can download on-demand. Meaning a user who is only build/debugging armeabi can get going faster and many people will never need to download mips[64]. However, the error message you have is a parser error. I don't yet see the problem. Looking closer... |
The parser error can be fixed by changing to this line: I originally only supported one .a per zip but that was too limiting. I try to never break an existing package so there is a fallback codepath that lets the freetype lib pass (I still need to figure out why yours doesn't hit that path). I was wrong about "dependencies:", that is valid schema. This is my punishment for answering before coffee. |
Okay, the reason your manifest didn't hit the fallback code path is because you have a license clause which wasn't supported then (so vCurrent doesn't allow single lib and vPrior doesn't allow license). Anyway, the best answer is to use libs: []. This will get you the most modern schema. If you do end up publishing a package, let me know and I can add it to https://github.com/google/cdep/blob/master/smoke-test/cdep.yml (or you can) so that it will be tested on each CDep checkin. |
I made a PR to improve the error message when this happens to people: |
Thx !
I'm trying to compute the sha256 from my gradle script using the ant task:
(gradle file attached for full reference) |
When I execute (in the command line) the shasum tool as per cdep doc I got:
I still have an error while running: Same with all the others lib ... |
BTW, here is the zip with everything I still can't find what is wrong |
Your package works fine for me. I think what's happening is that you already have downloaded your package, then you changed something without incrementing the version number, so now your cached sha256 doesn't agree with your new sha256. I think the best way to solve it is as follows.
This will force the new package to replace the old. Let me know if that fixes it and I'll start looking at improving that error message. |
You were right ! |
I tried to follow the doc to create a cdep package and reach the point where I have to check the integrity of the .yml
So I run: ./cdep fetch upload/cdep-manifest.yml (I put the yml also under upload directory like in the doc)
And I have these errors:
I've attached my .yml (rename .txt because of github).
I'm specially worried about the first error:
in 'reader', line 1, column 1:
coordinate:
if "coordinate:" should not be the first line of the .yml, what should it be ?
cdep-manifest.txt
The text was updated successfully, but these errors were encountered: