You should use "_WIN32" and "_WIN64" instead of "WIN32" and "WIN64".
_WIN32 is always defined in VS, regardless with the target program is 32bit or 64bit; if you are compiling a 64bit program, _WIN64 will be defined as well. See MSDN: http://msdn.microsoft.com/en-us/library/b0084kay%28v=vs.100%29.aspx On Wed, Dec 31, 2014 at 5:43 AM, Johannes Saam <[email protected]> wrote: > oh i am portable its just that this windows build helper file was giving > me grief... i think i am good i am just wondering who uses #define win64 i > only see win32 everywhere.... especially was the plugin suite supports all > OS and multiple compiler / nuke versions. > > On Tue, Dec 30, 2014 at 8:20 AM, Julik Tarkhanov <[email protected]> > wrote: > >> Modern Nuke is 64bit only, isn't it? Also, can it be that you are making >> your plugin non-portable by relying on Windows path translations >> sxclusively? ( I know this mighg not be a concern at this point, just >> curious). >> >> >> >> > On 30 dec. 2014, at 01:16, Johannes Saam <[email protected]> >> wrote: >> > >> > I have a compile/build question... >> _______________________________________________ >> Nuke-dev mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev >> > > > _______________________________________________ > Nuke-dev mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev > >
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
