Closed rachelkelly closed 4 years ago
Thanks for the report. The "Not an ELF file" message isn't anything to be concerned about; it's only the "Could not find dependency" that is a problem.
I'm a little confused about the sequence of events that leads to you getting this error, though. Are you saying that you are:
briefcase build
briefcase build
againYou're also saying that this is happening on step 3 of the tutorial, when you do the first run; and on step 4 when you do the explicit code update?
If you're able to show us a log of a successful build, that would also help. The log you've provided has two interesting features:
Seeing a successful log might help narrow down what is going on.
Two last things to confirm that you're not doing. These are "Hail Mary" questions; I doubt they're the cause, but if you're doing either of these things, it would explain the behavior you're reporting:
You're definitely running this in "docker mode"? (i.e., you haven't being using the --no-docker
option an leaving that out of the log transcript?)
You're using the stock linux support package - currently Python-3.8-linux-x86_64-support.b2.tar.gz
- obtained from briefcase itself, rather than anything self compiled? If you're not sure which support package is used, you can look in ~/.briefcase/support
; the support packages should be stored there.
Ok, I did this process a few more times in a row just to iron out all the process kinks, and I'm going to chalk this up to newness to the docs. Also, I think, newness to py3-style environmenting, which is the only thing I can guess for the difference in the python - I am one of those unfortunate souls very much stuck on py2 at work, while we move toward py3 slowly, and I am extremely accustomed to virtualenvwrapper's workflow. So I'll do a little reading on py3's venv
. Also I think I bungled a couple of mac vs linux instructions in round 1.
It's working great :) thank you @freakboy3742 & sorry to take yr time! Can't wait to have built this idea I have!
Great to hear it's worked out. If you ever discover the exact sequence of events/conditions that caused this failure, let us know; anything we can do to prevent (or at least warn about) potential failure modes would be a great addition to the docs.
I'm having the exact same error, It might get solved if I reinstall docker and go from start but apparently there is an issue there on Ubuntu 20.04
Edit: Can't confirm it 100% but seems like running briefcase create
solved the issue without removing docker using docker system prune -a
Describe the bug Command
briefcase build
sometimes needs multiple runs to build entirely (and sometimes will not build at all).To Reproduce Steps to reproduce the behavior:
briefcase build
(right before using briefcase run -u on page 4), it simply won't build and throws an error. Therefore, it won't update because the new package is not yet built.Expected behavior Successful
briefcase build
in tutorial on Linux KDE Ubuntu 20.04.Screenshots Scroll to last ~100 lines or so, particularly the
not an ELF file
bit:Environment:
Additional context reminder, just getting this from the Tutorial