Search Issue Tracker

Fixed in 2020.2

Fixed in 2019.4, 2020.1

Votes

1

Found in

2018.4

2019.2

2019.3

2019.3.0f3

2020.1

Issue ID

1207413

Regression

No

Assembly definition define constraints are incompatible when using global defines from "csc.rsp" file

Scripting

-

How to reproduce:
1. Open the user's attached project
2. In the "Project" tab, navigate to "Assets/Scripts/ModuleA/NewAssembly" and inspect it in the inspector
3. Notice the errors in "Define Constraints" tab

Expected results: No errors are shown and Assembly Definition Constraints works with global defines
Actual results: "Define constraint is incompatible" error is shown and assembly definition does not work

Reproducible with: 2018.4.15f1, 2019.2.17f1, 2019.3.0f4, 2020.1.0a18
Couldn't test with 2017.4 (it doesn't support assembly definition constraints)

Notes:
1. The global define is detected by scripts, but it doesn't work in assembly definition constrains
2. When using deprecated 3.5 .NET runtime, the global define is not detected in scripts (tested in 2018.4 stream)
3. When the "csc.rsp" file is placed in the same directory as the assembly definition, everything works fine

  1. Response avatar

    Resolution Note (fix version 2020.2):

    Now Rsp files Defines will be included in the resolution of Define constraints.
    Fixed in 2020.2.0a19.2490

  2. Response avatar

    Resolution Note (fix version 2020.1):

    Fixed in 2020.1.4f1

  3. Response avatar

    Resolution Note (fix version 2019.4):

    Fixed in 2019.4.9f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.