Skip to content
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

1.7.x Compatibility? #120

Open
dave-fl opened this issue Mar 3, 2016 · 19 comments
Open

1.7.x Compatibility? #120

dave-fl opened this issue Mar 3, 2016 · 19 comments

Comments

@dave-fl
Copy link

dave-fl commented Mar 3, 2016

Will this work with 1.7.x? Getting a bunch of warnings during DLL compilation process.

@dpinte
Copy link
Member

dpinte commented Mar 3, 2016

@david-wolf it should work fine as 1.7 did not had major changes. If you can repot specific warnings or errors, that would help.

@dave-fl
Copy link
Author

dave-fl commented Mar 3, 2016

FAILED (failures=4, errors=1, skipped=1)

test_results.txt

@dave-fl
Copy link
Author

dave-fl commented Mar 3, 2016

Fixed the error in the test case. Warnings but it passed. Would like to know reason for the failures.

test_results.txt

@dpinte
Copy link
Member

dpinte commented Mar 3, 2016

I'll look into the details. From a quick review, can you confirm you build the QL DLL as explained in the doc? In particular the point 1 in this section https://github.com/enthought/pyql/blob/master/docs/source/getting_started.rst#installation-from-source-on-windows

@dave-fl
Copy link
Author

dave-fl commented Mar 3, 2016

Yes I did. Those steps seem to guarantee that if followed correctly the program will run - not its program correctness.

I had some issues initially with the DEF file which prevented compilation but I went back and fixed that.

@dave-fl
Copy link
Author

dave-fl commented Mar 3, 2016

Note I used QL 1.7.1, MSVC 14 and Anaconda latest version with Python 3.5.

Those settings have some issues too. First you are not updating a settings.py file you are updating a C++ file. Second you require Cygwin to be installed specifically with NM which is part of binutils.

@dave-fl
Copy link
Author

dave-fl commented Mar 3, 2016

Full build output.
build_output.txt

@dpinte
Copy link
Member

dpinte commented Mar 17, 2016

Thanks @dave-fl for the report. I'll investigate asap.

@bigtan
Copy link

bigtan commented Mar 18, 2016

build_output.txt

I got the similar output as @dave-fl, But I failed the comiling. The error log is listed in the txt file.

I used the nm from the mingw, maybe this is the reason, or should I try cygwin?

@dpinte
Copy link
Member

dpinte commented Mar 18, 2016

I think we should investigate the https://github.com/enthought/pyql/blob/master/scripts/generate_symbols.py and check if it does its job correctly. It has been designed on Python 2.7 and known to work with Python 3.3. Python 3.5. is using a new Visual Studio version that might do things in a different way ...

@dave-fl
Copy link
Author

dave-fl commented Mar 18, 2016

I used cygwin. Took a while to get the build going and then we had failed unit test cases.

@bigtan
Copy link

bigtan commented Mar 18, 2016

Hi @dpinte I use Python27 and vs2015, the .def file generated is just about 15mb. So I agree with you, Maybe something wrong with https://github.com/enthought/pyql/blob/master/scripts/generate_symbols.py

@ceaza
Copy link

ceaza commented Mar 18, 2016

Hi @bigtan , it may be something to do with fact that Python27 is compiled using vs2008, and you are using vs2015. I can compile PyQl on WinPython3.5 but not on Python2.7 and I think this was my 2.7 issue. See [https://blog.ionelmc.ro/2014/12/21/compiling-python-extensions-on-windows/].

So while I don't have much experience in this, all downstream modules would also need to be compiled in vs2008.

@bigtan
Copy link

bigtan commented Mar 18, 2016

@ceaza I will try it on my laptop, and give the feedback here.

@dpinte
Copy link
Member

dpinte commented Mar 18, 2016

@bigtan I confirme what @ceaza says. You must use the compatible MSVC version for the target Python. Python 2.7 means MSVC 2008.

@dpinte
Copy link
Member

dpinte commented Mar 18, 2016

@bigtan another comment: it is expected that the def file is a big file...

@bigtan
Copy link

bigtan commented Mar 18, 2016

@dpinte I have finished the compiling for python 35 with MSVC2015, it works well.
I am now trying to compiling it for python 27 with MSVC2008

@dave-fl
Copy link
Author

dave-fl commented Apr 5, 2016

Is this active at all?

@dpinte
Copy link
Member

dpinte commented Apr 6, 2016

@dave-fl I don't have much bandwidth at the moment. If you have some pressing needs and want to consider other options than contributor's free time, ping me by e-mail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants