binstall.1 2.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970
  1. .\" $XConsortium: binstall.1 /main/3 1995/10/30 14:05:34 rswiston $
  2. .TH binstall 1 "" "" CDE
  3. .ds )H Common Desktop Environment
  4. .ds ]W January 1994
  5. .SH NAME
  6. binstall \- build tree build environment installation mechanism
  7. .SH DESCRIPTION
  8. This man page is an index into the build installation mechanism set up
  9. by
  10. .I imake
  11. for the CDE build environment.
  12. This mechanism was set up to allow developers to use alternative build
  13. environments (usually from some previous day's build) when build trees
  14. are unstable.
  15. The mechanism extracts libraries,
  16. headers, make configuration, and binaries from a build tree and installs
  17. them in a designated location. If
  18. .I installpath
  19. is the installation location,
  20. .I make binstall
  21. will create the following directories under
  22. .IR installpath :
  23. .I include
  24. (and subdirectories),
  25. .IR lib ,
  26. .IR bin ,
  27. .IR config ,
  28. and
  29. .IR util .
  30. The mechanism can also create any other needed directories under
  31. .IR installpath .
  32. These directories can then be accessed by a developer by pointing the
  33. .I TOP
  34. of his Makefiles to
  35. .I installpath
  36. (See Examples below).
  37. Most components (including imake-oriented components not in any build
  38. tree) can then leverage the libraries, headers, etc. in the binstall
  39. path and build correctly.
  40. .SH EXAMPLES
  41. A developer can use the headers, libraries, etc. located under the
  42. .I installpath
  43. by doing the following:
  44. .TP 3
  45. 1) Create or copy the directory structure you are developing. It is
  46. assumed that this structure is using imake. If there is no Makefile at
  47. the top of directory structure, copy one from any build tree for your
  48. architecture.
  49. .TP
  50. 2) cd to the top of your directory structure.
  51. .TP
  52. 3)
  53. .I make TOP=installpath Makefile; [make Makefiles];make
  54. .SH FURTHER INFORMATION
  55. Access to binstall paths may vary for each vendor site. For information
  56. about the binstall paths available to developers, see each site's man
  57. page of the form binstall_vendor(1)-> binstall_hp(1), binstall_sun(1),
  58. binstall_novell(1), binstall_ibm(1), etc..
  59. For information about the administration of binstall see
  60. .IR binstall (5).
  61. .SH AUTHOR
  62. The binstall mechanism
  63. was developed by Marc Ayotte,
  64. WTD-CV, Hewlett-Packard.
  65. .SH SEE ALSO
  66. binstall_hp(1),
  67. binstall_sun(1),
  68. binstall_novell(1),
  69. binstall_ibm(1),
  70. binstall(5).