-
Notifications
You must be signed in to change notification settings - Fork 0
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
How to get 64bit dll for python in windows by Makefile.win #19
Comments
From @infwinston on July 26, 2015 5:13 You should try "nmake -f Makefile.win lib" to generate .dll file. |
From @CharlesMei on July 26, 2015 8:28 @infwinston Thank you! It works! But when i use "from liblinearutil import *", it throws "AttributeError: function 'find_parameter_C' not found".When i comment "fillprototype(liblinear.find_parameter_C, None, [POINTER(problem), POINTER(parameter), c_int, c_double, c_double, POINTER(c_double), POINTER(c_double)])" in the liblinear.py, it throws no errors. But what should i do if i want to use find_parameter_C |
From @infwinston on July 26, 2015 18:7 Hi, @CharlesMei |
From @infwinston on July 27, 2015 5:20 BTW, I think the dll file in liblinear-2.01 is already 64-bit version, why do you need to re-generate the dll? |
From @CharlesMei on July 27, 2015 13:11 Hi, @infwinston Thank you! It works well! You're right, it's already 64-bit version. When i use the original dll in liblinear-2.01, it throws errors when i use "from liblinearutil import *", and it is because of the find_parameter_C problem. When i use libsvm-3.20, it needs to re-generate the dll for 64bit to solve the import error, so i thought it may need to do the same in liblinear-2.01. I'm sorry for that. |
From @CharlesMei on July 25, 2015 19:1
I want to use python interface for 64bit python in windows, but the liblinear.dll in the /windows directory seems to be 32bit one. And i can not generate 64bit dll by "nmake -f Makefile.win clean all" , this just generate exe file in /windows directory. So how can i do that?
Copied from original issue: cjlin1#12
The text was updated successfully, but these errors were encountered: