ATTENTION: This repository has been moved and is for archival purposes only. GPSTk toolkit has been renamed to GNSSTK and has been split into two new separate repositories. GNSSTK now only contains libraries while the other repository GNSSTK-APPS contains only applications. The rename and split into libraries and applications started with version v12.0.0 on September 2021. GPSTk --> GNSSTK at https://gitlab.com/sgl-ut/gnsstk --> GNSSTK-APPS at https://gitlab.com/sgl-ut/gnsstk-apps
Per Bryan Parsons suggestion for taking a quick and dirty shot with generating Python3 bindings, I created a CustomPythonSetup.cmake file pointing to my local anaconda 3.6 installation, then built (on OS X 10.12.4) with the command:
The resulting bindings don't seem to export any symbols, although the module is about the right size (vis-a-vis the python2 bindings):
Last login: Wed Apr 12 09:25:28 on ttys004
et-imac-retina:~ sjbespa$ python
Python 3.6.0 |Anaconda 4.3.1 (x86_64)| (default, Dec 23 2016, 13:19:00)
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpstk
>>> dir(gpstk)
['__builtins__', '__cached__', '__doc__', '__file__', '__loader__', '__name__', '__package__', '__path__', '__spec__']
>>> gpstk.__path__
['/Users/sjbespa/.local/lib/python3.6/site-packages/gpstk']
Any ideas on how to attack the problem would be greatly appreciated... I see elsewhere on the GPSTK website that the current bindings were conceived "with an eye towards python 2." It would help to understand what that comment means.
Per Bryan Parsons suggestion for taking a quick and dirty shot with generating Python3 bindings, I created a CustomPythonSetup.cmake file pointing to my local anaconda 3.6 installation, then built (on OS X 10.12.4) with the command:
The resulting bindings don't seem to export any symbols, although the module is about the right size (vis-a-vis the python2 bindings): Last login: Wed Apr 12 09:25:28 on ttys004
Any ideas on how to attack the problem would be greatly appreciated... I see elsewhere on the GPSTK website that the current bindings were conceived "with an eye towards python 2." It would help to understand what that comment means.