What steps will reproduce the problem?
1. Create a new library, try to use distorm from inside that library.
What is the expected output? What do you see instead?
Since the new library project also #defines _LIB in the project settings,
the distorm exports are preprocessed out of the header file.
Usually this is solved by giving the _LIB macro a unique name, for example
_LIB_DISTORM3 to prevent collisions.
What version of the product are you using? On what operating system?
r48, msvc2008.
Original issue reported on code.google.com by ianp...@gmail.com on 12 May 2010 at 10:58
Original issue reported on code.google.com by
ianp...@gmail.com
on 12 May 2010 at 10:58