MEGA --- The Privacy Company --- is a Secure Cloud Storage provider that protects your data thanks to end-to-end encryption. We call it User Controlled Encryption, or UCE, and all our clients automatically manage it.

All files stored on MEGA are encrypted. All data transfers from and to MEGA are encrypted. And while most cloud storage providers can and do claim the same, MEGA is different – unlike the industry norm where the cloud storage provider holds the decryption key, with MEGA, you control the encryption, you hold the keys, and you decide who you grant or deny access to your files.

This SDK brings you all the power of our client applications and let you create your own or analyze the security of our products. Are you ready to start? Please continue reading.

In this SDK, you can find our low level SDK, that was already released few months after the MEGA launch, a new intermediate layer to make it easier to use and to bind with other programming languages, and example apps for all our currently supported platforms (Windows, Linux, OSX, Android, iOS and Windows Phone).

In the examples folder you can find example apps using:

1. The low level SDK:

• megacli (a powerful command line tool that allows to use all SDK features)
• megasimplesync (a command line tool that allows to use the synchronization engine)

2. The intermediate layer:

• An example app for Visual Studio in examples/win32
• An example app for Android (using Java bindings based on SWIG) in examples/android
• An example app for iOS (using Objective-C bindings) in examples/iOS
• An example app for Windows Phone (using Windows Phone bindings) in examples/wp8

MEGAcmd, a higher level command line application that uses the SDK to provide interactive and scriptable access to MEGA, can be found here.

There are two methods - the one we are using now for most platforms is with vcpkg and cmake, and the prior system based on autotools still works for POSIX based systems.

Some dependencies are different for each platform because the SDK uses generic interfaces to get some features and they have different implentations.

• Network (cURL with OpenSSL/c-ares or WinHTTP)
• Filesystem access (Posix or Win32)
• Graphics management (FreeImage, QT or iOS frameworks)
• Threads/mutexes (Win32, pthread, QT threads, or C++11)

This is the method that works for Windows - it also works for other platforms (and for those, autotools is also an option). We use vcpkg, cmake, and provide scripts to build the 3rd party libraries and set up the project.

• Consult contrib\cmake\3rdparty_deps.txt to see dependencies and enable/disable a particular package.
• Your 3rdParty library builds should be outside the SDK repo. You can use the same 3rdParty folder for other mega components, e.g., megasync, etc..
• To build the 3rdParty libraries with vcpkg, you can start like this:
  • mkdir 3rdParty
  • cd 3rdParty
  • git clone https://github.com/Microsoft/vcpkg.git
  • cd vcpkg
  • .\bootstrap-vcpkg.bat -disableMetrics (Windows)
  • ./bootstrap-vcpkg.sh -disableMetrics (Posix)
• Edit triplet configuration as required in the SDK:
  • contrib\cmake\vcpkg_extra_triplets<x64-windows-mega-staticdev.cmake/x64-windows-mega.cmake/x86-windows-mega.cmake> (Windows)
  • contrib/cmake/vcpkg_extra_triplets/ (Linux)
• Fix compiler and toolset selection.
  • Just comment them if you only have one VS installed. (Windows)
• Run the SDK's batch file from vcpkg folder, check options first
  • ....\sdk\contrib\cmake\build3rdparty.cmd -o x64-windows-mega (Windows)
  • ../../sdk/contrib/cmake/build3rdparty.bash x64-linux (Posix - adjust per platform)

Once the 3rdParty dependencies are built, you can start building your SDK as follows:

• Download and install CMake from https://cmake.org/download/. Mininimum required version is 3.15
• cd contrib\cmake
• mkdir cmake-build-x64 (folder names matching pattern cmake-build-* in contrib/cmake are ignored by git)
• cd cmake-build-x64
• Run CMake-gui from this folder: cmake-gui .. (Windows)
  • Click "Configure"
  • Choose your compiler etc if it prompts for that (Choose the same compiler and configurations used to generate 3rdParty)
  • Set your options and flags (though the defaults should be fine for just SDK), e.g., USE_FREEIMAGE == 0
  • Make sure UNCHECKED_ITERATORS matches the setting used in your 3rdparty (for debug, off is faster, but that can't be turned off if using Qt)
  • Click "Configure" again, and then "Generate"
  • Click "Open Project" to start Visual Studio with that .sln
• Run ccmake from this folder: ccmake .. (Posix)
  • Adjust options in ccmake in a similar way as above, using ccmake's text interface
  • Run cmake to generate projects.
  • Run make to actually build. (or whichever build system you selected, eg XCode on Mac)

For platforms with Autotools, first set up needed libraries and then the generic way to build and install it is:

sh autogen.sh
./configure
make
sudo make install

Notice that you would need Autotools installed in your system (in Linux this normally entails having autoconf and libtool packages installed).

That compilation will include the examples using our low level SDK (megacli and megasimplesync). You also have specific build instructions for OSX (doc/OSX.txt) and FreeBSD (doc/FreeBSD.txt) and a build script to automatically download and build the SDK along with all its dependencies (contrib/build_sdk.sh)

For other platforms, or if you want to see how to use the new intermediate layer, the easiest way is to get a smooth start is to build one of the examples in subfolders of the examples folder.

All these folders contains a README.md file with information about how to get the project up and running, including the installation of all required dependencies.

Install the following development packages, if available, or download and compile their respective sources (package names are for Debian and RedHat derivatives, respectively):

• cURL (libcurl4-openssl-dev, libcurl-devel), compiled with --enable-ssl
• c-ares (libc-ares-dev, libcares-devel, c-ares-devel)
• OpenSSL (libssl-dev, openssl-devel)
• Crypto++ (libcrypto++-dev, libcryptopp-devel)
• zlib (zlib1g-dev, zlib-devel)
• SQLite (libsqlite3-dev, sqlite-devel) or configure --without-sqlite
• FreeImage (libfreeimage-dev, freeimage-devel) or configure --without-freeimage
• pthread

Optional dependency:

• Libraw (libraw-dev, libraw-devel)
• Sodium (libsodium-dev, libsodium-devel), configure --with-sodium
• MediaInfoLib (optional, see third_party/README_MediaInfo.txt)

Filesystem event monitoring: The provided filesystem layer implements the Linux inotify and the MacOS fsevents interfaces.

To build the reference megacli example, you may also need to install:

• GNU Readline (libreadline-dev, readline-devel) on Mac, you will probably need to download the source and build it yourself, and adjust the project to refer to that version.

For Android, we provide an additional implementation of the graphics subsystem using Android libraries.

For iOS, we provide an additional implementation of the graphics subsystem using Objective C frameworks.

The low level SDK doesn't have inline documentation yet. If you want to use it, please check one of our example apps (examples/megacli, examples/megasimplesync).

The new intermediate layer has been documented using Doxygen. The only public header that you need to include to use is include/megaapi.h. You can read the documentation in that header file, or download the same documentation in HTML format from this link:

https://mega.nz/#!7glwEQBT!Fy9cwPpCmuaVdEkW19qwBLaiMeyufB1kseqisOAxfi8

In this version, the sync functionality is limited in scope and functionality:

• There is no locking between clients accessing the same remote folder. Concurrent creation of identically named files and folders can result in server-side dupes.

• Syncing between clients with differing filesystem naming semantics can lead to loss of data, e.g. when syncing a folder containing ABC.TXT and abc.txt with a Windows client.

• On POSIX platforms, filenames are assumed to be encoded in UTF-8. Invalid byte sequences can lead to undefined behaviour.

• Local filesystem items must not be exposed to the sync subsystem more than once. Any dupes, whether by nesting syncs or through filesystem links, will lead to unexpected results and loss of data.

• No in-place versioning. Deleted remote files can be found in //bin/SyncDebris (only when syncing to the logged in account's own cloud drive - there is no SyncDebris facility on syncs to inbound shares), deleted local files in a sync-specific hidden debris folder located in the local sync's root folder.

• No delta writes. Changed files are always overwritten as a whole, which means that it is not a good idea to sync e.g. live database tables.

• No direct peer-to-peer syncing. Even two machines in the same local subnet will still sync via the remote storage infrastructure.

• No support for unidirectional syncing (backup-only, restore-only). Syncing to an inbound share requires it to have full access rights.

The megacli example is currently not handling console Unicode input/output correctly if run in cmd.exe.

Filename caveats: Please prefix all paths with \\?\ to avoid the following issues:

• The MAX_PATH (260 character) length limitation, which would make it impossible to access files in deep directory structures

• Prohibited filenames (con/prn/aux/clock$/nul/com1...com9/lpt1...lpt9). Such files and folders will still be inaccessible through e.g. Explorer!

Also, disable automatic short name generation to eliminate the risk of clashes with existing short names.