On 03/05/11 15:51, Steven Booth wrote:
Thanks, Chris, and Peter, for your responses. Yes, I read the readme.txt file in the 'vc8' directory in the release folder. I am slowly making progress on this. I was a MS Solution Provider and a Partner for many years before I saw the light ( :) ), so I'm aware of the vagaries of binary incompatibility. I think the real problem isn't the header files, per-se (they are just text, after all), but rather the calling sequences to the procedures defined in the DDImage.dll and glew32.dll files included with Nuke, and which Nuke assumes we all are using.
That's not really the case though - the issue is mainly the STL headers which ship with devstudio which use the Dinkum STL library. MS has changed these pretty much with every version of their compiler -> 7.0 -> 8.0 -> 9.0, to do things like change from copy-on-write to ref-counting (strings), so depending on what version you use, different things might happen if you're using std::strings, std::sets, or std::vectors.
If you're not using anything in DDImage which uses any of the above containers, you'd probably get away with it, but if you do need any of that stuff, I'd be very surprised if there wasn't a crash somewhere down the line.
Peter -- Peter Pearson, Software Engineer The Foundry, 6th Floor, The Communications Building, 48 Leicester Square, London, UK, WC2H 7LT Tel: +44 (0)20 7434 0449 - Fax: +44 (0)20 7434 1550 Web: www.thefoundry.co.uk The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027 _______________________________________________ Nuke-dev mailing list [email protected] http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
