I'd like to add the instant cache dir to the profile, is it ok if we add
someting like
export INSTANT_CACHE_DIR=\${FENICS_INSTALL_PREFIX}/instant_cache
export INSTANT_CACHE_DIR=\${FENICS_INSTALL_PREFIX}/cache/instant
?
This will allow separation of python 2 and 3 caches, and doing instant-clean
regularly on a dev install without wiping the production cache.
It's tricky to place it in ~/.cache/instant/<foo> because it's hard to
define a good 'foo'.
Martin
On 6 January 2015 at 14:40, Anders Logg <[email protected]> wrote:
> Good!
>
>
> Tue Jan 06 2015 at 2:26:35 PM skrev Martin Sandve Alnæs <
> [email protected]>:
>
>> The scripts are now identical. I just checked for the existence of
>> setup.py or CMakeLists.txt.
>>
>> On 6 January 2015 at 14:15, Martin Sandve Alnæs <[email protected]>
>> wrote:
>>
>>> I'm on it. Just had a little bughunt, my bash is not very good.
>>>
>> On 6 January 2015 at 14:05, Anders Logg <[email protected]> wrote:
>>>
>> Good. Can you make the corresponding change to the DOLFIN version of the
>>>> script?
>>>>
>>>> It's important to keep both scripts as close as possible.
>>>>
>>>> We might consider actually making the scripts identical with some
>>>> if-clause to select either distutils or Cmake. What do you think?
>>>>
>>>>
>>>> Tue Jan 06 2015 at 2:00:24 PM skrev Martin Sandve Alnæs <
>>>> [email protected]>:
>>>>
>>>>> Added some more missing ones plus
>>>>> FENICS_PYTHON_EXECUTABLE
>>>>> FENICS_PYTHON_VERSION
>>>>>
>>>>>
>>>>> On 6 January 2015 at 13:52, Anders Logg <[email protected]> wrote:
>>>>>
>>>>>> 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
