Over the years, a few parties have wanted to be able to build Open MPI components outside of the official source tree (e.g., they are developing their own components outside of OMPI's SVN). We've typically said "use --with-devel-headers", but a) never really provided a full example of how to do this, and b) never acknowledged that using --with-devel-headers is somewhat of a pain.
That ends now. :-) I am publishing a bitbucket repo of three example "tcp2" BTL components. They are almost exact copies of the real TCP BTL component, but have had their configury updated to enable them to be built outside of the Open MPI source tree: 1. A component for the v1.4 Open MPI tree 2. A component for the v1.5/v1.6 Open MPI tree 3. A component for the trunk/v1.7 (as of r24265) Open MPI tree Each of these example components support the --with-devel-headers method as well as a new method: --with-openmpi-source=DIR (i.e., where you specify the corresponding Open MPI source directory, and the component builds against that). There are three different components because the configury between each of them are a bit different. Look at the configure.ac in the version that you care about to see examples of how to get the relevant CPPFLAGS / CFLAGS that you need to build your component. Here's the bitbucket repo: https://bitbucket.org/jsquyres/build-ompi-components-outside-of-source-tree There's a top-level README.txt file in the repo that explains a bit more. Enjoy! -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
