Differences
This shows you the differences between two versions of the page.
|
ndk:assignments:warmup [2014/03/22 10:44] petre.eftime [Warm-up assignment] |
ndk:assignments:warmup [2014/03/22 11:42] (current) petre.eftime [Description] |
||
|---|---|---|---|
| Line 42: | Line 42: | ||
| === Library === | === Library === | ||
| - | . | + | |
| The service should use a native library for archiving and unarchiving. Make an API to your liking, but the implemented functionality should be as follows: | The service should use a native library for archiving and unarchiving. Make an API to your liking, but the implemented functionality should be as follows: | ||
| * Functions for archiving and unarchiving. The archive can be in any format but it must preserve relative paths and the contents of the files, including empty directories. Permissions and ownership are not important. | * Functions for archiving and unarchiving. The archive can be in any format but it must preserve relative paths and the contents of the files, including empty directories. Permissions and ownership are not important. | ||
| * Functions for getting the file names and paths in an archive. | * Functions for getting the file names and paths in an archive. | ||
| * The archive should be compressed (android comes with libzlib by default) | * The archive should be compressed (android comes with libzlib by default) | ||
| - | * It is desirable that the archives are in a standard format (zip, tar, tar.gz, 7zip, etc). You can use external libraries, but the source must be available. | + | * It is desirable that the archives are in a standard format (zip, tar, tar.gz, 7zip, etc). You can use external libraries, but the source code for them must be available. |
| - | The library should be compilable and runnable on x86. | + | The library should be compilable and runnable on x86 processors. |
| ==== Points ==== | ==== Points ==== | ||
