Maybe I threw into much info...
I understand I still need all the CRT/MFC and other platform headers,libs,compiler etc...
I sure need the VS2005 build tools, currently they are on the system because VS2005 is installed.
I was hoping I can target the vs80 toolset by using a build/develop-machine with:
-only VS2010 and an older Windows Platform SDK installed (which also contains all build tools of VS2005), but not the VS2005 IDE itself.
-or even better: only VS2010 installed and an xcopy version of CRT/MFC-headers and libs/compiler/linker/... (and thus have a 'portable'-like set of the VS2005 buildtools, in the end we just need to call cl.exe and link.exe with correct parameters and some envVars set... Correct?)
I understand I still need all the CRT/MFC and other platform headers,libs,compiler etc...
I sure need the VS2005 build tools, currently they are on the system because VS2005 is installed.
I was hoping I can target the vs80 toolset by using a build/develop-machine with:
-only VS2010 and an older Windows Platform SDK installed (which also contains all build tools of VS2005), but not the VS2005 IDE itself.
-or even better: only VS2010 installed and an xcopy version of CRT/MFC-headers and libs/compiler/linker/... (and thus have a 'portable'-like set of the VS2005 buildtools, in the end we just need to call cl.exe and link.exe with correct parameters and some envVars set... Correct?)