[petsc-dev] BuildSystem concerns

[Matthew Knepley]

On Tue, Mar 15, 2011 at 7:06 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:

>
>  Stuff like this in BlasLapack.py
>
>  def getSharedFlag(self,cflags):
>    for flag in ['-PIC', '-fPIC', '-KPIC', '-qpic']:
>      if cflags.find(flag) >=0: return flag
>    return ''
>
>  def getPrecisionFlag(self,cflags):
>    for flag in ['-m32', '-m64', '-xarch=v9','-q64']:
>      if cflags.find(flag) >=0: return flag
>    return ''
>
>  def getWindowsNonOptFlags(self,cflags):
>    for flag in ['-MT','-MTd','-MD','-threads']:
>      if cflags.find(flag) >=0: return flag
>    return ''
>
>
> are of major concern. So someone adds a new "precision" flag in BuildSystem
> they have to know to go into BlasLapack.py and edit it?


Is the intent to deal with crappy flags from users here? If not, we can use
the information about
precision and shared libraries from modules rather than from flags. Do not
know about Windows.

   Matt


>
>   Barry
>
-- 
What most experimenters take for granted before they begin their experiments
is infinitely more interesting than any results to which their experiments
lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110315/e11c6c6f/attachment.html>