Hi Craig, I'm using eclipse3.3.0 and eclipseME1.7.6. Is there a later version of eclipseME? A cvs or svn snapshot perhaps?
Using #if would certainly be more user friendly but #ifdef is a simple enough workaround. I'm now at the stage of trying to get my app to run on one of the J2ME emulators. Both Sun's WTK and microemulator crash at start up with my app that runs quite happily on the Siemens TC65. (it's something to do with starting a new thread just before returning from startapp().) So I tried the supplied Sun simple demo calculator. Runs fine on the Sun WTK emulator but so far cannot get microemu to recognise it as a midlet let alone run it. This is all proving surprisingly hard work. Hopefully the extra debugging facilities of eclipseme should be worth it. BTW Sun's WTK is stunningly slow at starting up, my few years old XP box takes almost a minute, slower than blowing the flash in the TC65! Keep the good work up, Regards, John Craig Setera wrote: >If you are using an older version of EclipseME, you likely do not have >the recent upgrade to using Omry's Antenna preprocessor. > >Markus Sinner wrote: > > >>It seems that the preprocessor then is configured using "V1". The >>Antenna preprocessor supports the //#if xxx=="yyy" only in "V2". >> >>I do not know how to figure that out. Did you use the latest >>eclipseME-build? >> >> >>Markus >> >>John Pote schrieb: >> >> >> >>>Hi all, >>>Having followed, >>> >>> http://eclipseme.org/docs/installEclipseME.html >>> See "4. Configuring Preprocessor Support" at the end of the page. >>> >>>I now have preprocessing running and also noticed that preprocessed code is >>>placed in the .processed dir. >>> >>>BUT only //#ifdef and //#ifndef seem to be working. And in any case the >>>editor window still marks the import as not resolvable even though the >>>preprocessing will remove that line during the build. >>> >>>I have tried ever whichway but can only get //#if xyz to evaluate to true. >>> >>>At least some progress. >>> >>>Best wishes, >>>John >>> >>> >>> >>> >>>Markus Sinner wrote: >>> >>> >>> >>> >>>>Hello John, >>>> >>>>you have to tweak your eclipse as well: >>>> >>>>http://eclipseme.org/docs/installEclipseME.html >>>>See "4. Configuring Preprocessor Support" at the end of the page. >>>> >>>>If that solves your problem, please write a short reply. >>>> >>>>Regards, >>>>Markus >>>> >>>> >>>> >>>> >>>> >>>> >>>------------------------------------------------------------------------- >>>This SF.net email is sponsored by: Splunk Inc. >>>Still grepping through log files to find problems? Stop. >>>Now Search log events and configuration files using AJAX and a browser. >>>Download your FREE copy of Splunk now >> http://get.splunk.com/ >>>_______________________________________________ >>>Eclipseme-users mailing list >>>[email protected] >>>https://lists.sourceforge.net/lists/listinfo/eclipseme-users >>> >>> >>> >> >> >> > >------------------------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. >Still grepping through log files to find problems? Stop. >Now Search log events and configuration files using AJAX and a browser. >Download your FREE copy of Splunk now >> http://get.splunk.com/ >_______________________________________________ >Eclipseme-users mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/eclipseme-users > > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Eclipseme-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/eclipseme-users
