Portability¶

take me with you

Portability
compiling for different platforms

Task has been written to go wherever g++ (a member of the gcc - Gnu Compiler Collection) can go, and where there is a POSIX standard C library and STL implementation waiting.

This means the Unix variants are covered, Windows is supported only because Cygwin provides all of the above, and there are some platforms that may or may not support task, like Symbian and the iPhone.

When building task on a Unix-like platform, it may be that task has never been built on that platform. Occasionally someone will send email saying they got task to run on "Aaa Linux", but they had to do one of the following:

1) Add an "#include <....>" line to the source somewhere.

2) Change the source from "int" to "bbbb_t" somewhere.

So if you are building task somewhere new, this is probably all you need to do, at most.

putting task in your pocket

fredde: I already do something in the line of this: I use Dropbox to store all my
different task binaries + my (encrypted) data files online. I'm too good in
leaving my USB keys behind. I could use my own webspace for hosting and
downloading/uploading the corresponding files. The benefit I have with
Dropbox is that I can "share" my task data files across all my computers. I
see the advantage of having task on a USB key as the computer doesn't need
to be connected to the Internet. But that is rarelly the case for me.
Sounds like we need a howto document for this.

pb: Fredde, I know you're not the only person who does this, for example: Richard does it and wrote about it. But the encryption part would be
nice to see. Richard, you're out there - do you encrypt?

http://blog.rfquerin.org/2008/10/07/using-task-and-dropbox-to-manage-...

USB key, portable task bundle

dropbox

SSHFS