Reply
Thread Tools
Copernicus's Avatar
Posts: 1,986 | Thanked: 7,697 times | Joined on Dec 2010 @ Dayton, Ohio
#11
Originally Posted by blue bottle View Post
my 'app' is written in C (not much interaction with the UI) and requires that some changes have been made at the kernel level.
Hmm. I've honestly never written any code that requires intimate knowledge of what the kernel is doing, let alone modifying that behavior; are you certain you can't run your program in userland?

2. Since my 'app' uses a number of C libraries, what is the best way to adapt my 'app' so that is can run on N9?
If you've got a command-line C program, you really shouldn't need to do any adaptation at all -- both the N900 and the N9 are running Linux, after all. The only significant difference between the two, for most apps anyway, is the user interface. If you've got a dependency on specialized libraries, that might be a problem, if they haven't been ported to the N9 yet. (And if you really really do have a dependency on a customized kernel, well, I just don't know what you are trying to build...)
 

The Following User Says Thank You to Copernicus For This Useful Post:
Copernicus's Avatar
Posts: 1,986 | Thanked: 7,697 times | Joined on Dec 2010 @ Dayton, Ohio
#12
Originally Posted by Mike Fila View Post
This is not correct the only part of qt that can be ported with minimal effort are apps built only using qt quick any other components have to be basically rewritten.
Certainly, Qt-based code must be ported from one device to another; we are talking C++ here, not Java. But the big problem with Symbian is that only a relatively small portion of Qt is supported on it; I think that's the main reason why they push so hard to get Symbian folks to use Qt Quick instead.

For many apps, going from, say, Windows to Linux becomes a heck of a lot easier to do if you don't have to rewrite the user interface. Implementing your UI in Qt makes life much, much easier.
 
Reply


 
Forum Jump


All times are GMT. The time now is 04:24.