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

Implement a new transactions map to fix address issue #14

Merged
merged 4 commits into from
Oct 11, 2021

Conversation

edimetia3d
Copy link
Owner

Comes from here: #1 (comment)

Hi guys, am using your OPC-Client SDK since about 10 years as part of our own software package for industrial controls, so I already know it quite well. Recently I also had to port our software to 64-bit, and came across similar issues as you've been facing. So after I've found out you're also working on this I just took your latest version from git (via git clone) and adapted it to my current software, and then fixed it, in the right way, so no "/HIGHENTROPYVA:NO" or alike, but all with a new transactions map, and by extending the already existing items map. Which means now handles are really handles, and not addresses anymore. Am using Qt as toolchain, and now your SDK compiles and runs properly under 32 and 64 bit, and with or without UNICODE. And both Qt5 and Qt6, and from on msvc2010 until msvc2019. Am using cmake instead of qmake, so I didn't care much about it. Am also using your SDK as one of about 10 libraries, fixed the Microsoft declarations etc., but else exactly with the revamped project you've provided. So in case anybody is interested, here is a Dropbox link to a .7z with my whole SDK folder: https://www.dropbox.com/s/uc9a8p6cnej0jqs/OPC-Client-X64.7z?dl=0

close #1

@edimetia3d edimetia3d merged commit ecb816a into master Oct 11, 2021
@edimetia3d edimetia3d deleted the fix_address_issue branch October 11, 2021 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

not reading/writing items on 64 bit version
2 participants