>All and all, as a start, interested users will have to create
>builds file to replace current ones. Such build files should be
>able to create native and cross build Harbours targeted for
>both emulator and native devices:
> win -> win emulator
> win -> linux device
> linux -> linux emulator
> linux -> linux device
> osx -> osx emulator
> osx -> linux device
>Viktor
What differences from gcc and gccarm in android term?
Which os result cgywin?
>Where "emulator" usually means x86 and "device" usually
>means "ARM" CPU, but I'm not sure if it's even further
>fragmented and there exist f.e. x86 android devices.
>Most similar (hybrid) build scenarios so far are vxworks,
>symbian and cygwin, but none that complicated.