/src/wrappers/gtk/examples/windows/plain_window_example.ace
Unknown | 209 lines | 167 code | 42 blank | 0 comment | 0 complexity | f84a531c77d79625ad0ed816912c24f7 MD5 | raw file
1system 2"plain_window_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 7root 8 9 PLAIN_WINDOW_EXAMPLE: make 10 -- Replace ROOT_CLASS and creation_procedure with the names of the 11 -- root class and the root creation procedure for your system. 12 13default -- section of the system 14 15 assertion (require); 16 -- The default level of assertion checking for the system. 17 -- Choose the appropriate value: boost, no, require, ensure, 18 -- invariant, loop, check, all. 19 20 assertion_flat_check (no); 21 -- In flat mode each assertion will be executed in no_check mode. 22 -- This means that while checking assertion, no other assertion will 23 -- be checked. This mode has only sense in assertion modes from 24 -- require to debug. 25 26 debug (no); 27 -- The default debug level for the system. 28 -- Choose yes, no, or any "key" you wish. 29 30 trace (no); 31 -- The default trace mode for the system. Choose yes or no. 32 33 collect (yes); 34 -- Choose yes here to add garbage collector support to your system. 35 -- Choose no here to indicate that you don't want the garbage collector 36 -- to be included in your system; no is the equivalent of the -no_gc 37 -- flag in traditional command line mode. 38 39 no_style_warning (no); 40 -- My humble opinion is that you should always write no here. 41 -- Yes is the equivalent of the -no_style_warning flag in traditional 42 -- command line mode. 43 44 no_warning (no); 45 -- My humble opinion is that you should always write no here. 46 -- Yes is the equivalent of the -no_warning flag in traditional 47 -- command line mode. 48 49 verbose (no); 50 -- The equivalent of the -verbose flag. (Also note that the -verbose 51 -- flag is still accepted in ACE file mode.) 52 53 manifest_string_trace (yes); 54 -- The equivalent of the -manifest_string_trace flag. 55 56 high_memory_compiler (no); 57 -- The equivalent of the -high_memory_compiler flag. 58 59 profile (yes); 60 -- The equivalent of the -profile flag. 61 62 relax (yes); 63 -- The equivalent of the -relax flag. 64 65cluster -- section 66 gtk: "${eiffel_libraries}/eiffel-gtk/loadpath.se" 67 gdk: "${eiffel_libraries}/eiffel-gdk/loadpath.se" 68 glib: "${eiffel_libraries}/eiffel-glib/loadpath.se" 69 gobject: "${eiffel_libraries}/eiffel-gobject/loadpath.se" 70 pango: "${eiffel_libraries}/eiffel-pango/loadpath.se" 71 72 plain_window_example: "." 73 -- The cluster section is an ordered list of clusters. Roughly speaking, 74 -- a cluster can be considered as a directory where Eiffel source files 75 -- are to be searched for. Thus, the order of this list of clusters is 76 -- important because clusters are considered sequentially while 77 -- searching for an Eiffel source file. Each cluster is described 78 -- as follows: 79 80-- optional_cluster_name: "cluster_path_using_system_file_notation_here" 81-- default -- at this cluster level 82-- assertion (require) 83-- debug (no); 84-- trace (no); 85-- option -- for this cluster 86-- assertion (loop) : CLASS_NAME1, CLASS_NAME2; 87-- assertion (all) : CLASS_NAME3, CLASS_NAME4; 88-- -- ... 89-- debug (yes) : CLASS_NAME1, CLASS_NAME2, ...; 90-- debug ("KEY") : CLASS_NAME1, CLASS_NAME2, ...; 91-- -- ... 92-- trace : CLASS_NAME1, CLASS_NAME2; 93-- trace : CLASS_NAME3, CLASS_NAME4; 94-- -- ... 95-- end -- of one cluster 96 97 -- Pull in SmartEiffel's standard library. Always put this last so 98 -- that you can override options for parts of the library. 99 100 standard: "${path_lib}/loadpath.se" 101 102external -- section for elements written in another language 103 -- Directories where to search for C .h files: 104 -- external_header_path: "/usr/local/expat/include /usr/local/include/mjpegtools" 105 --external_header_path: "$(pkg-config --cflags glib-2.0)" 106 107 108 -- External object files to be considered; update and uncomment the 109 -- following line: 110 -- external_object_files: "foo.o bar.o" 111 112 -- External C files to be considered; update and uncomment the 113 -- following line: 114 -- external_c_files: "foo.c bar.c" 115 116 -- External C++ files to be considered; update and uncomment the 117 -- following line: 118 -- external_c_plus_plus_files: "foo.cpp bar.cpp" 119 120 -- The equivalent of the -cecil flag of the traditional command line mode. 121 -- To indicate some cecil file to be considered, update and uncomment 122 -- the following lines: 123 -- cecil ("my_cecil_file1.se") 124 -- cecil ("my_cecil_file2.se") 125 -- cecil ("my_cecil_file3.se") 126 -- ... 127 128 -- External libraries directory path to be considered; update and uncomment 129 -- the following line: 130 --external_lib_path: " $(pkg-config --cflags --libs glib-2.0)" 131 132 -- From release -0.74Beta#20 and later SmartEiffel supports linker 133 -- external_lib_path. Just leave out the -L: 134 -- external_lib_path: "/usr/local /foo/bar" 135 -- In this case external_lib_path will work on Windows too. 136 137 -- External libraries to be considered; update and uncomment the following 138 -- line: 139 --external_lib: "$(pkg-config --libs glib-2.0)" 140 141 -- or linker independent: 142 -- external_lib: "m X11" 143 144generate -- section 145 146 no_strip(no); 147 -- Yes would mean that you don't want to run "strip" on the generated 148 -- executable. This is the equivalent of the -no_strip flag of the 149 -- traditional command line mode. (I.e. to use a C level debugger on your 150 -- system, you should choose yes here). 151 152 no_split(no); 153 -- Yes would mean that you want one big single C file for the complete 154 -- system, pinstead of the many small C files produced by default ("no"). 155 -- This may be useful for delivery of the most efficient version. (Some 156 -- C compilers including gcc can then do better inlining.) 157 158 clean(no); 159 -- Yes would mean that you want to remove all generated C files, all 160 -- generated object files as well as other temporary files generated 161 -- during the compilation process. (See also command clean.) 162 163 -- The equivalent of the -cc flag of the traditional command line mode. 164 -- To select a different C compiler from the default, update and uncomment 165 -- the following line: 166 -- cc : "gcc" 167 168 -- To decide which C compiler options are to be passed, you need to use 169 -- this keyword as well as a good understanding of your C compiler. 170 -- Update and uncomment the following line: 171 c_compiler_options : "$(pkg-config --cflags gtk+-2.0)" 172 173 -- Some options are to be passed only to the linker. Update and uncomment 174 -- the following line: 175 linker_options : "$(pkg-config --libs gtk+-2.0)" 176 177 -- For the equivalent of the -no_main flag of the traditional command line 178 -- mode, uncomment the following line: 179 -- no_main (yes) 180 181 -- For the equivalent of the -gc_info flag of the traditional command line 182 -- mode, uncomment the following line: 183 -- gc_info (yes) 184 185 -- For the equivalent of the -wedit flag of the traditional command line 186 -- mode. To Include support for the Wedit debugger uncomment the following 187 -- line: 188 -- wedit (yes) 189 190 191-- Additional information about system environment variables: 192-- Inside manifest strings, you are allowed to use system 193-- environment variables using the same notation as in the traditional 194-- "loadpath.se" files. Actually, this notation is inspired by the 195-- traditional UNIX bracketed notation as for example: ${FOO} or ${Bar} 196-- or ${SmartEiffel}. 197-- 198-- Additional information about the ${SmartEiffelDirectory} variable: 199-- If not explicitely set by the user, the ${SmartEiffelDirectory} variable 200-- is automatically computed using the value of the ${SmartEiffel} variable. 201-- (Keep in mind that the ${SmartEiffel} variable is mandatory for using 202-- SmartEiffel.) The computed value indicates the SmartEiffel main 203-- directory. For example, if the value of ${SmartEiffel} is 204-- "/usr/local/lib/SmartEiffel/sys/system.se" 205-- the computed value is "/usr/local/lib/SmartEiffel/". This automatically 206-- defined variable ${SmartEiffelDirectory} is useful for indicating the 207-- location of the SmartEiffel standard library. 208-- 209end