ConfigMap Problem/Question

[MrDrElliot]

Hello,

I have a project which only contains runtime libraries, so I mapped my Debug configuration to another which is a MD_DynamicRelease, the issue is that I link to other projects, and when I build this specific application, it needs to build the newly mapped versions of those libraries as well.

Even though in this application I mapped my Debug configuration, it's still attempting to build another library under the "Debug" configuration, thus giving me a LNK2038.

Any ideas?

[MrDrElliot]

The only solution I could find that works was to not link to that library, and embed the source files directory into the project with the configuration mapping, but that's just circumventing the issue.

[nickclark2016]

I think you have the configmap the wrong way around:

configmap {
  ["Development"] = "Debug"
}

The configmap key is the workspace configuration, the value is the project configuration.

[MrDrElliot]

I think you have the configmap the wrong way around:

configmap {
  ["Development"] = "Debug"
}

The configmap key is the workspace configuration, the value is the project configuration.

Nope, I believe I have it correct. I am mapping the workspace "Debug" to the project's "Development".

I'm fairly certain it's working because if I remove it, I will get other errors relating to linking to incorrect runtimes, since the libraries "Reflector" links to are not debug.

[nickclark2016]

Can you provide a minimum reproducing premake script? Also, what exporters are impacted? It looks like Visual Studio 2022 of earlier. In the future, please do not remove the issue template.