Deva has it correct..if you're going to use anything from the android-omap3logic repository, please use all of it. The files in there are provided as a whole package..
Regards -- Ashwin On Mon, Apr 5, 2010 at 5:38 PM, Deva R <r.deva...@gmail.com> wrote: > Hi, > > A version mismatch between below header versions might cause such > build errors. i checked and they match your build errors., > > TSLIB header: > http://gitorious.org/android-omap3logic/frameworks-base/blobs/ee594708228548bebd3266c87f51fa4810499f45/base/include/ui/EventHub.h > > Donut header: > http://git.omapzoom.org/?p=platform/frameworks/base.git;a=blob_plain;f=include/ui/EventHub.h;hb=donut > > I guess you got EventHub.h from TSLIB git, but EventHub.cpp is from > donut release. > > > If you are using TSLIB version, you should have picked EventHub.cpp from > http://gitorious.org/android-omap3logic/frameworks-base/blobs/ee594708228548bebd3266c87f51fa4810499f45/base/libs/ui/EventHub.cpp > then you wouldnt have faced this break.. > > then you can see the function signature matching there > bool EventHub::getEvent(InEvent *inevt) > > > On Mon, Apr 5, 2010 at 2:52 PM, Fasil <mfasi...@gmail.com> wrote: >> Hi Deva, >> >> After adding the corresponding files to the Android source and >> on building the source, I m getting the following errors due to the UI >> part of TSLIB, Any suggestion for this, I m using Android donut-1.6 >> >> target thumb C++: libui <= frameworks/base/libs/ui/EventHub.cpp >> In file included from frameworks/base/include/ui/EventHub.h:26, >> from frameworks/base/libs/ui/EventHub.cpp:18: >> frameworks/base/include/ui/IInputDriver.h:24: warning: 'class >> android::IInputDriver' has virtual functions but non-virtual >> destructor >> frameworks/base/libs/ui/EventHub.cpp:257: error: prototype for 'bool >> android::EventHub::getEvent(int32_t*, int32_t*, int32_t*, int32_t*, >> uint32_t*, int32_t*, nsecs_t*)' does not match any in class >> 'android::EventHub' >> frameworks/base/include/ui/EventHub.h:84: error: candidate is: virtual >> bool android::EventHub::getEvent(android::InEvent*) >> make: *** [out/target/product/generic/obj/SHARED_LIBRARIES/ >> libui_intermediates/EventHub.o] Error 1 >> >> >> Regards >> Fasil >> >> On Apr 1, 4:34 pm, Deva R <r.deva...@gmail.com> wrote: >>> can u try this? without doing much, you can just go to the folder, >>> below command will straighaway will start building the module >>> $source <mydroid>/build/envsetup.sh >>> $mm >>> >>> You can plugin a 'Android.mk' file to build system, by placing the >>> folder in <mydroid>/<some-dir> >>> then upper directory's Android.mk files shall include subdirecties' >>> make files, by either a call like 'include $(call >>> all-subdir-makefiles)' or directly by handpicking 'include >>> <path-to-.mk-file>' >>> so, now if you run 'make' at top level, you will see if its included >>> or not. (introduce some junk to make build fail, so u know for sure >>> its included) >>> >>> On Thu, Apr 1, 2010 at 11:58 AM, Fasil <mfasi...@gmail.com> wrote: >>> > Hi Ashwin, >>> >>> > Thanks for your suggestion, Could you help me in adding these files >>> > to Android source. >>> >>> > I have added the TSLIB to the external folder of Android Source and >>> > Framework related files to the framework/base folder of Android >>> > source. >>> >>> > Now do we need to have any changes in Makefile to include TSLIB >>> > package to be build.Any suggestion regarding this. >>> >>> > Thanks >>> > Mohamed Fasil >>> >>> > On Mar 31, 6:34 pm, Ashwin Bihari <abih...@gmail.com> wrote: >>> >> Sending to list as well.. >>> >>> >> -- Ashwin >>> >>> >> ---------- Forwarded message ---------- >>> >> From: Ashwin Bihari <abih...@gmail.com> >>> >> Date: Wed, Mar 31, 2010 at 9:33 AM >>> >> Subject: Re: [android-porting] Touchscreen support for 7 Inch LCD panel >>> >> To: nagarajan1...@gmail.com >>> >>> >> Gokul, >>> >>> >> You need to take those TSLIB generated calibration information and >>> >> then feed that into Android so that it can properly scale the incoming >>> >> X, Y, and Z coordinates from the touch screen controller.. >>> >>> >> I've ported the TSLIB package into Android and added the hooks into >>> >> Android 1.6, you can check them out at: >>> >>> >> TSLIB -http://gitorious.org/android-omap3logic/external-tslib >>> >> Android Changes -http://gitorious.org/android-omap3logic/frameworks-base >>> >>> >> Regards >>> >> -- Ashwin >>> >>> >> On Wed, Mar 31, 2010 at 8:55 AM, Gokul Nagarajan >>> >> <nagarajan1...@gmail.com> wrote: >>> >> > Hello all, >>> >> > We are working in OMAP3530 processor. We have changed the LCD size >>> >> > from 480 x 272 to 800 x 480 . >>> >> > We have changed the front panel parameters accordingly and we are able >>> >> > to get Android screen properly. >>> >>> >> > Currently we are working in touchscreen . We are using ads7846 touch >>> >> > screen controller. >>> >>> >> > We have tested Touch screen through tslib calibration after linux >>> >> > booting. Its able to sense it. >>> >>> >> > But in Android it should not able to sense the proper positions. >>> >>> >> > we would like to know , how the xmin, xmax, ymin and ymax parameter >>> >> > values are calculated for the new LCD resolution? >>> >>> >> > ie For 480 x 272 the following values are given in the board file >>> >>> >> > struct ads7846_platform_data ads7846_config = { >>> >> > //#ifdef CONFIG_ADS_SCALED_EV >>> >> > .x_min = 0, >>> >> > .y_min = 0, >>> >> > .x_max = 3800, >>> >> > .y_max = 3800, >>> >> > //#else >>> >> > // .x_max = 0x0fff, >>> >> > // .y_max = 0x0fff, >>> >> > //#endif >>> >>> >> > .x_plate_ohms = 180, >>> >> > .pressure_max = 255, >>> >> > .debounce_max = 20, >>> >> > .debounce_tol = 10, >>> >> > .debounce_rep = 1, >>> >> > .get_pendown_state = ads7846_get_pendown_state, >>> >> > .keep_vref_on = 1, >>> >> > .settle_delay_usecs = 150, >>> >> > }; >>> >>> >> > We would like to know for the new LCD 800 x 480 , how this value >>> >> > should be calculated? >>> >>> >> > ---Gokul >>> >>> >> > -- >>> >> > unsubscribe: android-porting+unsubscr...@googlegroups.com >>> >> > website:http://groups.google.com/group/android-porting >>> >>> >> > To unsubscribe, reply using "remove me" as the subject. >>> >>> > -- >>> > unsubscribe: android-porting+unsubscr...@googlegroups.com >>> > website:http://groups.google.com/group/android-porting >> >> -- >> unsubscribe: android-porting+unsubscr...@googlegroups.com >> website: http://groups.google.com/group/android-porting >> > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
