/src/wrappers/gobject/examples/g_value_example.ace

http://github.com/tybor/Liberty · Unknown · 169 lines · 138 code · 31 blank · 0 comment · 0 complexity · 7b67b1048043040f3d310df268091209 MD5 · raw file

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