-
Notifications
You must be signed in to change notification settings - Fork 50
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
64Bit version of XLL add in #6
Comments
Sorry, I don't have an ETA on this since I don't currently have access to a version of Excel 2010. |
Out of interest couldn't you use the 30 day trial to do a build ? I tried doing it myself but ran out of skill / knowledge as it was complaining about some deprecated code and also a missing include (JDK related I think) |
That might help for the initial version but for any bugs or future versions it would be tricky. So not really an option. |
BTW - is there any chance you can do a quick document on how to compile the addin from the source code, hopefully I can then compile a 64bit version and push it back into the project for you (assuming no major issues) |
There should be no special setup. Just visual studio (2005 and above). Open the solution file and build. |
Will give it a try in the next couple of days and report back, thanks again. |
Ok I'm stuck on an issue with the build
After some googling around I didn't get any further but look to have setup my build correctly to Release and x64. There are also 131 additional warnings to do with deprecated functions (sprintf, strdup, strcpy) Again any help or thoughts appreciated, I love the XLLoop project and have some handy PHP code talking to a Mongo DB which works great on 32Bit, but I do need 64Bit support. ;-) |
You'll have to use the visual studio runtime library for 64bit. Same for the other libs here as they are all 32 bit. Take a look at my other project's build file. It has 32 and 64 bit support: https://github.com/poidasmith/winrun4j/blob/master/WinRun4J/build/WinRun4J.vcproj |
I managed to compile XLLoop for x64 use under Windows 8. |
Yeah, would be interesting to see what code/project/build changes were required to get this working. Perhaps as a patch? |
Great - but how? |
Hey mostbit, well done for building a 64bit version! I'll be happy to help you test it. I'm stuck on a 64bit machine at the moment which breaks the xlloop add-in. Sadness. It was working brilliantly on the 32bit machine I was using last week. Unfortunately I don't have build enviornment (Visual Studio) on this machine, but I would be so happy to get it running again. Thanks! |
Hi mostbit, would you like to send whole project to me via my email: [email protected]? Thanks a lot! |
Hi,
|
Hi Kay, many thanks for your kind help.
|
I would love to have a copy as well, why don't you share it on github. — On Fri, Feb 13, 2015 at 6:21 AM, zenchanhk [email protected]
|
You are right - I was about to share it on github but I failed,
|
Ok, First create yajl for x64. You get the source package lloyd-yajl-1.0.12-0-g17b1790.zip from sourceforge
updating the XLLoop x64:
get the following LIBs from the internet: I will follow up with the x64bit-project files once I get my Visual Studio running again. |
Hi Kay, Many thanks again for your so prompt response. But I don't have Visual 2015-02-14 3:08 GMT+08:00 mostbit [email protected]:
|
can anybody put the 64bit up for download please? Possibilities for people not familiar with github:
|
Would you be so kind to share the 64bit project files? Probably open up a fork on github to share patches, etc. Thanks alot! |
I generated now a x64 Xlloop and started a "pull request" to commit to github. Please check if my commit was succesfull. As I mentioned above: I am new to github and I tried my very best... |
Thanks alot for your help, mostbit. Unfortunately it seems that your repo is even with the master of poidasmith, I cannot see any changes to the project you have made in your master repo. Can you please verify that you have committed all changes to your master branch on github? btw. - i have seen that you created your pull request against the V0_3_3_BRANCH branch. was that intended or did you do this by accident? Cheers! |
Yes, my commit to V0_3_3_BRANCH was by accident. |
Hello mostbit, it seems that you removed your xlloop repo, can you please re-add? Cheers! |
How is it possible to contact user privately in github? |
sure, drop me an email to [email protected] .... |
I've found a package with a subfolder called xlloop-addin-x64. It compiled under Visual Studio 2013, and the 64 bits xll works well with Excel 2013 64bits. Only flaw: a message error when Excel exits, but probably it depends from the python server, and it was already mentioned. Luckily, the server doesn't stop. |
@mostbit Do you have the 64bit add-in available? |
@bernardorusso we've done it and published it here: https://github.com/PATRONAS/xlloop |
Here is the dll, compiled to 64 bit and with a function table allowing 10000 exposed functions, plus some files using the python server (with, more or less, the usual packages: numpy, scipy, alglib). Also included an Excel test workbook (requires the server started before). Let me know if it works for you: to pass the .sln file and the source tree requires some cleanup that I can't do right now. Da: Bernardo Russo Guedes [email protected] @mostbithttps://github.com/mostbit Do you have the 64bit add-in available? You are receiving this because you commented. |
Anybody has a compiled 64bit version working? Apparently this guy https://github.com/PATRONAS/xlloop has the project configured for 64 bit but do not provide compiled releases. I'm really trying to avoid MS Visual Studio... Thank you in advance. |
Same here. I'm looking for 64bit as well. Thanks. I will try put that into github if anyone can send me the 64 bit compiled version. Thanks |
Hi all, I'm also looking for a 64bit compiled file aswell. Is there someone who has it available? |
As per the thread regarding the testing on Excel 2010 do you know when there will be a 64bit version of the XLLoop Excel plugin available to test / use ?
The text was updated successfully, but these errors were encountered: