PR# 13068 Turning on use_application_options after initial compile has no effect

After an initial compile where the use_application_options setting is not
specified for base library in the configuration file, add
use_application_options="true" to the <library> element in the
configuration file and recompile the system.  System execution then does not
use application options, so it still prints False but it should fail with
a precondition violation.

This is an incrementality bug - compiling from scratch with the final .ecf file
causes system execution to produce the correct result (a precondition violation).

This should go on the Critical Bugs list.

Compile with attached class and config file test.ecf.
Execute system.  Prints False because library is not using application options.
Copy file test_new.ecf to test.ecf (it just adds the use_application_options
attribute to the <library> element).
Recompile.  Execute system.  Still prints False but should get a precondition
   violation.
Now delete EIFGENs directory and compile.  System execution then correctly
   results in a precondition violation.

This should be fixed in rev#71453.

Added eweasel test#assert002.

Trying with eweasel worked just fine and the reason is that by default we always force the `-melt' option so that file changes are always tracked. I'll try to fix this for 6.1 but it might be more tricky.

Attachments for problem report #13068