/src/wrappers/gtk/examples/hello/boost-hello.ace

http://github.com/tybor/Liberty · Unknown · 163 lines · 134 code · 29 blank · 0 comment · 0 complexity · 218631a83da736032f2a0676d2e30d0f MD5 · raw file

  1. system "boost-hello"
  2. root HELLO: make
  3. default -- section of the system
  4. assertion (boost);
  5. assertion_flat_check (no);
  6. debug (no);
  7. trace (no);
  8. collect (yes);
  9. no_style_warning (no);
  10. no_warning (no);
  11. verbose (no);
  12. manifest_string_trace (no);
  13. high_memory_compiler (no);
  14. profile (no);
  15. relax (yes);
  16. cluster -- section
  17. gtk: "${eiffel_libraries}/eiffel-gtk/loadpath.se"
  18. gdk: "${eiffel_libraries}/eiffel-gdk/loadpath.se"
  19. glib: "${eiffel_libraries}/eiffel-glib/loadpath.se"
  20. gobject: "${eiffel_libraries}/eiffel-gobject/loadpath.se"
  21. pango: "${eiffel_libraries}/eiffel-pango/loadpath.se"
  22. hello_demo: "."
  23. -- The cluster section is an ordered list of clusters. Roughly speaking,
  24. -- a cluster can be considered as a directory where Eiffel source files
  25. -- are to be searched for. Thus, the order of this list of clusters is
  26. -- important because clusters are considered sequentially while
  27. -- searching for an Eiffel source file. Each cluster is described
  28. -- as follows:
  29. -- optional_cluster_name: "cluster_path_using_system_file_notation_here"
  30. -- default -- at this cluster level
  31. -- assertion (require)
  32. -- debug (no);
  33. -- trace (no);
  34. -- option -- for this cluster
  35. -- assertion (loop) : CLASS_NAME1, CLASS_NAME2;
  36. -- assertion (all) : CLASS_NAME3, CLASS_NAME4;
  37. -- -- ...
  38. -- debug (yes) : CLASS_NAME1, CLASS_NAME2, ...;
  39. -- debug ("KEY") : CLASS_NAME1, CLASS_NAME2, ...;
  40. -- -- ...
  41. -- trace : CLASS_NAME1, CLASS_NAME2;
  42. -- trace : CLASS_NAME3, CLASS_NAME4;
  43. -- -- ...
  44. -- end -- of one cluster
  45. -- Pull in SmartEiffel's standard library. Always put this last so
  46. -- that you can override options for parts of the library.
  47. standard: "${path_lib}/loadpath.se"
  48. external -- section for elements written in another language
  49. -- Directories where to search for C .h files:
  50. -- external_header_path: "/usr/local/expat/include /usr/local/include/mjpegtools"
  51. --external_header_path: "$(pkg-config --cflags glib-2.0)"
  52. -- External object files to be considered; update and uncomment the
  53. -- following line:
  54. -- external_object_files: "foo.o bar.o"
  55. -- External C files to be considered; update and uncomment the
  56. -- following line:
  57. -- external_c_files: "foo.c bar.c"
  58. -- External C++ files to be considered; update and uncomment the
  59. -- following line:
  60. -- external_c_plus_plus_files: "foo.cpp bar.cpp"
  61. -- The equivalent of the -cecil flag of the traditional command line mode.
  62. -- To indicate some cecil file to be considered, update and uncomment
  63. -- the following lines:
  64. -- cecil ("my_cecil_file1.se")
  65. -- cecil ("my_cecil_file2.se")
  66. -- cecil ("my_cecil_file3.se")
  67. -- ...
  68. -- External libraries directory path to be considered; update and uncomment
  69. -- the following line:
  70. --external_lib_path: " $(pkg-config --cflags --libs glib-2.0)"
  71. -- From release -0.74Beta#20 and later SmartEiffel supports linker
  72. -- external_lib_path. Just leave out the -L:
  73. -- external_lib_path: "/usr/local /foo/bar"
  74. -- In this case external_lib_path will work on Windows too.
  75. -- External libraries to be considered; update and uncomment the following
  76. -- line:
  77. --external_lib: "$(pkg-config --libs glib-2.0)"
  78. -- or linker independent:
  79. -- external_lib: "m X11"
  80. generate -- section
  81. no_strip(no);
  82. -- Yes would mean that you don't want to run "strip" on the generated
  83. -- executable. This is the equivalent of the -no_strip flag of the
  84. -- traditional command line mode. (I.e. to use a C level debugger on your
  85. -- system, you should choose yes here).
  86. no_split(no);
  87. -- Yes would mean that you want one big single C file for the complete
  88. -- system, pinstead of the many small C files produced by default ("no").
  89. -- This may be useful for delivery of the most efficient version. (Some
  90. -- C compilers including gcc can then do better inlining.)
  91. clean(no);
  92. -- Yes would mean that you want to remove all generated C files, all
  93. -- generated object files as well as other temporary files generated
  94. -- during the compilation process. (See also command clean.)
  95. -- The equivalent of the -cc flag of the traditional command line mode.
  96. -- To select a different C compiler from the default, update and uncomment
  97. -- the following line:
  98. -- cc : "gcc"
  99. -- To decide which C compiler options are to be passed, you need to use
  100. -- this keyword as well as a good understanding of your C compiler.
  101. -- Update and uncomment the following line:
  102. c_compiler_options : "$(pkg-config --cflags gtk+-2.0)"
  103. -- Some options are to be passed only to the linker. Update and uncomment
  104. -- the following line:
  105. linker_options : "$(pkg-config --libs gtk+-2.0)"
  106. -- For the equivalent of the -no_main flag of the traditional command line
  107. -- mode, uncomment the following line:
  108. -- no_main (yes)
  109. -- For the equivalent of the -gc_info flag of the traditional command line
  110. -- mode, uncomment the following line:
  111. -- gc_info (yes)
  112. -- For the equivalent of the -wedit flag of the traditional command line
  113. -- mode. To Include support for the Wedit debugger uncomment the following
  114. -- line:
  115. -- wedit (yes)
  116. -- Additional information about system environment variables:
  117. -- Inside manifest strings, you are allowed to use system
  118. -- environment variables using the same notation as in the traditional
  119. -- "loadpath.se" files. Actually, this notation is inspired by the
  120. -- traditional UNIX bracketed notation as for example: ${FOO} or ${Bar}
  121. -- or ${SmartEiffel}.
  122. --
  123. -- Additional information about the ${SmartEiffelDirectory} variable:
  124. -- If not explicitely set by the user, the ${SmartEiffelDirectory} variable
  125. -- is automatically computed using the value of the ${SmartEiffel} variable.
  126. -- (Keep in mind that the ${SmartEiffel} variable is mandatory for using
  127. -- SmartEiffel.) The computed value indicates the SmartEiffel main
  128. -- directory. For example, if the value of ${SmartEiffel} is
  129. -- "/usr/local/lib/SmartEiffel/sys/system.se"
  130. -- the computed value is "/usr/local/lib/SmartEiffel/". This automatically
  131. -- defined variable ${SmartEiffelDirectory} is useful for indicating the
  132. -- location of the SmartEiffel standard library.
  133. --
  134. end