
Vector Label Module as Express Project
--------------------------------------

          April 25, 1995
          Ian Curington

Notes on how to construct a "portable" and "consistant"
Express project, such that similar modules can be merged:

[1] "mods" source directory convention

[2] "v"    v directory convention

[3] Well denoted express and/or user process support in module

[4] worksp.v $include of module specific V

[5] no "build_dir" property, set on library workspace only

[6] use src_file, not c_src_files to specify C source.

[7] use WORKSPACE_1 for method wrappers only

[8] use WORKSPACE_2 for macros, pure V, UI components

[9] use WORKSPACE_3 for demo macros, complete networks or applications

[10] precise note of which version of express it was built with,
     such as: "EXPRESS version: 2.0 (4.44 HPUX9)"

[11] notes on what buttons to push in what order, to use the module.

[12] as many properties as possible specified in V properties,
     and not in source code, include files, or Makefile.

[13] no hard coded path names any where, assume the user has
     cd'd to your project directory, use relative path names from this.

[14] include no auto-generated files with the project.


