[Qt-embedded-interest] Difference between -embedded and -xplatform?

[Tom Cooksey]

> On Mar 31, 2009, at 2:12 AM, Tom Cooksey wrote:
> > So, -embedded sets the architecture (To
> > enable the correct inline assembly) and -xplatform sets the mkspec
> > if you need
> > something other than the default.
>
> So does that mean if you set -xplatform you should also set -embedded
> for the proper assembly code? 

Yes, it sounds like you need both -embedded mips and -xplatform qws/linux-my-
platform. Note: The platform name must start with "linux-".

> What's the requirement for a cross-
> compile with a custom toolchain? In my case, I am use a proprietary
> manufacturer distributed toolchain for their custom version of MIPS32.

It depends if you need anything other than system libraries (gstreamer for 
phonon, tslib, etc). If you only need essentially libc, then you can simply 
add sym-links called mips-linux-* to your toolchain and make sure they're in 
your path. That way you don't need -xplatform at all. Alternetively, if you 
also want to use some custom CFLAGS or add some custom include paths (for E.g. 
tslib), you can create a mkspec for your toolchain in mkspecs/qws using one of 
the existing specs as an example.


Cheers,

Tom