frysk.*.Build, aka common/Build.javain, deleted

frysk.*.Build, aka common/Build.javain, deleted

[Andrew Cagney]

FYI,

I've deleted the classes frysk.{imports,core,gui}.Build that were 
generated from common/Build.javain.  While appearing to be a good idea 
at the time, it proved problematic, for instance being used it ways it 
wasn't intended and having non-constant java strings.

Going forward code looking to obtain build information should follow one 
of the following patterns:


- code requiring the location of exec and data files, e.g., a test case 
reading in a .xml file

For test cases, all required paths can be found in frysk.junit.Paths.  
In the case of the .xml file, the path frysk.junit.Paths.getDataPrefix() 
should be used.  The value returned will differ for build-tree and 
install-tree test runs.


- a build-tree main program needing build-time paths, e.g., TestRunner

The TestRunner source file (TestRunner.javain) is pre-processed wiring 
in the build-time location of data and exec directories, those values 
then being made available in frysk.junit.Paths.  Since the TestRunner 
executable and .class files are not distributed problems with clashing 
paths are avoided.

Please note that such programs and tests _should_ _not_ be written to 
look in both the build-tree and install-tree for files using a search 
algorithm.  This is wrong as, for instance, it can lead to a build-time 
program ising installed files from a different release, or an installed 
program apparently working because it is accidently using files from a 
newer build.


- an installed main program needing install-time paths, e.g., funit

Installed programs such as funit use frysk.Config for paths.


Andrew