#17605: "How to call C code from Sage" thematic tutorial
-------------------------+-------------------------------------------------
Reporter: | Owner:
ncohen | Status: needs_review
Type: | Milestone: sage-6.5
enhancement | Resolution:
Priority: major | Merged in:
Component: | Reviewers:
documentation | Work issues:
Keywords: | Commit:
Authors: | 2ad9b510df07b6f97741f934e9830b3b405401e8
Nathann Cohen | Stopgaps:
Report Upstream: N/A |
Branch: |
public/17605 |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by vbraun):
Replying to [comment:14 ncohen]:
> > Once you install the shared library into Sage you might just as well
go through `module_list.py` as well.
>
> I do not understand this comment.
Presumably you want to build a stand-alone C/C++ and Cython project
without having to install stuff into Sage. By definition, this should
exclude steps that modify Sage directly. I mentioned the code in my github
repo, this is the only way to do this currently: Write Makefile that calls
gcc and cython directly.
Also, you shouldn't build shared libraries the way you describe. Its very
platform dependent and your steps won't work under OSX, say.
--
Ticket URL: <http://trac.sagemath.org/ticket/17605#comment:15>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
