Hi Peter,
Thanks for pointing this out. Have made the changes to the example
plugin project here, so you shouldn't have to make these changes in
future releases.
Regards,
Peter.
On 11/09/2012 10:30, Peter Kaufmann wrote:
It seems to be the other way around. The NDK was built for multi byte
character sets (not Unicode), but the example plugin project uses
Unicode.
To fix this, got to the project settings and change 'Character Set' to
'Use Multi-Byte Character Set' for debug and release.
Also, change the post build step for both debug and release to
copy "$(TargetPath)" "$(USERPROFILE)\.nuke\$(TargetName).dll"
I wasn't able to test this though, I cannot run the Nuke 7 beta here
due to a licensing issue.
Best,
Peter
On 11.09.2012 10:58, Peter Pearson wrote:
On 10/09/12 21:00, villain749 wrote:
I decided to try and recompile a plugin for the Nuke 7 beta with VS
2010
(windows 7). I keep getting an error at compile time.
1>C:\Program Files\Nuke7.0v1b38\include\Build/OS/fnWindows.h(106):
error
C2664: 'GetVersionExW' : cannot convert parameter 1 from
'LPOSVERSIONINFOA' to 'LPOSVERSIONINFOW'
1> Types pointed to are unrelated; conversion requires
reinterpret_cast,
C-style cast or function-style cast
I was just wondering if this is something on my end, or if other people
are experiencing something similar?
Sounds like something unicode-related...
Looks like our stuff is built for Unicode (with Wide character
support), but the plugin you're building isn't (it's looking for the
Ascii version of the function).
Cheers,
Peter
_______________________________________________
Nuke-dev mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
