Incorrect default value of MSBuild property wxIntRootDir? (Issue #26135)

13 views

Skip to first unread message

PB

unread,

Jan 30, 2026, 5:06:13 AM (3 days ago) Jan 30

to wx-...@googlegroups.com, Subscribed

PBfordev created an issue (wxWidgets/wxWidgets#26135)

MSBuild property wxIntRootDir is used for the object files and is currently defined for example like this
https://github.com/wxWidgets/wxWidgets/blob/21b5e055cacc074f7216804e37c6257938c7efc3/build/msw/wx_setup.props#L76-L77

In contrast, when building with nmake the object path is
https://github.com/wxWidgets/wxWidgets/blob/21b5e055cacc074f7216804e37c6257938c7efc3/build/msw/makefile.vc#L37-L38

There are several differences, for me the important one is that with MSBuild, the configuration part (wxCfg) is missing.

This results in a minor annoyance when one is building the default configuration (e.g., passing /p:Configuration=Release to MSBuild) and the same customized configuration (e.g., adding /p:wxCfg="-staticCRT" /p:wxRuntimeLibs=static) where the object files for both configurations are put in the same object folder and therefore overwritten (the object folder name is vc_x64_mswu with MSBuild and vc_x64_mswu-staticCRT with nmake).

Perhaps this MSBuild property should be created in a similar way it is done in the MSVC makefile.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

VZ

unread,

Jan 30, 2026, 8:15:20 AM (3 days ago) Jan 30

to wx-...@googlegroups.com, Subscribed

vadz left a comment (wxWidgets/wxWidgets#26135)

I agree we could add wxCfg there, as it's empty by default this should be backwards compatible for most people (and using a config-specific directory shouldn't be a problem for those who do set wxCfg anyhow).