ok. I have fixed this now. Take a look again.

Tue Jan 06 2015 at 1:43:56 PM skrev Martin Sandve Alnæs <[email protected]
>:

>  Talked to Johannes: just adding all the variables to fenics.conf in both
> scripts should do the trick.
>
> On 6 January 2015 at 13:32, Anders Logg <[email protected]> wrote:
>
>> Yes, I'm aware of this problem.
>>
>> Any suggestion for how it should be solved? I want something that helps
>> me (us) to set the right variables.
>>
>>  How about the first script writing fenics.conf and the second writing
>> dolfin.conf?
>>
>>  --
>> Anders
>>
>>
>> Tue Jan 06 2015 at 1:29:11 PM skrev Martin Sandve Alnæs <
>> [email protected]>:
>>
>>>  I see one problem: They both unconditionally copy a config file to
>>> ${FENICS_INSTALL_PREFIX}/fenics.conf
>>> but the config files generated by the two scripts differ.
>>> This means e.g. reinstalling ffc after dolfin will break the dolfin
>>> config.
>>>
>>>  Martin
>>>
>>>
>>>    On 6 January 2015 at 12:56, Anders Logg <[email protected]> wrote:
>>>
>>>> Following the discussion yesterday on workflows for HashDist, I have
>>>> added a new script named
>>>>
>>>>      fenics-dev-install.sh
>>>>
>>>>  to DOLFIN and FFC.
>>>>
>>>>  I have tried to incorporate suggestions from Martin and Johannes
>>>> after the initial draft I committed yesterday.
>>>>
>>>>  Check it out and see if it is useful. Feel free to commit changes but
>>>> please try to keep the two versions of the script as close as possible: the
>>>> CMake-version (for DOLFIN) and the distutils version (for all other
>>>> packages). The idea is that this script should reside in all our packages
>>>> so changes made in one package need to manually be copied to and committed
>>>> in other packages. (Hopefully, changes will be rare.)
>>>>
>>>>  PS: This script is really not related to HashDist at all, the
>>>> discussion just started out that way. So this is merely an improved version
>>>> of cmake.local that also covers our Python packages.
>>>>
>>>>  --
>>>> Anders
>>>>
>>>>
>>>>       _______________________________________________
>>>> fenics mailing list
>>>> [email protected]
>>>> http://fenicsproject.org/mailman/listinfo/fenics
>>>>
>>>>
>>>
>
_______________________________________________
fenics mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics

Reply via email to