search for: incorpart

...other tools are at their own risk). And, I think it also would be really cool, if you guys come up with a solution how to handle multiple VC++ x solutions/projects from the same source, possibly ranging from VC 6.0 to future releases. Another future solution could be that the VC++ x tools get incorparted into the makefile structure, as previously discussed. It appeared to me that the mingw or gunwin32 environment mixed with the VC++ x tools could be a solution. Henrik. ----Original Message Follows---- From: Jeff Cohen <jeffc at jolt-lang.org> Date: Sat, 25 Dec 2004 16:28:40 -0800 It...

It's a possibility, though it would be better to create whole separate trees for different versions of VS. It's not just the project and solutions that need to be kept separate; the object files themselves cannot be mixed between different versions of VS. There's no rush though. Trust me, C/C++ programmers will not rush to adopt Whidbey once it's released. You'd be

Hi Jeff and Morten, I was just wondering if below wisdom is true, why not prefix every solution and project file with VC71 in front of the file name to signal the case that it is only designed for that specific IDE/tool? This gives us room for comming up with other solution and project files for another MS specific IDE/tool independt of each other. Henrik. ----Original Message Follows----