Difference between revisions of "AnyWave:DeveloperCorner"
(→AnyWave compatibility) |
|||
| Line 19: | Line 19: | ||
==AnyWave compatibility== | ==AnyWave compatibility== | ||
When building a plug-in, the developer has two choices: | When building a plug-in, the developer has two choices: | ||
| − | * Build for the currently distributed | + | * Build for the currently distributed binary version of AnyWave. |
* Build for its own AnyWave version built from the sources available on github. | * Build for its own AnyWave version built from the sources available on github. | ||
| + | ===Plug-ins for the binary distributed package of AnyWave=== | ||
Pay attention that if the plug-in must work with the distributed binary versions of AnyWave it must match more requirements: | Pay attention that if the plug-in must work with the distributed binary versions of AnyWave it must match more requirements: | ||
* Qt4 must be 4.8.2 to work with the Linux debian packaged version of AnyWave. | * Qt4 must be 4.8.2 to work with the Linux debian packaged version of AnyWave. | ||
* Qt4 must be 4.8.1 to 4.8.5 to work with the Windows and Mac OS X versions. | * Qt4 must be 4.8.1 to 4.8.5 to work with the Windows and Mac OS X versions. | ||
* VTK library must be 5.4.2 to 5.8.xx (VTK 6.x will not work) | * VTK library must be 5.4.2 to 5.8.xx (VTK 6.x will not work) | ||
| + | |||
| + | The Linux and Mac versions have been built with the gcc compiler and therefore will use the glibc library. | ||
| + | On Mac systems, the XCode software must be downloaded and installer to get access to the gcc compiler. | ||
| + | |||
| + | '''ATTENTION:''' The Windows version of AnyWave was built with Visual Studio 2008. Therefore, the developed plug-in must also be built using Visual Studio 2008 for binary compatibility. | ||
| + | |||
| + | ===Plug-ins for the developer version of AnyWave=== | ||
| + | If a developer plans to build plug-ins that will stay private, it is up to him/her not to match the requirements previously mentioned. | ||
Revision as of 15:17, 25 February 2015
Contents
Welcome
This part of the Wiki is dedicated to developers who would like to implement their own plug-ins for AnyWave.
Setting up the SDK
Before developing a plug-in for AnyWave, the developer must download and build the SDK.
The SDK is available here: https://github.com/anywave/sdk
Note that you can also try to build the complete AnyWave software which includes the SDK.
AnyWave git repository is available here: https://github.com/anywave/anywave
Clone the sdk repository on your computer:
- On Linux or Mac systems this can be done in a terminal with the following command: git clone https://github.com/anywave/sdk mysdkfolder
- On Windows, we strongly suggest to install the TortoiseGit Software, freely available at https://code.google.com/p/tortoisegit/wiki/Download
Software requirements
To successfully build the SDK, at least two software must be installed on the computer:
- The Qt4 framework
- The VTK library (version 5.4.2 to 5.8 will work)
AnyWave compatibility
When building a plug-in, the developer has two choices:
- Build for the currently distributed binary version of AnyWave.
- Build for its own AnyWave version built from the sources available on github.
Plug-ins for the binary distributed package of AnyWave
Pay attention that if the plug-in must work with the distributed binary versions of AnyWave it must match more requirements:
- Qt4 must be 4.8.2 to work with the Linux debian packaged version of AnyWave.
- Qt4 must be 4.8.1 to 4.8.5 to work with the Windows and Mac OS X versions.
- VTK library must be 5.4.2 to 5.8.xx (VTK 6.x will not work)
The Linux and Mac versions have been built with the gcc compiler and therefore will use the glibc library. On Mac systems, the XCode software must be downloaded and installer to get access to the gcc compiler.
ATTENTION: The Windows version of AnyWave was built with Visual Studio 2008. Therefore, the developed plug-in must also be built using Visual Studio 2008 for binary compatibility.
Plug-ins for the developer version of AnyWave
If a developer plans to build plug-ins that will stay private, it is up to him/her not to match the requirements previously mentioned.
