j2me-device-db-general Mailing List for j2me-device-db (Page 2)
Brought to you by:
s_szczygiel,
space2
You can subscribe to this list here.
2006 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
(15) |
Oct
|
Nov
(4) |
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
|
Feb
|
Mar
(6) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: James B. <jm...@ho...> - 2006-09-20 15:09:45
|
Thanks for the reply, I've just taken the latest version from CVS (at about 3.30 today) and rebuilt. I've then taken the framework project example mariobros-example.zip. Unpacked it, altered the properties etc. Then I've added a new resource called donkey.png and added the following to the res.bld #pngsize on +donkey.png In the generated device.profile I get the following: //#define $full_canvas 1 //#define $vendor nokia //#define $model s60 //#define $profile nokia/s60 //#define $nokia 1 //#define $nokia/s60 1 //#define $uses.nokia/s60 //#define $uses.nokia/base //#define $uses.generic/midp1 //#define $midp.version 1 //#define $cldc.version 1.0 //#define $mmapi 0 //#define $btapi 0 //#define $nokiaapi 1 //#define $siemensapi 0 //#define $samsungapi 0 //#define $vscl 0 //#define $wmapi 0 //#define $mascotapi 0 //#define $m3gapi 0 //#define $pdaapi 0 //#define $locationapi 0 //#define $webservicesapi 0 import javax.microedition.lcdui.*; import javax.microedition.midlet.*; import javax.microedition.rms.*; //#define $uses.includes/nokiaapi import com.nokia.mid.ui.*; import com.nokia.mid.sound.*; //#define $nokiaapi.ott 1 //#define $nokiaapi.wav 1 //#define $key.up -1 //#define $key.down -2 //#define $key.left -3 //#define $key.right -4 //#define $key.softleft -6 //#define $key.softright -7 //#define $key.clear -8 //#define $canvas_class FullCanvas //#define $uses.nokia/canvas_176x208 //#define $canvas.width 176 //#define $canvas.height 208 //#define $icon.width 42 //#define $icon.height 29 Which is missing the donkey properties. Is there a step I'm missing, or is this a bug? Cheers, James Brook ----- Original Message ----- From: "Sebastian Szczygiel" <seb...@op...> To: <j2m...@li...> Sent: Wednesday, September 20, 2006 3:48 PM Subject: Re: [J2me-device-db-general] Plugin Problems > Hi, > > microcode framework creates a "device.profile" which can be found in > /dist/src after deployment. > > Like written in the documentation you have to include this file in your > java-sources with > > //#include "device.profile" > > After that you can access all device-properties and also the properties > generated by pngsize plugin. > > BR, Sebastian > >> -----Original Message----- >> From: j2m...@li... [mailto:j2me- >> dev...@li...] On Behalf Of Szasz Pal >> Sent: Mittwoch, 20. September 2006 16:43 >> To: James Brook >> Cc: j2m...@li... >> Subject: Re: [J2me-device-db-general] Plugin Problems >> >> Hi! >> >> I'm not very familiar with the microcode framework (I use the other, >> linux/shell/gcc based one), but here is how the pngsize works: >> >> When the exporter runs in resource collector mode (ie creates the JAR >> file), it can also save the profile as text file. The profile contains >> all the properties from the phone database (for the given phone) as well >> as all the properties defined in the "resource recepie" file, hence also >> the image sizes. >> >> For example let's take a test image, call it test.png. Write the >> following res.txt: >> >> //--------8<---------- >> #pngsize on >> +test.png >> //--------8<---------- >> >> I executed the exporter this way: >> >> $ ~/work/j2me-device-db/tools/exporter/exporter --root >> /work/j2me-device-db/db --res res.txt --jar out.jar --format cpp >> --output profile.h sonyericsson/k750 >> >> (I have the j2medd project at ~/work/j2me-device-db) >> In short what each options does: >> --root - specifies where the phone database is >> --res - means work in resource collector mode, read the resource list >> from res.txt >> --jar - create the jar file with the resource >> --format - use the C header file format for output (for the profile file) >> --output - save the profile file >> >> Now in profile.h I will have all the properties and image sizes: >> >> ... >> //+TEST_PNG >> #define TEST_PNG_WIDTH 256 >> #define TEST_PNG_WIDTH_ "256" >> #define TEST_PNG_HEIGHT 256 >> #define TEST_PNG_HEIGHT_ "256" >> >> I think the microcode framework creates the profile file as well, but I >> don't know where. Also it uses a different naming convention (ie. the >> properties are not converted to uppercase, etc). >> Actually now I just took a look in microcode, it seems it does not save >> the profile file when collecting resources. It executes the exporter >> twice: first to get the profile file, then to create the jar. This has >> the disadvantage that the properties set in the resource file cannot be >> accessed from the code... but I might be mistaken here... >> >> >> James Brook wrote: >> > Hello All, >> > >> > I don't seem to be able to get the plugins to work properly with my >> > basic test project. >> > >> > I have added the command "#pngsize on" to my res.bld and it doesn't >> > appear to have any effect. >> > >> > The documentation says "When this plugin is enabled for each PNG file >> > added to the jar it find out it size and adds the properties >> > '<filename>.width' and '<filename>.height' " >> > >> > Where does it add this property to? >> > >> > Also when I try and include the pngcheck that causes a "[exec] [E] >> > Unknown command `pngcheck' at >> > c:/development/microcode/mariobros/build/res.bld:10!" >> > >> > Any pointers would be great. >> > >> > Cheers, >> > >> > James Brook >> > >> > >> > ------------------------------------------------------------------------ >> > >> > ------------------------------------------------------------------------ >> - >> > Take Surveys. Earn Cash. Influence the Future of IT >> > Join SourceForge.net's Techsay panel and you'll get the chance to share >> your >> > opinions on IT & business topics through brief surveys -- and earn cash >> > >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> > >> > >> > ------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > J2me-device-db-general mailing list >> > J2m...@li... >> > https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general >> >> >> -- >> Best regards, >> Szasz Pal >> ---------------- >> Space Software Studio >> http://www.spacesoftwarestudio.com >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share >> your >> opinions on IT & business topics through brief surveys -- and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> J2me-device-db-general mailing list >> J2m...@li... >> https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > J2me-device-db-general mailing list > J2m...@li... > https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general > > |
From: Szasz P. <sp...@sp...> - 2006-09-20 15:05:09
|
Sebastian Szczygiel wrote: > Hi, > > microcode framework creates a "device.profile" which can be found in > /dist/src after deployment. > > Like written in the documentation you have to include this file in your > java-sources with > > //#include "device.profile" > > After that you can access all device-properties and also the properties > generated by pngsize plugin. > Yes, but as I see, you save the device.profile file when processing only the phone. When you process the resource file (res.txt) the file is not saved. Ie.: <exec executable="${microcode.home}/contrib/exporter/exporter.exe" output="${dist.dir}/src/device.profile"> <arg line="--root ${j2me.device.db} --set ${exporter.props} --format cpp:prefix=//#,nameprefix=$,noupper,n ostrings ${device}"/> </exec> ^--- here is the device.profile created, but here the exporter doesn't create the jar or read the res.txt <target name="resource-collector"> <echo message="Adding resources to JAR ..."/> <exec executable="${microcode.home}/contrib/exporter/exporter.exe"> <arg line="--root ${j2me.device.db} --set ${exporter.props} ${device} -d ${res.dir} -r ${res.bld} ++jar ${ dist.dir}/jadjar/${release.filename}.jar"/> </exec> </target> ^--- here is the resource collected, the jar created, but the output is not saved (so the output of pngsize is lost) -- Best regards, Szasz Pal ---------------- Space Software Studio http://www.spacesoftwarestudio.com |
From: Sebastian S. <seb...@op...> - 2006-09-20 15:04:14
|
Yes, it's a bug (or let's call it a "missing feature") in the microcode framework. > -----Original Message----- > From: James Brook [mailto:jm...@bl...] > Sent: Mittwoch, 20. September 2006 16:57 > To: Sebastian Szczygiel > Subject: Re: [J2me-device-db-general] Plugin Problems > > Thanks for the replies, > > I thought that this was how it was supposed to work. However if I take the > example and add > > #pngsize on > +mariobros_176x208.png > > I don't see any additional fields within the device.profile. Is this a > bug? > > I'll get the latest version and rebuild to see if that will work. > > Cheers, > > James > > ----- Original Message ----- > From: "Sebastian Szczygiel" <seb...@op...> > To: <j2m...@li...> > Sent: Wednesday, September 20, 2006 3:48 PM > Subject: Re: [J2me-device-db-general] Plugin Problems > > > > Hi, > > > > microcode framework creates a "device.profile" which can be found in > > /dist/src after deployment. > > > > Like written in the documentation you have to include this file in your > > java-sources with > > > > //#include "device.profile" > > > > After that you can access all device-properties and also the properties > > generated by pngsize plugin. > > > > BR, Sebastian > > > >> -----Original Message----- > >> From: j2m...@li... > [mailto:j2me- > >> dev...@li...] On Behalf Of Szasz Pal > >> Sent: Mittwoch, 20. September 2006 16:43 > >> To: James Brook > >> Cc: j2m...@li... > >> Subject: Re: [J2me-device-db-general] Plugin Problems > >> > >> Hi! > >> > >> I'm not very familiar with the microcode framework (I use the other, > >> linux/shell/gcc based one), but here is how the pngsize works: > >> > >> When the exporter runs in resource collector mode (ie creates the JAR > >> file), it can also save the profile as text file. The profile contains > >> all the properties from the phone database (for the given phone) as > well > >> as all the properties defined in the "resource recepie" file, hence > also > >> the image sizes. > >> > >> For example let's take a test image, call it test.png. Write the > >> following res.txt: > >> > >> //--------8<---------- > >> #pngsize on > >> +test.png > >> //--------8<---------- > >> > >> I executed the exporter this way: > >> > >> $ ~/work/j2me-device-db/tools/exporter/exporter --root > >> /work/j2me-device-db/db --res res.txt --jar out.jar --format cpp > >> --output profile.h sonyericsson/k750 > >> > >> (I have the j2medd project at ~/work/j2me-device-db) > >> In short what each options does: > >> --root - specifies where the phone database is > >> --res - means work in resource collector mode, read the resource list > >> from res.txt > >> --jar - create the jar file with the resource > >> --format - use the C header file format for output (for the profile > file) > >> --output - save the profile file > >> > >> Now in profile.h I will have all the properties and image sizes: > >> > >> ... > >> //+TEST_PNG > >> #define TEST_PNG_WIDTH 256 > >> #define TEST_PNG_WIDTH_ "256" > >> #define TEST_PNG_HEIGHT 256 > >> #define TEST_PNG_HEIGHT_ "256" > >> > >> I think the microcode framework creates the profile file as well, but I > >> don't know where. Also it uses a different naming convention (ie. the > >> properties are not converted to uppercase, etc). > >> Actually now I just took a look in microcode, it seems it does not save > >> the profile file when collecting resources. It executes the exporter > >> twice: first to get the profile file, then to create the jar. This has > >> the disadvantage that the properties set in the resource file cannot be > >> accessed from the code... but I might be mistaken here... > >> > >> > >> James Brook wrote: > >> > Hello All, > >> > > >> > I don't seem to be able to get the plugins to work properly with my > >> > basic test project. > >> > > >> > I have added the command "#pngsize on" to my res.bld and it doesn't > >> > appear to have any effect. > >> > > >> > The documentation says "When this plugin is enabled for each PNG file > >> > added to the jar it find out it size and adds the properties > >> > '<filename>.width' and '<filename>.height' " > >> > > >> > Where does it add this property to? > >> > > >> > Also when I try and include the pngcheck that causes a "[exec] [E] > >> > Unknown command `pngcheck' at > >> > c:/development/microcode/mariobros/build/res.bld:10!" > >> > > >> > Any pointers would be great. > >> > > >> > Cheers, > >> > > >> > James Brook > >> > > >> > > >> > --------------------------------------------------------------------- > --- > >> > > >> > --------------------------------------------------------------------- > --- > >> - > >> > Take Surveys. Earn Cash. Influence the Future of IT > >> > Join SourceForge.net's Techsay panel and you'll get the chance to > share > >> your > >> > opinions on IT & business topics through brief surveys -- and earn > cash > >> > > >> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > >> > > >> > > >> > --------------------------------------------------------------------- > --- > >> > > >> > _______________________________________________ > >> > J2me-device-db-general mailing list > >> > J2m...@li... > >> > https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general > >> > >> > >> -- > >> Best regards, > >> Szasz Pal > >> ---------------- > >> Space Software Studio > >> http://www.spacesoftwarestudio.com > >> > >> ----------------------------------------------------------------------- > -- > >> Take Surveys. Earn Cash. Influence the Future of IT > >> Join SourceForge.net's Techsay panel and you'll get the chance to share > >> your > >> opinions on IT & business topics through brief surveys -- and earn cash > >> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > >> _______________________________________________ > >> J2me-device-db-general mailing list > >> J2m...@li... > >> https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general > > > > > > ------------------------------------------------------------------------ > - > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > your > > opinions on IT & business topics through brief surveys -- and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > J2me-device-db-general mailing list > > J2m...@li... > > https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general > > > > > > |
From: Sebastian S. <seb...@op...> - 2006-09-20 14:48:49
|
Hi, microcode framework creates a "device.profile" which can be found in /dist/src after deployment. Like written in the documentation you have to include this file in your java-sources with //#include "device.profile" After that you can access all device-properties and also the properties generated by pngsize plugin. BR, Sebastian > -----Original Message----- > From: j2m...@li... [mailto:j2me- > dev...@li...] On Behalf Of Szasz Pal > Sent: Mittwoch, 20. September 2006 16:43 > To: James Brook > Cc: j2m...@li... > Subject: Re: [J2me-device-db-general] Plugin Problems > > Hi! > > I'm not very familiar with the microcode framework (I use the other, > linux/shell/gcc based one), but here is how the pngsize works: > > When the exporter runs in resource collector mode (ie creates the JAR > file), it can also save the profile as text file. The profile contains > all the properties from the phone database (for the given phone) as well > as all the properties defined in the "resource recepie" file, hence also > the image sizes. > > For example let's take a test image, call it test.png. Write the > following res.txt: > > //--------8<---------- > #pngsize on > +test.png > //--------8<---------- > > I executed the exporter this way: > > $ ~/work/j2me-device-db/tools/exporter/exporter --root > /work/j2me-device-db/db --res res.txt --jar out.jar --format cpp > --output profile.h sonyericsson/k750 > > (I have the j2medd project at ~/work/j2me-device-db) > In short what each options does: > --root - specifies where the phone database is > --res - means work in resource collector mode, read the resource list > from res.txt > --jar - create the jar file with the resource > --format - use the C header file format for output (for the profile file) > --output - save the profile file > > Now in profile.h I will have all the properties and image sizes: > > ... > //+TEST_PNG > #define TEST_PNG_WIDTH 256 > #define TEST_PNG_WIDTH_ "256" > #define TEST_PNG_HEIGHT 256 > #define TEST_PNG_HEIGHT_ "256" > > I think the microcode framework creates the profile file as well, but I > don't know where. Also it uses a different naming convention (ie. the > properties are not converted to uppercase, etc). > Actually now I just took a look in microcode, it seems it does not save > the profile file when collecting resources. It executes the exporter > twice: first to get the profile file, then to create the jar. This has > the disadvantage that the properties set in the resource file cannot be > accessed from the code... but I might be mistaken here... > > > James Brook wrote: > > Hello All, > > > > I don't seem to be able to get the plugins to work properly with my > > basic test project. > > > > I have added the command "#pngsize on" to my res.bld and it doesn't > > appear to have any effect. > > > > The documentation says "When this plugin is enabled for each PNG file > > added to the jar it find out it size and adds the properties > > '<filename>.width' and '<filename>.height' " > > > > Where does it add this property to? > > > > Also when I try and include the pngcheck that causes a "[exec] [E] > > Unknown command `pngcheck' at > > c:/development/microcode/mariobros/build/res.bld:10!" > > > > Any pointers would be great. > > > > Cheers, > > > > James Brook > > > > > > ------------------------------------------------------------------------ > > > > ------------------------------------------------------------------------ > - > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > > opinions on IT & business topics through brief surveys -- and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > J2me-device-db-general mailing list > > J2m...@li... > > https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general > > > -- > Best regards, > Szasz Pal > ---------------- > Space Software Studio > http://www.spacesoftwarestudio.com > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > J2me-device-db-general mailing list > J2m...@li... > https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general |
From: Szasz P. <sp...@sp...> - 2006-09-20 14:43:42
|
Hi! I'm not very familiar with the microcode framework (I use the other, linux/shell/gcc based one), but here is how the pngsize works: When the exporter runs in resource collector mode (ie creates the JAR file), it can also save the profile as text file. The profile contains all the properties from the phone database (for the given phone) as well as all the properties defined in the "resource recepie" file, hence also the image sizes. For example let's take a test image, call it test.png. Write the following res.txt: //--------8<---------- #pngsize on +test.png //--------8<---------- I executed the exporter this way: $ ~/work/j2me-device-db/tools/exporter/exporter --root /work/j2me-device-db/db --res res.txt --jar out.jar --format cpp --output profile.h sonyericsson/k750 (I have the j2medd project at ~/work/j2me-device-db) In short what each options does: --root - specifies where the phone database is --res - means work in resource collector mode, read the resource list from res.txt --jar - create the jar file with the resource --format - use the C header file format for output (for the profile file) --output - save the profile file Now in profile.h I will have all the properties and image sizes: ... //+TEST_PNG #define TEST_PNG_WIDTH 256 #define TEST_PNG_WIDTH_ "256" #define TEST_PNG_HEIGHT 256 #define TEST_PNG_HEIGHT_ "256" I think the microcode framework creates the profile file as well, but I don't know where. Also it uses a different naming convention (ie. the properties are not converted to uppercase, etc). Actually now I just took a look in microcode, it seems it does not save the profile file when collecting resources. It executes the exporter twice: first to get the profile file, then to create the jar. This has the disadvantage that the properties set in the resource file cannot be accessed from the code... but I might be mistaken here... James Brook wrote: > Hello All, > > I don't seem to be able to get the plugins to work properly with my > basic test project. > > I have added the command "#pngsize on" to my res.bld and it doesn't > appear to have any effect. > > The documentation says "When this plugin is enabled for each PNG file > added to the jar it find out it size and adds the properties > '<filename>.width' and '<filename>.height' " > > Where does it add this property to? > > Also when I try and include the pngcheck that causes a "[exec] [E] > Unknown command `pngcheck' at > c:/development/microcode/mariobros/build/res.bld:10!" > > Any pointers would be great. > > Cheers, > > James Brook > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > ------------------------------------------------------------------------ > > _______________________________________________ > J2me-device-db-general mailing list > J2m...@li... > https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general -- Best regards, Szasz Pal ---------------- Space Software Studio http://www.spacesoftwarestudio.com |
From: James B. <jm...@ho...> - 2006-09-20 14:23:47
|
Hello All, I don't seem to be able to get the plugins to work properly with my = basic test project. I have added the command "#pngsize on" to my res.bld and it doesn't = appear to have any effect. The documentation says "When this plugin is enabled for each PNG file = added to the jar it find out it size and adds the properties = '<filename>.width' and '<filename>.height' "=20 Where does it add this property to? Also when I try and include the pngcheck that causes a "[exec] [E] = Unknown command `pngcheck' at = c:/development/microcode/mariobros/build/res.bld:10!" Any pointers would be great. Cheers, James Brook |
From: James B. <jm...@ho...> - 2006-09-11 18:49:56
|
Hello, I was wondering if you have had any problems with Pre-Verification failing on the obfuscated version? I'm converting my project to use the j2me-device-db from an existing Antenna build process. This existing process makes uses of the wtk-package instead of doing the build in the 2 steps (creating jar - then pre-verifying). It builds the un obfuscated version ok, but fails on the the obfuscated version. The output says the following: [echo] Obfuscating ... [echo] c:/development/eclipse2/workspace/TestApp/lib/midp2-cldc11.jar;c: /development/eclipse2/workspace/TestApp/lib/nokia-ui.jar [proguard] ProGuard, version 3.3 [proguard] ProGuard is released under the GNU General Public License. The autho rs of all [proguard] programs or plugins that link to it (net.sf.antcontrib.logic, ..) t herefore [proguard] must ensure that these programs carry the GNU General Public License as well. [proguard] Reading program jar [C:\development\eclipse2\workspace\TestApp\di st\jadjar\sonyericsson\k800\TestGame_v1-0-0_en.jar] [proguard] Reading library jar [C:\development\eclipse2\workspace\TestApp\li b\midp2-cldc11.jar] [proguard] Reading library jar [C:\development\eclipse2\workspace\TestApp\li b\nokia-ui.jar] [proguard] Preparing output jar [C:\development\eclipse2\workspace\TestApp\d ist\jadjar_obfuscated\sonyericsson\k800\TestGame_v1-0-0_en.jar] [proguard] Copying resources from program jar [C:\development\eclipse2\worksp ace\TestApp\dist\jadjar\sonyericsson\k800\TestGame_v1-0-0_en.jar] [wtkjad] ************************************************************** [wtkjad] * Antenna 0.9.13 initialized for project "microcode build file" * [wtkjad] * Using Sun Wireless Toolkit 2.2 (CLDC-1.0; MIDP-1.0) * [wtkjad] ************************************************************** [wtkjad] Creating JAD file C:\development\eclipse2\workspace\TestApp\dist\ jadjar_obfuscated\sonyericsson\k800\TestGame_v1-0-0_en.jad [wtkpreverify] Preverifying C:\development\eclipse2\workspace\TestApp\dist\ja djar_obfuscated\sonyericsson\k800\TestGame_v1-0-0_en.jar [wtkpreverify] Error preverifying class as [wtkpreverify] VERIFIER ERROR as.e()V: [wtkpreverify] Expecting to find object/array on stack BUILD FAILED C:\development\eclipse2\workspace\TestApp\build\build.xml:8: The following er ror occurred while executing this line: C:\development\j2me-device-db\tools\microcode\build.xml:50: The following error occurred while executing this line: C:\development\j2me-device-db\tools\microcode\build.xml:61: The following error occurred while executing this line: C:\development\j2me-device-db\tools\microcode\build.xml:143: Preverification fai led (result=1) I'm a bit baffled why the Antenna is being initialized as a CLDC-1.0 & MIDP-1.0 when further up on the build it builds the main project as: [echo] Using CLDC 1.1 MIDP 2.0 [delete] Deleting: C:\development\eclipse2\workspace\TestApp\dist\src\devi ce.properties [wtkjad] ************************************************************** [wtkjad] * Antenna 0.9.13 initialized for project "microcode build file" * [wtkjad] * Using Sun Wireless Toolkit 2.2 (CLDC-1.1; MIDP-2.0) * [wtkjad] ************************************************************** I'm guessing this is why it is failing the verification. Does anyone else see the same problem? Thanks in advance, James Brook |
From: Sebastian S. <seb...@op...> - 2006-08-04 11:28:15
|
Without setting source and target in wtkbuild i get only a warning [wtkbuild] WARNING [wtkbuild] The -source switch defaults to 1.5 in JDK 1.5. [wtkbuild] If you specify -target 1.1 you now must also specify -source 1.2. [wtkbuild] Ant will implicitly add -source 1.2 for you. Please change your bui ld file. But, the build is still successful. Strange, nevertheless I'll keep your hint in the build code. But, what do you say about using source="1.2" instead of source="1.3" ? <wtkbuild srcdir="${dist.dir}/src" bootclasspath="${project.libs}" destdir="${dist.dir}/classes" preverify="false" source="1.2" target="1.1"/> Because I think J2ME/MIDP code is only source 1.2 based? Sebastian _____ From: j2m...@li... [mailto:j2m...@li...] On Behalf Of James Brook Sent: Freitag, 4. August 2006 13:21 To: szc...@co...; j2m...@li... Subject: Re: [J2me-device-db-general] Getting started. [try this build-file] Cheers for this! It works, but you have to alter the following line (~90) <wtkbuild srcdir="${dist.dir}/src" bootclasspath="${project.libs}" destdir="${dist.dir}/classes" preverify="false"/> to <wtkbuild srcdir="${dist.dir}/src" bootclasspath="${project.libs}" destdir="${dist.dir}/classes" preverify="false" source="1.3" target="1.1"/> Otherwise it dies when using JDK 1.5 with the following error (javac: target release 1.1 conflicts with default source release 1.5). It also works for WTK25 (beta) as well as WTK22. Thanks for the quick fix! Cheers, James Brook ----- Original Message ----- From: Sebastian <mailto:szc...@co...> Szczygiel To: 'James Brook' <mailto:jm...@ho...> ; j2m...@li... Sent: Friday, August 04, 2006 12:07 PM Subject: RE: [J2me-device-db-general] Getting started. [try this build-file] I think i solved the problem. Please put in your /microcode folder the attached build-file. For me it works now with WTK23. Sebastian _____ From: j2m...@li... [mailto:j2m...@li...] On Behalf Of James Brook Sent: Donnerstag, 3. August 2006 22:54 To: j2m...@li... Subject: Re: [J2me-device-db-general] Getting started. Hello All, I've download the windows version of the J2ME Device DB tools and have followed the examples. By default the demo doesn't work for me since I'm using JDK 1.5 and you have to modify the antenna build target which I have done: From: <wtkbuild srcdir="${dist.dir}/src" bootclasspath="${project.libs}" destdir="${dist.dir}/classes" preverify="false"/> to <wtkbuild srcdir="${dist.dir}/src" bootclasspath="${project.libs}" destdir="${dist.dir}/classes" preverify="false" source="1.3" target="1.1"/> However now I'm getting a different error: [echo] Creating JAR ... [wtkpackage] Building jar: C:\development\microcode\mariobros\dist\jadjar\nokia\ s40\MarioBros_v1-0-0_en.jar [wtkpackage] Updating JAD file C:\development\microcode\mariobros\dist\jadjar\no kia\s40\MarioBros_v1-0-0_en.jad [echo] Preverification ... [wtkpreverify] Preverifying C:\development\microcode\mariobros\dist\jadjar\nokia \s40\MarioBros_v1-0-0_en.jar [wtkpreverify] ERROR: floating-point arguments should not appear [wtkpreverify] Error preverifying class java.lang.String BUILD FAILED C:\development\microcode\mariobros\build\build.xml:8: The following error occurr ed while executing this line: C:\development\j2me-device-db\tools\microcode\build.xml:50: The following error occurred while executing this line: C:\development\j2me-device-db\tools\microcode\build.xml:59: The following error occurred while executing this line: C:\development\j2me-device-db\tools\microcode\build.xml:105: Preverification fai led (result=1) Any ideas? Cheers, James Brook |
From: Sebastian S. <seb...@op...> - 2006-08-04 10:49:36
|
Hello, Install an older WTK version (wtk21 or even older will work) and set it in build.properties The problem is that the build-system currently needs wtk-home for preverify process. I'll try to change the build and make it wtk-independent. I only don't know if it's allowed to include the preverify tool as part of our distribution. Best regards, Sebastian _____ From: j2m...@li... [mailto:j2m...@li...] On Behalf Of James Brook Sent: Donnerstag, 3. August 2006 22:54 To: j2m...@li... Subject: Re: [J2me-device-db-general] Getting started. Hello All, I've download the windows version of the J2ME Device DB tools and have followed the examples. By default the demo doesn't work for me since I'm using JDK 1.5 and you have to modify the antenna build target which I have done: From: <wtkbuild srcdir="${dist.dir}/src" bootclasspath="${project.libs}" destdir="${dist.dir}/classes" preverify="false"/> to <wtkbuild srcdir="${dist.dir}/src" bootclasspath="${project.libs}" destdir="${dist.dir}/classes" preverify="false" source="1.3" target="1.1"/> However now I'm getting a different error: [echo] Creating JAR ... [wtkpackage] Building jar: C:\development\microcode\mariobros\dist\jadjar\nokia\ s40\MarioBros_v1-0-0_en.jar [wtkpackage] Updating JAD file C:\development\microcode\mariobros\dist\jadjar\no kia\s40\MarioBros_v1-0-0_en.jad [echo] Preverification ... [wtkpreverify] Preverifying C:\development\microcode\mariobros\dist\jadjar\nokia \s40\MarioBros_v1-0-0_en.jar [wtkpreverify] ERROR: floating-point arguments should not appear [wtkpreverify] Error preverifying class java.lang.String BUILD FAILED C:\development\microcode\mariobros\build\build.xml:8: The following error occurr ed while executing this line: C:\development\j2me-device-db\tools\microcode\build.xml:50: The following error occurred while executing this line: C:\development\j2me-device-db\tools\microcode\build.xml:59: The following error occurred while executing this line: C:\development\j2me-device-db\tools\microcode\build.xml:105: Preverification fai led (result=1) Any ideas? Cheers, James Brook |
From: James B. <jm...@ho...> - 2006-08-03 20:54:12
|
Hello All, I've download the windows version of the J2ME Device DB tools and have = followed the examples. By default the demo doesn't work for me since I'm using JDK 1.5 and = you have to modify the antenna build target which I have done: From: <wtkbuild srcdir=3D"${dist.dir}/src" bootclasspath=3D"${project.libs}" destdir=3D"${dist.dir}/classes" preverify=3D"false"/> to=20 <wtkbuild srcdir=3D"${dist.dir}/src" bootclasspath=3D"${project.libs}" destdir=3D"${dist.dir}/classes" preverify=3D"false" source=3D"1.3" target=3D"1.1"/> However now I'm getting a different error: [echo] Creating JAR ... [wtkpackage] Building jar: = C:\development\microcode\mariobros\dist\jadjar\nokia\ s40\MarioBros_v1-0-0_en.jar [wtkpackage] Updating JAD file = C:\development\microcode\mariobros\dist\jadjar\no kia\s40\MarioBros_v1-0-0_en.jad [echo] Preverification ... [wtkpreverify] Preverifying = C:\development\microcode\mariobros\dist\jadjar\nokia \s40\MarioBros_v1-0-0_en.jar [wtkpreverify] ERROR: floating-point arguments should not appear [wtkpreverify] Error preverifying class java.lang.String BUILD FAILED C:\development\microcode\mariobros\build\build.xml:8: The following = error occurr ed while executing this line: C:\development\j2me-device-db\tools\microcode\build.xml:50: The = following error occurred while executing this line: C:\development\j2me-device-db\tools\microcode\build.xml:59: The = following error occurred while executing this line: C:\development\j2me-device-db\tools\microcode\build.xml:105: = Preverification fai led (result=3D1) Any ideas? Cheers, James Brook |
From: Szasz P. <sp...@sp...> - 2006-03-17 08:39:58
|
Welcome everybody! -- Best regards, Szasz Pal ---------------- Space Software Studio http://www.spacesoftwarestudio.com |