Developer Notes

This is not a bug. You can't forcibly enable exceptions for the installed build. If it pretended to let you before, that was a bug.

Description

It is no longer possible to enable C++ exceptions for the ProjectEditor target in code projects that use the binary Engine. Some fixes that were made for 4.19 now correctly show an error message if bForceEnableExceptions is set to true in the ProjectEditor.Target.cs file. The error message states that exceptions can be enabled if a unique build environment is used. However, adding the suggested line (BuildEnvironment = TargetBuildEnvironment.Unique;) results in another build failure.

Steps to Reproduce
  1. Create a new code project.
  2. Close the Editor.
  3. Open the project's ProjectEditor.Target.cs file.
  4. Add the following line to the class constructor: this.bForceEnableExceptions = true;
  5. Build the project.
    • The build will fail and the Output window will show a message that modifying bForceEnableExceptions is not allowed unless the BuildEnvironment is set to Unique.
  6. Add the following line above the previous line: BuildEnvironment = TargetBuildEnvironment.Unique;
  7. Build the project.

RESULT:
The build fails with the following error message: error : System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\Unreal Projects\Current Issues\TestException2\Intermediate\Build\Win64\TestException2Editor\Development\Launch\Launch.precompiled'.

EXPECTED:
The build completes successfully, and exceptions are enabled.

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-61804 in the post.

10
Login to Vote

Non-Issue
ComponentUE - Foundation - Cpp Tools
Affects Versions4.19.24.204.21
CreatedJul 16, 2018
ResolvedJul 17, 2018
UpdatedJul 17, 2018
View Jira Issue