Closed williamstein closed 7 years ago
Description changed:
---
+++
@@ -7,7 +7,7 @@
# clang c
# clib cblas
# cfile myfile.c
-# cinclude super.h standard.h
+# cinclude "/usr/local/include"
Questions -- where can one put these? Must the # be there?
However this is documented, at a bare minimum typing
Is there also a directive ccflags (analogous to cflags in C)? For instance, in order to compile an spkg using FLINT, one needs a line like
#ccflags -std=c99
(1) should have been dealt via #3530, i.e. the documentation of the pragmas.
(2) is potentially still valid and I am not sure whose fault it is: Sage or Cython.
I am adding Martin and Robert to the CC field here.
Cheers,
Michael
Actually, (1) is not dealt with since it isn't necessarily easy to get to the new documentation. That should be addressed.
Note that this stackoverflow.com post points to this ticket. Apparently this is still something that could be documented within Sage better?
Reviewer: Jeroen Demeyer
Those directives should be deprecated anyway: #22461
Closing tickets in the sage-duplicate/invalid/wontfix module with positive_review (i.e. someone has confirmed they should be closed).
There are some issues with cython spyx files:
Questions -- where can one put these? Must the # be there?
However this is documented, at a bare minimum typing
should give enough information to find docs that clearly explain this cinclude, etc. directives.
CC: @malb @robertwb
Component: user interface
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/1994