Visual Studio Community 2019 Build Process

[AlexProudfoot]

Visual Studio Community 2019 is no longer available for download from Microsoft.

The installer can be obtained from The Internet Archive instead.

Maybe update the README file to reflect this?

Also. I had no trouble updating to Visual Studio Community 2022.

Maybe use this instead?

[AlexProudfoot]

I'm having trouble building ganelson/inform from scratch and am curious to know if you have noticed anything similar. Issue raised as I7-2596. I'm pretty sure I have followed the build instructions precisely and am wondering if some necessary configuration details are missing.

[DavidKinder]

I haven't encountered such an error, but then I'm building in an existing environment, not a clean build. My initial guess would be something has crept into the build procedure such that it no longer works from an entirely clean starting point.

[AlexProudfoot]

Yes. A precarious situation I think. I’ll look into it some more and let you know how far I got.

[AlexProudfoot]

Graham has fixed the build problem which was due to a bug in Inweb. However, I’m still getting a problem with exporting inform to Windows-Inform7. On trying to compile a game, I get complaints from inform 6 about double definitions of globals. Have you any idea what might be causing this?

[DavidKinder]

Yes, I'm seeing this, it looks likely to be caused by the move to Inform 6.43, but not sure if it is a problem in Inform 6.43 or Inform 7.

[AlexProudfoot]

Issue raised as I7-2602.

[DavidKinder]

Issue raised as I7-2602.

This turns out to be an Inform 6 issue, DavidKinder/Inform6#332.

[AlexProudfoot]

Thanks for that David. Maybe I can roll back to the previous release of Inform 6? I’ll see how that goes.

[AlexProudfoot]

Great, that worked. Now I can move on to complaining about namespace pollution from the standard extensions. I think my build issues are sorted for now. Thanks for your help David.

[AlexProudfoot]

Building from scratch is still a problem because the standard extension kits are not exported by "make forceintegration".

See I7-2623 for my local workround.

[DavidKinder]

Building from scratch is still a problem because the standard extension kits are not exported by "make forceintegration".
See I7-2623 for my local workround.

I don't think this is right. With the latest code, there is no "Internal\Inter" directory at all in the build directory: all the relevant files are in "Internal\Extensions\Graham Nelson\*.i7xd\Materials\Inter" directories.

[AlexProudfoot]

OK. That’s confusing because files in Internal\Inter are definitely being noticed by the application. I’ll remove those and make sure the new locations are populated.

Thanks for explaining. Maybe update the readme file to include the removal of Internal\Inter?

[AlexProudfoot]

Done and working.