aapt can't find 9Patch Images - command

I want to certificate an Android project just with cmd. Now Im stocked at the creation of the .apk file. aapt says he cant find the pictures with the .9. ending. If i rename this pictures and delete the .9. ending then everything works fine without the correct size of the pictures in the app.
ettings
I figured out that I have to "crunch" this pictures, like what he says at the page: Ant Build AAPT Crunch is stripping draw9 information from Library resource images but Im not sure how this works correctly.
I tried this command:
aapt crunch -v -S res -C bin/res
It works with my .9.png files but I still dont get it how I can run it, that it creates the .apk file. How can I use it in the following command ?
aapt package -v -f -A \assets -M \AndroidManifest -S \res -I \android.jar -F \Projectname.unsigned.apk \bin
Just this command gives me the following error:
activity_settings.xml:2: error: Error: No resource found that matches the given name (at 'sound' with value '#drawable/btn_sound_active_pressed')
This file is an .9.png file.
With eclipse everything runs fine.

So i figured it out: I have to "crunch" all picture in the res folder first:
aapt crunch -v -S \res -C \bin\res
And then I pointed as a source folder to the res dir and to the bin\res dir. Also added --no-chrunch --generate-dependencies
aapt package --no-crunch --generate-dependencies -v -f
-M \AndroidManifest.xml"
-S \bin\res
-S \res
-A \assets
-I \android.jar
-F \bin\APPNAME.unsigned.apk \bin
Now Its working perfectly. Also with the .9.png 9patch pictures.

Related

tar: Error opening archive: Failed to open 'wekaUT.tar.gz' in Command Line Windows 10

I want to extract a tar file that I obtained at tar.gz file. However, when I try: tar -xzvf wekaUT.tar.gz
I get the following error:
tar: Error opening archive: Failed to open 'wekaUT.tar.gz'
I see the file in my directory as wekaUT.tar.gz.
Any help would be much appreciated.
Just commenting here as I ran into the same issue. In windows "tar xfv .tar.gz" should work if you open the command prompt as administrator.
In my case, I was building the file to untar dynamically using a variable like
tar -xzvf "$SOME_TEMP_DIR/a_cool_file.tar.gz"
And encountered this error because of the quotes. If I updated it to:
tar -xzvf $SOME_TEMP_DIR/a_cool_file.tar.gz
It worked :)
In windows compand promt use quotation marks ("") when specifying the path. It will work properly
Exaple : tar -xvzf "C:/PATH/TO/FILE/FILE-NAME.tar.gz" -C "C:/PATH/TO/FOLDER/EXTRACTION"
tar -xvzf "C:/PATH/TO/FILE/FILE-NAME.tar.gz"

Cannot unpack .tgz mongodb distribution on OSX

I grab the tgz file via
curl -O https://fastdl.mongodb.org/osx/mongodb-osx-ssl-x86_64-2.6.12.tgz
yes I want mongodb version 2.6.12... :(
and I try to unzip it using:
tar -xvzf mongodb-osx-ssl-x86_64-2.6.12.tgz
but I get:
tar: Unrecognized archive format
tar: Error exit delayed from previous errors.
anybody know what might be wrong?
The file didn't download property, so even though it was a .tgz file on the filesystem it was incomplete or corrupted. To get a proper download I had to drop the ssl
before:
curl -O https://fastdl.mongodb.org/osx/mongodb-osx-ssl-x86_64-2.6.12.tgz
after:
curl -O https://fastdl.mongodb.org/osx/mongodb-osx-x86_64-2.6.12.tgz
then unpacking with tar worked. √

wget corrupted file .zip file error

I am using wget to try and download two .zip files (SWVF_1_44.zip and SWVF_44_88.zip) from this site: http://www2.sos.state.oh.us/pls/voter/f?p=111:1:0::NO:RP:P1_TYPE:STATE
when I run:
wget -r -l1 -H -t1 -nd -N -np -A.zip -erobots=off "http://www2.sos.state.oh.us/pls/voter/f?p=111:1:0::NO:RP:P1_TYPE:STATE/SWVF_1_44.zip"
I get a downloaded zip file that has a screwed up name (f#p=111%3A1%3A0%3A%3ANO%3ARP%3AP1_TYPE%3ASTATE%2FSWVF_1_44) and it cannot be opened.
Any thoughts on where my code is wrong?
There's nothing "wrong" with your code. Wget is simply assuming you want to save the file in the same name that appears in the url. Use the -O option to specify an output file:
wget blahblahblah -O useablefilename.zip

ln -s command failing in Solaris

I have a situation where my installation process runs a script which creates symbolic links for couple of files. The case here is the links are not being created and ln -s command is getting failed with the below error.
No such file or directory
Where as the required files exits in the given location. I tried running the ln -s command from command prompt, which is working perfectly fine. What could be the cause.? Any thoughts?
try
ln -sf
using also the absolute path for the source and destination
Regards
Claudio

PintOS, kernel panic with -v option bochs on ubuntu

when i do "pintos -- run alarm-multiple" in .../build/ everything seems fine.
but when i do "make check" in .../build/ all 7 tests failed with the same
"Run didn't start up properly: no "pintos booting" message"
pintos -v -k -T 60 --bochs -- -q run alarm-single < /dev/null 2> tests/threads/alarm-single.errors > tests/threads/alarm-single.output
perl -I../.. ../../tests/threads/alarm-single.ck tests/threads/alarm-single tests/threads/alarm-single.result
FAIL tests/threads/alarm-single
Run didn't start up properly: no "Pintos booting" message
then I discovered "pintos -v -k -T 60 --bochs -- -q run alarm-single" in .../build
it gives a
Bochs is exiting with the following message:
[ ] bochsrc.txt:12: display library 'nogui' not available
if I take away the "-v" it will be fine.
How to fix this
display library 'nogui' not available
Nobody seems to answer me... I got that myself at last.
just need to change the bochs's configure : ./configer --with-nogui
and then compile it again:
make
sudo make install
After that pintos's make check will work.
i had same problem and i solved it.
open "/pintos/src/tests/Make.tests"
edit line 54 (delete -v)
TESTCMD = pintos -v -k -T $(TIMEOUT)
then, in "/threads/build" you can do
make check
Remember when you using Ubuntu 14.04 or 16.04, never forget doing such things when you download original pintos project or any pintos project from Github.
(Any line with no parentheses are terminal commands)
cd ~
gedit .bashrc
(add next line to the final of the file)
{export PATH="$PATH:/home/{username}/pintos/src/utils"}
(save)
bash
cd ~/pintos/src/utils
gedit Makefile
(You need to change one line)
{change LDFLAGS = -lm to LDLIBS = -lm}
(save)
make
Then you can compile and run "make check" for pintos with no error.
(Any ~/pintos should be changed to your pintos path)
Remember final make in ~/pintos/src/utils is ridiculously important. Otherwise you will get "Run didn't start up properly: no "Pintos booting" message".
You can check full version here. http://www.luosheng-parallelbgls.com.cn/2016/03/29/pintos-install/
Cause this is a Chinese version, I would appreciate for anyone who can translate it to English.