-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source code for Python Zorba api? #8
Comments
Michael,
The python port is generated by swig from the .i files.
See:
https://github.com/zorba-processor/zorba/tree/master/swig/
and
https://github.com/zorba-processor/zorba/tree/master/swig/python
Cezar
…On Wed, Jul 5, 2017 at 9:56 AM, Michael Estwik ***@***.***> wrote:
We are currently working on to get Zorba api working for Python 3.4+ and
it seems problematic to import the _zorba_api.pyd file.
Is there any way we can get the source code for that file and make it work
for Python 3.4+?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#8>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AApPXhP5IreuwXrNclFQFVpemf7meDjxks5sK6QHgaJpZM4OOdF3>
.
|
Thank you! But one question, where is the interface file that is mentioned in the zorba_api.py?
Also, that file is created for Python 2.7 and not 3.x. |
Also on more question, how do I build the file with Swig? We haven't touched Swig before. |
Michael,
If you have the swig packages installed on your computer as described in:
http://www.zorba.io/documentation/latest/zorba/build/build_prerequisites
You should just run the regular build cmake .. and make, and the make
scripts will call the swig compiler to generate python bindings according
to the .i files that are the input for the swig compiler.
For python 3 you might need to debug the build and get into the swig
details to generate the appropriate bindings. Let us know how it went.
Cezar
…On Thu, Jul 6, 2017 at 4:28 AM, Michael Estwik ***@***.***> wrote:
Also on more question, how do I build the file with Swig? We haven't
touched Swig before.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AApPXtAvxrnW7J3lI_sDohEzxWAI3D0fks5sLKjCgaJpZM4OOdF3>
.
|
I managed to build it with the following packages:
And used the command: The problem is that in the swig/python folder, I only get header files and no api file for python. I'm trying to read the documentation of the Zorba but there are to many broken links and I can't get any further. And yes, there are som errors with missing headerfiles (will include it in a seperate comment) |
CMakeError.log: |
You are working on Windows, were you able to compile Zorba in first instance?? |
let me try to get a working version for you... |
Yes, I have a working example of Zorba on my computer. I found out that it could be easier to build this on Linux, but we are not using Linux at my workplace. That would be great, thank you. |
Michael, did you try the binaries from github?
https://github.com/zorba-processor/zorba/releases
…On Tue, Jul 25, 2017 at 3:56 PM, Michael Estwik ***@***.***> wrote:
Yes, I have a working example of Zorba on my computer.
Yes, I did install an instance of iconv.h but it didn't wan't to find it,
but it does find it during the building process - which is quite weird.
I found out that it could be easier to build this on Linux, but we are not
using Linux at my workplace.
That would be great, thank you.
I think others would appreciate that as well.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AApPXmV8x21QWerMFieAdwJU5sneMNy8ks5sRlZqgaJpZM4OOdF3>
.
|
We are currently working on to get Zorba api working for Python 3.4+ and it seems problematic to import the _zorba_api.pyd file.
Is there any way we can get the source code for that file and make it work for Python 3.4+?
The text was updated successfully, but these errors were encountered: