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