msvs2003 problem(s)
msvs2003 problem(s)
i have recently been fighting to compile subset of celestia files i wanned to play with on visual studio 2003 (the one that intoduced solutions). ususally it imports older dsw/dsp just fine, but this time it could not import any of celestia project files (said they are "broken"). this is something for you to think about. also, I had to define windows version for debug funcs to be linked (maybe you had it in dsp, but isn't it better to put it in source? or maybe it's because i had no psdk... but, since it links now, i assume psdk has little to do with it). finally, it cries about size_t or __int64 to int lossy conversions all over the code; could be that basictypes.h is included in the wrong place, but check (i simply pragma-disabled them all).
-
- Posts: 2
- Joined: 18.11.2008
- With us: 16 years
Re: msvs2003 problem(s)
It seems to me that it's better to implement own stroke's for MS VC
2003 in order not to change library sources and don't assume that library
will not rely on stored states.
2003 in order not to change library sources and don't assume that library
will not rely on stored states.