[petsc-dev] BuildSystem concerns

[Sean Farley]

>
>  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?


This is absurd, we should be generating BlasLapack.py!

-- 
What most researchers put in their email signature is infinitely more
interesting than the rest of their message.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110315/846b4687/attachment.html>