Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] Building Open MPI components outside of the sourcetree
From: Jeff Squyres (jsquyres) (jsquyres_at_[hidden])
Date: 2011-01-19 19:39:23


I'd rather not setup another SVN repo. Where should it go in the current OMPI SVN?

Sent from my PDA. No type good.

On Jan 19, 2011, at 5:01 PM, "George Bosilca" <bosilca_at_[hidden]> wrote:

>
> On Jan 19, 2011, at 16:44 , Jeff Squyres wrote:
>
>> Where should it be on the main web site?
>
> The Documentation section look like a good place to me.
>
>> It needs to be in a repo somewhere; it may change over time.
>
> The source code can be hosted at Indiana in the same way ompi-tests and ompi-docs are hosted. However, I don't expect this code to drastically change every other day, so providing a tar on a webpage should be good enough. To be more precise on this point, as we only allow big modification of the build system between major releases I expect to only maintain 3 template (stable, unstable and trunk).
>
> george.
>
>>
>>
>> On Jan 19, 2011, at 4:38 PM, George Bosilca wrote:
>>
>>> This stuff should be directly on the main Open MPI website. Not as a link to bitbucket, but as a webpage and 3 tars.
>>>
>>> george.
>>>
>>> On Jan 19, 2011, at 15:43 , Jeff Squyres wrote:
>>>
>>>> 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
>>>> jsquyres_at_[hidden]
>>>> For corporate legal information go to:
>>>> http://www.cisco.com/web/about/doing_business/legal/cri/
>>>>
>>>>
>>>> _______________________________________________
>>>> devel mailing list
>>>> devel_at_[hidden]
>>>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>>>
>>>
>>> _______________________________________________
>>> devel mailing list
>>> devel_at_[hidden]
>>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>>
>>
>> --
>> Jeff Squyres
>> jsquyres_at_[hidden]
>> For corporate legal information go to:
>> http://www.cisco.com/web/about/doing_business/legal/cri/
>>
>>
>> _______________________________________________
>> devel mailing list
>> devel_at_[hidden]
>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>
>
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/devel