-
Notifications
You must be signed in to change notification settings - Fork 39
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
Remove 'declspec's on Windows as they are currently inconsistent #42 #43
Conversation
…o#42 Signed-off-by: Andrew V. Jones <[email protected]>
@andrewvaughanj I don't have a windows system, but I feel that this change is suspicious: I've used the You say that "nothing sets EXPORT_API", which makes sense. In "classic" windows development, this Have you tried this, by any chance? |
If you set I'll try it though, but it doesn't feel right ... |
Yeah, no worky:
|
Ah! Those operators don't have the export set ... let me try that for a second! |
I see… but in your approach here, If you take a look at the structure, there's a hierarchy of cmake files CMakeLists.txt where each (sub) "API header" relies on specific API macros, e.g., Then, in common's cmake file, we'd have |
Yeah, what you wrote makes sense ... we don't want one I think there's also an issue that:
aren't "tagged" at all. However, even labelling those functions as I can try the per-module |
|
Closing. See: #44 |
This is a "hack" to fix the build issues as reported in #42. While I can't say these changes are "better", currently nothing sets
EXPORT_API
, which then means a lot ofpsychec
's code ends-up with symbols having "incorrect"declspec
s (leading to link-time issues).I'd hoped that doing
ninja install
would remove the need for manually copying the DLL in-place:but the "new" branch still expects to find
psychecsolver-exe
(from "original"), which means you can't do the install, so I can't really test that theory.Signed-off-by: Andrew V. Jones [email protected]