dorsal team mailing list archive

[Harish Narayanan <harish.mlists@xxxxxxxxx>]

On 8/3/11 10:13 AM, Johannes Ring wrote:
> On Wed, Aug 3, 2011 at 10:09 AM, Harish Narayanan
> <harish.mlists@xxxxxxxxx> wrote:
>> On 8/3/11 9:56 AM, Johannes Ring wrote:
>>> On Mon, Jul 25, 2011 at 1:46 AM, Benjamin Kehlet <benjamik@xxxxxxxxx> wrote:
>>>> When building Trilinos to see the newly installed Python (also
>>>> installed by Dorsal). The reason is apparantly that the cmake routine
>>>> FindPythonInterp sees the systemwide  installation of python before
>>>> the new locally installed python interpreter.
>>>>
>>>> Is it possible that Dorsal can handle this the same way as it handles
>>>> Swig? This means
>>>> * Add to python.package
>>>> package_specific_register() {
>>>>  export PYTHON_EXECUTABLE=${INSTALL_PATH}/bin/python
>>>> }
>>>>
>>>> * Add to trilinos.package
>>>> if [ -x "${PYTHON_EXECUTABLE}" ]; then
>>>>    CONFOPTS="${CONFOPTS} -D PYTHON_EXECUTABLE:FILEPATH=${PYTHON_EXECUTABLE}"
>>>> fi
>>>
>>> Yes, it should be possible, but probably not enough. We would also
>>> need to define PYTHON_INCLUDE_DIR and maybe also PYTHON_LIBRARY on
>>> some platforms. This will also need to be added in (at least)
>>> ufc.package and dolfin.package. Does any of the supported platform
>>> files require Python to be built from source?
>>
>> No.
> 
> Ok. Then I'm not sure it is worth it?

If any of this is really necessary, someone who is interested in
supporting a non-standard platform has to commit to making and
maintaining relevant changes. So Benjamin, if you really want to do
this, you can. It is just that you need to be the one supporting the
changes because others working on Dorsal do not have SLED/opensuse to
test on.

Harish