Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - sf-in-sf

Pages: 1 ... 5 6 [7]
91
Bug Reports / build.xml missing
« on: 2012-Apr-19 »

What's going on???

I'm re-installing everything, following all instructions in various forum posts.
Got GLb 10.231, install it on win7, and help->info says version 10.202. The bug of "no arrowdown" is still there.
I keep java properly installed, installed jdk, no problem.
java sdk installed in path with no blanks.

I adjusted the environment variables as described. (By the way, in win7, is it just system variable or also user variables?)

Erased the hkey_user....etc, re-entered the licence code.

Brand new project:

LOCAL a=1
a=a+6
END

then build for android:

_______________________________________
*** Configuration: ANDROID ***
precompiling:
GPC - GLBasic Precompiler V.10.104 SN:cc8796c9 - 3D, NET
Wordcount:2 commands
compile+link:
running Android build-script...
BUILD STAGE 1: Compile and pack RELEASE
Exception in thread "main" java.lang.RuntimeException: Failed to create Q:\Compiler\platform\android\android-sdk-windows\add-ons.
   at com.android.sdklib.SdkManager.loadAddOns(SdkManager.java:665)
   at com.android.sdklib.SdkManager.createManager(SdkManager.java:144)
   at com.android.sdkmanager.Main.parseSdk(Main.java:221)
   at com.android.sdkmanager.Main.run(Main.java:118)
   at com.android.sdkmanager.Main.main(Main.java:102)
Buildfile: build.xml does not exist!
Build failed
.
BUILD STAGE 2: Build DEBUG and install on device
Buildfile: build.xml does not exist!
Build failed
finished Android build-script.
Android=C:\GLBasic\test1\distribute\Android
success
_______________________________________
*** Finished ***
Elapsed: 11.8 sec. Time: 16:59
Build: 1 succeeded.



"build.xml does not exist" is now a new error. How can i cure that?

Help!

92
FAQ / android and archos tablet
« on: 2012-Apr-14 »
Help! What is wrong with my configuration? (win7 + Xubuntu on asus A53SV, archos android tablet 101G9)

The android SDK looks like it's installed o.k. since i get my pgm compiled.  =D
The tablet looks like it is installed o.k. as i can transfer ...\distribute\Android\bin\*name*-glbasic-debug-unaligned.apk into the tablet's directory "Computer\ARCHOS 101G9\Internal Storage\Download"   and then install and run it.  :happy:
(it's the only *.apk file that can be installed o.k. inside the tablet)  :S

By running AVD i get my 3 versions of android o.s. running ok inside the simulator.
However when AVD is open and running, compiling for android in GLbasic doesn't install and run the pgm in the simulator, as described in the help files.
(MoSync did it... if you have the patience to use the tedious C++)  :sick:

 :zzz: At command prompt i type "adb devices" and get the reply:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached

[2 empty lines]
C:\Users\Ra>_

// then//
"adb usb" replies:
error: device not found  :blink:

I tried to update the tablet driver:
computer Rclick -> computer management -> device manager -> portable devices -> archos 101G9
list of driver files:
...system32\DRIVERS\UMDF\WpdMtpDr.dll
...system32\DRIVERS\winusb.sys
...system32\DRIVERS\WUDFRd.sys
...system32\WpdMtp.dll
...system32\WpdMtpUS.dll   :glare:

Win7 doesn't allow me to update to the manufacturer's driver that contains
android_winusb.inf
WdfCoInstaller01009.dll
winusbcoinstaller2.dll
WUDFUpdate_01009.dll
   ...saying the installed drivers are already up-to-date.
Should i force do it manually?  :whip:

As Archos says, i added the line
echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
in c:\Users\Ra\.android\adb_usb.ini
without results.  :(

I can see two "BUILD FAILED" message in the ouput console (is it bad Doctor?):
Quote
____________________________________
*** Configuration: ANDROID ***
precompiling:
GPC - GLBasic Precompiler V.10.104 SN:cc8796c9 - 3D, NET
Wordcount:1139 commands
compile+link:
running Android build-script...
BUILD STAGE 1: Compile and pack RELEASE
     [echo] Gathering info for glbasic...
     [echo] Creating output directories if needed...
     [echo] ----------
     [echo] Handling aidl files...
     [echo] ----------
     [echo] Handling RenderScript files...
     [echo] ----------
     [echo] Handling Resources...

BUILD FAILED
Q:\Compiler\platform\android\android-sdk-windows\tools\ant\build.xml:539: The following error occurred while executing this line:
Q:\Compiler\platform\android\android-sdk-windows\tools\ant\build.xml:568: null returned: 1

Total time: 2 seconds
.
BUILD STAGE 2: Build DEBUG and install on device
     [echo] Gathering info for glbasic...
     [echo] Creating output directories if needed...
     [echo] ----------
     [echo] Handling aidl files...
     [echo] ----------
     [echo] Handling RenderScript files...
     [echo] ----------
     [echo] Handling Resources...

BUILD FAILED
Q:\Compiler\platform\android\android-sdk-windows\tools\ant\build.xml:539: The following error occurred while executing this line:
Q:\Compiler\platform\android\android-sdk-windows\tools\ant\build.xml:568: null returned: 1

Total time: 2 seconds
finished Android build-script.
Android=C:\Users\Ra\Myfuk-GLbasic\GLBasic\GLBasic\AppName004\distribute\Android
success
_______________________________________
*** Finished ***
Elapsed: 17.9 sec. Time: 04:29
Build: 1 succeeded.
   :whistle:

Here is a useful link to archos:
http://www.archos.com/support/support_tech/updates_adb.html?country=ws&lang=en

Finally the pictures used for sprites in GLb' are placed in the app folder and loaded o.k.  :-* (hope the transparency will be fine).
On the local machine the program works  :coke:. When i transfer it (manually) into the tablet, all the images/sprites appear as a white square instead.
I couldn't find where to place the images for them to be included in the apk file. Anyone with some experience there?

Many thanks in advance,  <3

   sf-in-sf

93
......... if you have the emulator running before you start the compiling, autmatically the application goes to the emulator, but really it´s a grear "mierda" it´s really slow, slow.

I found acceptable speeds for os 2.3 and 3.0 only when you set the resolution to 320x480. In the AVD, just edit the os version before running it, and adjust the resolution. It makes a big difference.

Pages: 1 ... 5 6 [7]