mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2025-12-06 23:02:28 +01:00
Code Issues Packages Projects Releases Wiki Activity

Author:bmeyer

Browse Source 
Date:2014-04-14T15:51:09.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1321 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
vwheeler
2014-04-18 16:35:06 +00:00
parent 92aab87b92
commit d7eed2b321
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/index.wiki
View File

@@ -3,7 +3,8 @@
[[Property:uuid|d3564eb8-ef56-4ec1-599f-430b023fa7e8]]
The '''EiffelCOM Wizard''' is delivered with EiffelStudio, but it is a '''standalone tool''' (i. e., not part of the EiffelStudio IDE). You can find the wizard by following the directory path: <code lang="text">$ISE_EIFFEL\wizards\com</code>. The executable file <code lang="text">com_wizard_launcher.exe</code> will launch the GUI version of the wizard. The executable file <code lang="text">com_wizard.exe</code> is a command line version of the wizard described [[Wizards: Command Line Options|here]].
The EiffelCOM Wizard allows the creation of Eiffel projects implementing or reusing COM components.
The EiffelCOM Wizard facilitates the creation of Eiffel projects implementing or reusing COM components.
* [[How the EiffelCOM Wizard works|How the EiffelCOM Wizard works]] describes the steps followed by the wizard when creating the Eiffel project.
* [[Generated Files|Generated Files]] describes the list of generated files and their usage.
* [[Class Hierarchy|Class Hierarchy]] describes the class hierarchy of the generated Eiffel project.
@@ -17,5 +18,3 @@ The EiffelCOM Wizard allows the creation of Eiffel projects implementing or reus
[[EiffelCOM Wizard Guided Tour|Guided Tour]] }}

1
documentation/current/solutions/iron-eiffel-package-repository.wiki
View File

@@ -22,6 +22,7 @@ As projects grow and multiply, the number of these variables adds up quickly. A
IRON has made it possible to simplify this scenario dramatically. For any commonly used library, it suffices to:
* Install the library on an IRON server.
* For any program that uses the library, include in the project's ECF a reference to the library's location <i>in the server</i>, rather than its physical location.
That's all! In the above example, the paths to the libraries, in the project, then become something like: