Visual C/C++ 7.1 compatibility?

14 views
Skip to first unread message

Mark Rotteveel

unread,
Jul 11, 2025, 3:29:14 AMJul 11
to firebir...@googlegroups.com
I was confused to see `/D _VC80_UPGRADE=0x0710` in our Windows builds.
Looking in our vcxproj, most of them contain this import:

```
<Import Project="$(VCTargetsPath)Microsoft.CPP.UpgradeFromVC71.props" />
```

The sole thing that file does is add that define.

I have no clue if _VC80_UPGRADE=0x0710 still does anything in VS 2022,
but it seems like historic cruft to me that should be removed, and if
that does result in problems, those problems should be addressed.

I'll try to remove these imports and see what happens.

If anyone knows if this is intentional, let me know.

Mark
--
Mark Rotteveel

Vlad Khorsun

unread,
Jul 11, 2025, 3:43:22 AMJul 11
to firebir...@googlegroups.com
11.07.2025 10:29, 'Mark Rotteveel' via firebird-devel:
It is definitely not intentional. According to

https://stackoverflow.com/questions/12215155/what-is-upgrade-from-vc-7-1-property-sheet

macro _VC80_UPGRADE is used by ATL and/or MFC which was never used in Firebird.


Remove it.

Regards,
Vlad

Mark Rotteveel

unread,
Jul 11, 2025, 4:06:47 AMJul 11
to firebir...@googlegroups.com
Should I also modify the cds.vcxproj (from
extern/libcds/projects/Win/vc141), or leave that untouched?

Mark
--
Mark Rotteveel

Vlad Khorsun

unread,
Jul 11, 2025, 5:09:11 AMJul 11
to firebir...@googlegroups.com
11.07.2025 11:06, 'Mark Rotteveel' via firebird-devel:
As you wish. I, personally, prefer to avoid not necessary changes in extern,
but this is not a holy cow ;)

Regards,
Vlad

Mark Rotteveel

unread,
Jul 11, 2025, 5:48:54 AMJul 11
to firebir...@googlegroups.com
OK, then I'll leave those as-is.

Mark
--
Mark Rotteveel
Reply all
Reply to author
Forward
0 new messages