07-22-2013 05:14 AM
When packaging a webworks application so that it can be deployed to a device, after creating a dev signature & loading it onto the device, I followed the instructions here:
In particular I got to the following line from the website:
bbwp C:\myapp -o C:\myapp\output
As I'm on windows 8 and do not have a .zip archive. You will note from this example line that the output directory is within the application source directory. I followed the same pattern, which seems reasonable.. providing the packager doesn't contain any ludicrous bugs.
To my surprise the packager has recursively created a directory so deep that windows cannot remove it (src/output/src/output...). The packager has literally corrupted my hard-drive. In trying to assess this issue & isolate the problem (as long as the output is somewhere else it seems to work fine) I've now littered my hard drive with these directories.
From a VM with shared directory:
Solved! Go to Solution.
07-22-2013 10:21 AM
Hehehe - that is a VERY stupid bug
Just tried it and it does as you say - thank god for cygwin (no problems killing it again)
Why anyone would be silly enough to type in the example you give is beyond me though
07-23-2013 10:10 AM
Well it's part of the examples, I don't normally try and second guess the boiler-plate instructions. Anyway thanks for checking its not just me
07-23-2013 03:59 PM - edited 07-23-2013 04:08 PM
Sincere apologies for that; I will follow-up with our documentation team to have that fixed ASAP.
Generally I've seen the packager fail if you supply an export folder that is a sub-folder if your project folder, but I've never seen what you describe. I always recommend using a separate folder for output but that is something that needs to be fixed in the docs.
Edit: Documentation teams have been notified.
07-30-2013 01:57 PM
Kudos to MrNorris for helping drive the changes here:
Documentation has been updated as well as a little note to not use a subfolder of the project folder. You've likely saved many developers of the future some heartache :-)
08-13-2013 11:46 AM
i'm on Debian Linux 64bit, using BB10-WebWorks-SDK-Linux-Gold (btw, what version of this WebWorks? )
it happened to me yesterday.
i zipped my application in sample.zip
the correct command should be:
bbwp sample.zip -g password -o outputdir
but accidently i typed:
bbwp -g password -o outputdir
then the rather similar error happened:
[ERROR] Error: ENAMETOOLONG, name too long '/mnt/sdb1/work/rim/workspace-webworks/bbuisamples
luckily it didn't do any harm to my harddisk, it's because in my case, i didn't specify output inside source directory, instead i forget to define source. and after reading this thread i tried to simulate the same thing, and break after few seconds, and the result is just same here in Linux.
aside from documentation, i thing this is minor bug in bbwp that should be fixed.
08-13-2013 06:03 PM
08-16-2013 11:23 AM
FYI, doesn't matter if the directory is on a different drive. If you run bbwp twice, it'll create a recursive structure you can't delete in Windows :-P
I'm using the latest WW10 tools downloaded 8/14/2013 :-P
I tried running bbwp -v to get the version (no other params) and it tries populating source????
[BUILD] Populating application source
Whoever wrote this should be smacked hard :-P