[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco edited a comment on issue #38: Python wrappers

2019-08-14 Thread GitBox
GuillaumeCisco edited a comment on issue #38: Python wrappers URL: https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521329526 What I tried: Using the file `test_pair_FP256BN.c` which use `CURVE_Order_FP256BN`. Creating the .so (from python wrapper generated

[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco edited a comment on issue #38: Python wrappers

2019-08-14 Thread GitBox
GuillaumeCisco edited a comment on issue #38: Python wrappers URL: https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521321028 Thanks. I need a little help on this one. If I create rom.c like: ```c #include #include #include #include

[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco edited a comment on issue #38: Python wrappers

2019-08-14 Thread GitBox
GuillaumeCisco edited a comment on issue #38: Python wrappers URL: https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521240128 Quick question, is `bls_ZZZ.py.in` a generated file? What `.py.in` stands for? could we generate a `rom_ZZZ.py.in` file?

[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco edited a comment on issue #38: Python wrappers

2019-08-14 Thread GitBox
GuillaumeCisco edited a comment on issue #38: Python wrappers URL: https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521240128 Quick question, is `bls_ZZZ.py.in` generated files? What `.py.in` stands for? could we generate a `rom_ZZZ.py.in` file?