You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Use different byte code versioning scheme value for chakracore from chakra in release build as well.
- Separate release flags between chakra/chakracore so that they can go into release mode independently.
- Make library byte code always use the release versioning scheme.
- Update the no jit version of the Intl byte code.
- Change the top level output directory for the no jit version to have the ".NoJIT" suffix so it can be
built independently of the with jit verison.
// Version number is a GUID (128 bits). There are two versioning modes--Engineering and Release. Engineering mode is for day-to-day development. Every time chakra.dll is built a
89
-
// fresh new version is generated by hashing the build date and time. This means that a byte code file saved to disk is exactly tied to the chakra.dll that generated it. This works
89
+
// fresh new version is generated by hashing the build date and time. This means that a byte code file saved to disk is exactly tied to the binary that generated it. This works
90
90
// well for QA test runs and buddy tests because there is no chance of effects between runs.
91
91
//
92
92
// Release mode is used when chakra.dll is close to public release where there are actual changes to chakra. The GUID is a fixed number from build-to-build. This number will stay
93
-
// the same for releases where there is no change to jscript9. The reason for this is that we don't want to invalidate compatible byte code that has already been cached.
93
+
// the same for releases where there is no change to chakra.dll. The reason for this is that we don't want to invalidate compatible byte code that has already been cached.
94
94
enum FileVersionScheme : byte
95
95
{
96
-
// Even Chakra and ChakraCore may have the same version, their byte code may not be compatible. Give them different value.
96
+
// Currently Chakra and ChakraCore versioning scheme is different.
97
+
// Same version number for Chakra and ChakraCore doesn't mean they are the same.
98
+
// Give the versioning scheme different value, so that byte code generate from one won't be use in the other.
0 commit comments