mirror of
https://github.com/jmcnamara/libxlsxwriter.git
synced 2026-05-15 14:15:54 -06:00
[GH-ISSUE #158] Issue with Installing on Visual Studio C++ #131
Labels
No labels
awaiting user feedback
bug
cmake
cmake
docs
feature request
in progress
long term
medium term
medium term
pull-request
question
question
ready to close
short term
under investigation
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/libxlsxwriter#131
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @r-chambers on GitHub (Apr 3, 2018).
Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/158
Originally assigned to: @jmcnamara on GitHub.
Hello,
I am using the libxlsxwriter in a Visual Studio C++ project and have followed the instructions in the MSVCLibXlsxWriter project, building the library and then using it to build ExampleExe. However, when I do this, ExampleExe does not run: I get the error "The Application was unable to start correctly (0xc000007b)." I have looked this error up and it seems it might be caused by outdated libraries or by mismatches between 32-bit and 64-bit, though it is probably the former in this case.
I am using Visual Studio Community 2017 with v141 build tools, Windows 10 x64, and libxlsxwriter 0.3.8.
Thank you very much for your time, and have a wonderful day.
@jmcnamara commented on GitHub (Apr 3, 2018):
Hi,
Can you check that you set and use the 64 bit targets at all the compilation stages and that you copied the dlls from the 64bit folders? Also, check if the supplied zlib dll is 64 bit? I'm not near a PC at the moment so I cannot check.
John
@r-chambers commented on GitHub (Apr 3, 2018):
Well, I feel so stupid now! Thank you so much. I was accidentally copying the Zlib.dll and Zlib.lib from the wrong folder.
This fixed it! Thank you again, and I'm sorry for the silly Issue.
Have a good day!
@jmcnamara commented on GitHub (Apr 3, 2018):
No problem. Closing.