On 8/2/07, Joel B. Mohler <[EMAIL PROTECTED]> wrote:
> That certainly isn't likely to happen for the uses of sage_c_lib so far. Most
> of it is pretty random bizarre stuff that was difficult from pyrex for some
> reason (C++ wrappers and other such stuff).
>
> I think this is quite reasonable to put this in the main repository supposing
> that setup.py can be coerced into building it. I'll look into that tomorrow,
> but hints on setup.py building c libraries would be nice if anyone has any.
I actually just envisioned maybe doing something like
os.system('cd c_lib; make')
but maybe slightly more sensible, e.g., catch an error if make fails.
William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
