In general we should take a close look at these build flags and see if we can do the configuration run-time instead of build time.
If run-time configuration is an option (and not too expensive) we can still use build time configuration to sniff the build environment and set sensible runtime defaults, but an app should be able to set/force some of these runtime options independent of the build/target environment/OS. Laszlo -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext Kenneth Christiansen Sent: Thursday, June 17, 2010 8:05 AM To: Hausmann Simon (Nokia-D-Qt/Oslo) Cc: [email protected] Subject: Re: [webkit-qt] mobile specific features and defines I'm OK with that. Maybe we should use cellphone(|tablet, etc) instead of mobile as mobile can mean a whole lot of things? On Thu, Jun 17, 2010 at 8:03 AM, Simon Hausmann <[email protected]> wrote: > On Wednesday, June 16, 2010 Turcotte Jocelyn (Nokia-D/Oslo), wrote: >> We could segment and wrap different "mobile" features using something >> like #if ENABLE(TOUCH_INPUT) and have all these features enabled when we >> use CONFIG+=mobile. >> This would allow different settings for individual features to be >> specified when compiling for half-mobile devices. > > I like that option very much. What do the others think? > > > Simon > > _______________________________________________ > webkit-qt mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt > > -- Kenneth Rohde Christiansen Technical Lead / Senior Software Engineer Qt Labs Americas, Nokia Technology Institute, INdT Phone +55 81 8895 6002 / E-mail kenneth.christiansen at openbossa.org _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
