ParaView:Plugin Deployment with Development Installs: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
| Line 3: | Line 3: | ||
New in version 3.8, we are now providing Development packages of ParaView. The primary purpose of these packages is to provide the necessary libraries and headers for one to build and deploy plugins that are binary compatible with the release ParaView binaries available on the download page. | New in version 3.8, we are now providing Development packages of ParaView. The primary purpose of these packages is to provide the necessary libraries and headers for one to build and deploy plugins that are binary compatible with the release ParaView binaries available on the download page. | ||
=Disclaimer= | ===Disclaimer=== | ||
* The Development install includes no debugging symbols and is built Release mode with the same compiler flags as the ParaView binaries. | * The Development install includes no debugging symbols and is built Release mode with the same compiler flags as the ParaView binaries. | ||
* The Development install | * The Development install | ||
Revision as of 17:18, 3 June 2010
Development Installs
New in version 3.8, we are now providing Development packages of ParaView. The primary purpose of these packages is to provide the necessary libraries and headers for one to build and deploy plugins that are binary compatible with the release ParaView binaries available on the download page.
Disclaimer
- The Development install includes no debugging symbols and is built Release mode with the same compiler flags as the ParaView binaries.
- The Development install
