Author:admin

Date:2008-09-18T14:32:43.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@13 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
jfiat
2008-09-18 14:32:43 +00:00
parent 8177357757
commit 13b85fb9c9
20 changed files with 1144 additions and 28 deletions

View File

@@ -1,6 +1,7 @@
[[Property:title|16 HOW EIFFELSTUDIO COMPILES]]
[[Property:link_title|How EiffelStudio Compiles]]
[[Property:weight|3]]
[[Property:uuid|6fc86303-8afe-78af-6ca7-2853e8bfcbc3]]
[[Help reading the EiffelStudio Guided Tour|Help reading this manual]]
So far we have relied on the compiling capabilities of EiffelStudio without exploring them in any detail. We must now understand the principles behind EiffelStudio's compiling strategy, in particular how it reconciles fast turnaround, efficient generated code, and strong typing.
@@ -161,7 +162,7 @@ Note the <code> No </code> option: by default, freezing will start a C compilati
Click <code> Yes </code> to confirm freeze and C-compilation. Once the Eiffel compilation is complete, a message in the Development Window ( <code> C compilation launched in background </code>) tells you when that C-compilation has started. C-compilation does not block EiffelStudio: at this point you can continue working with the environment. Any messages from C compiler will appear:
* On Windows, in a new console that comes up for the occasion (minimize it if you don't want to see the messages).
* On Unix/Linux and VMS, in the window from which you launched EiffelStudio.
* On Unix/Linux and OpenVMS, in the window from which you launched EiffelStudio.
You will be able to execute the frozen system as soon as the C compilation finishes.