[petsc-dev] switch petsc-dev to use --with-shared-libraries by default?

[Barry Smith]

On Jun 1, 2012, at 1:18 PM, Satish Balay wrote:

> I think the problems come from different types of externalpackage
> usages. [for ex: mpi not built shared]. Also we don't explicitly build
> all externalpackages shared - and this can cause grief in some
> cases. [they just get pulled into libpetsc.so]
> 
> We had this default for a while and then gaveup. But now that we
> default to --with-single-library=1 - some of those issues don't bite
> us..

   Maybe after the release is well tested we can try changing the default in the nightly builds.

   Note that making --with-shared-libraries=1 the default doesn't need to mean that shared library works on every two-bit obscure machines. On machines where shared libraries don't work the user would just us --with-shared-libraries=0


   Barry

> 
> Satish
> 
> On Fri, 1 Jun 2012, Barry Smith wrote:
> 
>> 
>>    Is it time to change in petsc-dev the default of --with-shared-libraries to true by default? It is a nicer user experience to use shared libraries (much faster link of executable for example).
>> 
>>    Does it work pretty much everywhere?
>> 
>>   Barry
>> 
>> 
>> 
>