Replies: 3 comments 1 reply
-
|
So I just pulled the Cpp files local which is maybe the right way to do this. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the feedback. |
Beta Was this translation helpful? Give feedback.
-
|
OK, I've finally gotten around to looking at this. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been using Clipper2 as a DLL from C++ with no problems until I called this function and got an "Unresolved" error:
Clipper2Lib::Paths64 result = Clipper2Lib::Difference(top, bottom, Clipper2Lib::FillRule::EvenOdd);My first guess is that I'm not including Clipper2_64.lib in my build. The other functions were working because they were inline functions in the headers. Difference eventually calls ExecuteInteral in a .cpp file so would need the library at link time.
However, I have Clipper2_64.lib as "Additional Dependencies" and I have its location in "Additional Library Dependences (
$(SolutionDir)..\Clipper2\DLL\CPP_DLL\x64\$(Configuration)Where SolutionDir is my project. The Lib is in the directory and the path resolves to that location for both debug and release.I'm 50% sure I've got some error keeping me from pulling the .lib file. But since I noticed the DLL export functionality is relatively new, I thought I'd check here should anyone else have an idea or recommendation?
Thanks (Clipper2 newbie)
Beta Was this translation helpful? Give feedback.
All reactions