tag:blogger.com,1999:blog-6628985022531866193.post9045742490839647736..comments2024-02-12T17:37:05.629+00:00Comments on The OldWood Thing: Visual C++, the INCLUDE variable and the /USEENV switchChris Oldwoodhttp://www.blogger.com/profile/18183909440298909448noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-6628985022531866193.post-14323150819851177322010-05-21T22:44:04.992+01:002010-05-21T22:44:04.992+01:00I completely agree with your comment and I suspect...I completely agree with your comment and I suspect that the Visual C++ team also believes that others consider those variables as only being for referencing 3rd Party libraries - hence the change. I guess the days of hand-written Makefiles are long gone :-)Chris Oldwoodhttps://www.blogger.com/profile/18183909440298909448noreply@blogger.comtag:blogger.com,1999:blog-6628985022531866193.post-27544510918202090402010-05-20T09:37:26.769+01:002010-05-20T09:37:26.769+01:00My point was that INCLUDE, LIB and PATH environmen...My point was that INCLUDE, LIB and PATH environment variables by sense goes more to common development environment settings (e.g., common x86-win32 settings, common arm-wince settings, etc.) While specific project dependency should better go to the project settings.<br />Though, '50+ projects' is a good counter plea from your side :)Alex Chehttps://www.blogger.com/profile/11914214520243114798noreply@blogger.comtag:blogger.com,1999:blog-6628985022531866193.post-85310289680247430942010-05-19T21:43:05.406+01:002010-05-19T21:43:05.406+01:00You're right that a workaround is to put the p...You're right that a workaround is to put the path in the project settings, but I don't think I'd classify it as any more "correct" than using the INCLUDE variable.<br /><br />Adding this same setting to 50+ projects also seems wrong though as the point is to have a single path to the root of the shared libs. Of course with VS2005+ you have inheritable property sheets to play with that would reduce the maintenance burden.Chris Oldwoodhttps://www.blogger.com/profile/18183909440298909448noreply@blogger.comtag:blogger.com,1999:blog-6628985022531866193.post-24631830709644533122010-05-18T08:20:11.867+01:002010-05-18T08:20:11.867+01:00Wasn't it more correct to add '%DEV%\OurCo...Wasn't it more correct to add '%DEV%\OurCode\Lib' path to project's include section, not in INCLUDE environmental variable, used by devenv? This way the problem would not arise, I think.Alex Chehttps://www.blogger.com/profile/11914214520243114798noreply@blogger.com