> I have recently commited a fair amount of changes to ParaView that > lets a developer create a functional development tree that could be > distributed. The development tree includes all the necessary headers, > libraries, CMake files and executable tools one would need for > developing ParaView branded applications and Plugins without building > your own ParaView.
Seems to have covered many issues. The includes are now landing in the correct place, but I'm still uncertain about what is or should be going on with the bin/ vs. lib/paraview-VER files on installation. I've added a note to the existing issue: http://www.paraview.org/Bug/view.php?id=8712 /mark DISCLAIMER: This electronic transmission (and any attachments thereto) is intended solely for the use of the addressee(s). It may contain confidential or legally privileged information. If you are not the intended recipient of this message, you must delete it immediately and notify the sender. Any unauthorized use or disclosure of this message is strictly prohibited. Faurecia does not guarantee the integrity of this transmission and shall therefore never be liable if the message is altered or falsified nor for any virus, interception or damage to your system. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview