make the dev version of bsc.exe behave the same as release version of bsc #4827
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, in the dev mode, it does not load cmi/cmj by default since there's a bootstrap issue,
you need build those binary artifacts first before embedding it, this cause the slightly different behavior
between the compiler built in dev mode and release mode, this commit make them behave almost
the same by adding the include path in dev mode, so that those binary artifacts are loaded during the runtime
The consequence is that to test the compiler, we don't need go into a release mode, you can test the new behavior very fast
add
rescript = 1in ninja file so that the build engine could do some specialization