Home/ Questions/Q 244411
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T21:00:09+00:00

Our code includes vector , which includes memory , which includes Microsoft’s intrin.h ,

  • 0

Our code includes vector, which includes memory, which includes Microsoft’s intrin.h, but we have an intrin.h of our own on our include path. Hence memory picks up our intrin.h instead of the system one, and fails to compile.

Both our intrin.h and Microsoft’s have been around for years, but we’ve never had a conflict before – VS 2010 introduces a new dependency. Moving or renaming our intrin.h would be a pain, and I’d rather avoid it.

Is there some way I can persuade MSVC to look in the system include directory before our own? Editing memory to say:

#include "intrin.h"

rather than

#include <intrin.h>

works, but I don’t want the whole team to have to modify their Visual Studio environments (and keep them modified in the face of service packs, etc.)

Any other way of working around this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    How about simply adding the system include directory to the include path before your directory?

    • 0