https://dev.eiffel.com/api.php?action=feedcontributions&feedformat=atom&user=MoriolEiffelStudio: an EiffelSoftware project - User contributions [en]2026-04-29T07:29:39ZUser contributionsMediaWiki 1.24.1https://dev.eiffel.com/index.php?title=VSTTE_address_check&diff=11392VSTTE address check2008-07-22T16:39:25Z<p>Moriol: /* Manuel Oriol */</p>
<hr />
<div>__NOTOC__<br />
The following is the list of the addresses that we have for the VSTTE 2005 attendees. The purpose of this page is to make sure we ship the proceedings to the appropriate addresses. The page will be removed as soon as the books have been shipped.<br />
<br />
==HOW TO EDIT YOUR ENTRY==<br />
* Find your name in the list<br />
* Click the "Edit" mark to the right of your name.<br />
* You will find yourself in Wiki edit mode and will see two lines of the form <nowiki><pre> and </pre></nowiki>. These delimit your entry.<br />
* Between those two lines, enter your full postal address (including your name) as it should appear on the envelope.<br />
<br />
Thank you for your cooperation and for making this volume possible.<br />
<br />
-- The VSTTE organization committee<br />
<br />
==<font color="#a00000">SAMPLE ENTRY==<br />
<pre><br />
Bertrand Meyer<br />
Chair of Software Engineering<br />
Clausiusstrasse 59<br />
8092 ETH Zentrum<br />
Zurich<br />
Switzerland<br />
</pre><br />
</font><br />
<br />
==Jean-Raymond Abrial ==<br />
<pre><br />
</pre><br />
==Rajeev Alur ==<br />
<pre><br />
</pre><br />
==Myla Archer ==<br />
<pre><br />
</pre><br />
==Ralph Back ==<br />
<pre><br />
</pre><br />
==Thomas Ball ==<br />
<pre><br />
</pre><br />
==David Basin ==<br />
<pre><br />
</pre><br />
==Yves Bertot ==<br />
<pre><br />
Yves Bertot<br />
2004, route des lucioles<br />
B.P. 93<br />
06902 Sophia Antipolis Cedex<br />
France<br />
</pre><br />
<br />
==Ramesh Bharadwaj ==<br />
<pre><br />
</pre><br />
==Dines Bjorner ==<br />
<pre><br />
</pre><br />
==Richard Bornat ==<br />
<pre><br />
</pre><br />
==Manfred Broy ==<br />
<pre><br />
</pre><br />
==Tevfik Bultan ==<br />
<pre><br />
Tevfik Bultan<br />
Department of Computer Science <br />
University of California <br />
Santa Barbara, CA 93106-5110<br />
USA<br />
</pre><br />
<br />
==Michael Butler ==<br />
<pre><br />
Michael Butler<br />
Electronics and Computer Science<br />
University of Southampton<br />
Highfield<br />
Southampton SO17 1BJ<br />
United Kingdom<br />
</pre><br />
<br />
==Egon Börger ==<br />
<pre><br />
</pre><br />
==Supratik Chakraborty ==<br />
<pre><br />
Supratik Chakraborty<br />
Dept. of Computer Science and Engg.<br />
I.I.T. Bombay, Powai<br />
Mumbai 400076<br />
Maharashtra<br />
India<br />
</pre><br />
<br />
==Patrice Chalin ==<br />
<pre><br />
</pre><br />
==Roderick Chapman ==<br />
<pre><br />
Praxis High Integrity Systems<br />
20 Manvers Street<br />
Bath<br />
BA1 1PX<br />
UK<br />
</pre><br />
<br />
==Marsha Chechik ==<br />
<pre><br />
Department of Computer Science<br />
University of Toronto<br />
40 St. George Street, Rm. 3248<br />
Toronto, ON M5S 2E4<br />
Canada<br />
</pre><br />
<br />
==Alessandro Coglio ==<br />
<pre><br />
Kestrel Institute<br />
3260 Hillview Avenue<br />
Palo Alto, CA 94041<br />
USA<br />
</pre><br />
<br />
==Green Cordell ==<br />
<pre><br />
Kestrel Institute<br />
3260 Hillview Avenue<br />
Palo Alto, CA 94041<br />
USA<br />
</pre><br />
<br />
==Patrick Cousot ==<br />
<pre><br />
Patrick Cousot<br />
Département d'Informatique<br />
École normale supérieure<br />
45 rue d'Ulm<br />
75230 Paris cedex 05 (France)<br />
</pre><br />
<br />
==Willem Paul de Roever ==<br />
<pre><br />
</pre><br />
==Michael Ernst ==<br />
<pre><br />
</pre><br />
==David Evans ==<br />
<pre><br />
</pre><br />
==Kathi Fisler ==<br />
<pre><br />
Kathi Fisler<br />
WPI Department of Computer Science<br />
100 Institute Road<br />
Worcester, MA 01609<br />
USA<br />
</pre><br />
<br />
==Kokichi Futatsugi ==<br />
<pre><br />
</pre><br />
==David Gill ==<br />
<pre><br />
</pre><br />
==Helen Gill ==<br />
<pre><br />
</pre><br />
==Allan Goldberg ==<br />
<pre><br />
</pre><br />
==Arie Gurfinkel ==<br />
<pre><br />
Arie Gurfinkel<br />
Software Engineering Institute<br />
4500 Fifth Ave<br />
Pittsburgh, PA, 15213-2612<br />
USA<br />
</pre><br />
<br />
==Masami Hagiya ==<br />
<pre><br />
</pre><br />
==Author Hagiya's ==<br />
<pre><br />
</pre><br />
==Anthony Hall ==<br />
<pre><br />
Anthony Hall<br />
22 Hayward Road<br />
Oxford OX2 8LW<br />
UK<br />
</pre><br />
<br />
==Stefan Hallerstede ==<br />
<pre><br />
</pre><br />
==Klaus Havelund ==<br />
<pre><br />
</pre><br />
==Eric C. R. Hehner ==<br />
<pre><br />
</pre><br />
==Constance Heitmeyer ==<br />
<pre><br />
</pre><br />
==Mike Hinchey ==<br />
<pre><br />
</pre><br />
==Thai Son Hoang ==<br />
<pre><br />
Thai Son Hoang<br />
Chair of Information Security<br />
IFW C48.2<br />
Haldeneggsteig 4 / Weinbergstrasse<br />
8092 ETH Zentrum<br />
Zurich<br />
Switzerland<br />
</pre><br />
<br />
==Tony Hoare ==<br />
<pre><br />
</pre><br />
==Gerard Holzmann ==<br />
<pre><br />
</pre><br />
==Vincent Homeier ==<br />
<pre><br />
</pre><br />
==Andrew Ireland ==<br />
<pre><br />
</pre><br />
==Bart Jacobs ==<br />
<pre><br />
Prof.dr. B.P.F. Jacobs<br />
Institute for Computing and Information Sciences (ICIS)<br />
Radboud University Nijmegen<br />
Heyendaalseweg 135<br />
6525 AJ Nijmegen<br />
The Netherlands <br />
</pre><br />
<br />
==He Jifeng ==<br />
<pre><br />
</pre><br />
==Cliff Jones ==<br />
<pre><br />
Prof Cliff Jones<br />
School of Computing Science<br />
Newcastle University<br />
NE1 7RU<br />
UK<br />
</pre><br />
<br />
==Mathai Joseph ==<br />
<pre><br />
</pre><br />
==Rajeev Joshi ==<br />
<pre><br />
Rajeev Joshi<br />
4800 Oak Grove Drive, MS 301-285<br />
Pasadena, CA 91109<br />
USA<br />
</pre><br />
<br />
==Joseph Kiniry ==<br />
<pre><br />
Joseph Kiniry<br />
UCD CASL<br />
Belfield Park building #8<br />
Dublin 4<br />
IRELAND<br />
</pre><br />
<br />
==Daniel Kröning ==<br />
<pre><br />
ETH Zentrum RZ H14<br />
8092 Zuerich<br />
</pre><br />
<br />
==Patrick Lam ==<br />
<pre><br />
Department of Electrical and Computer Engineering<br />
200 University Avenue West<br />
Waterloo, Ontario N2L 3G1<br />
</pre><br />
<br />
==Butler Lampson ==<br />
<pre><br />
Butler W. Lampson <br />
180 Lake View Ave.<br />
Cambridge MA 02138<br />
USA<br />
</pre><br />
<br />
==Gary T. Leavens ==<br />
<pre><br />
Gary T. Leavens<br />
Harris Center (Bldg. 116)<br />
School of EECS, University of Central Florida<br />
4000 Central Florida Blvd.<br />
Orlando, FL 32816-2362 <br />
USA<br />
</pre><br />
<br />
==Rustan Leino ==<br />
<pre><br />
</pre><br />
==Zhiming Liu ==<br />
<pre><br />
</pre><br />
==Panagiotis Manolios ==<br />
<pre><br />
College of Computer and Information Science<br />
Northeastern University<br />
360 Huntington Avenue<br />
Boston, Massachusetts 02115 U.S.A.<br />
</pre><br />
<br />
==Tiziana Margaria ==<br />
<pre><br />
</pre><br />
==Edu Metz ==<br />
<pre><br />
</pre><br />
==Bertrand Meyer ==<br />
<pre><br />
</pre><br />
==Jayadev Misra ==<br />
<pre><br />
</pre><br />
==J Moore ==<br />
<pre><br />
J Strother Moore<br />
Department of Computer Sciences<br />
Taylor Hall 2.124<br />
University of Texas at Austin<br />
Austin, TX 78712 USA<br />
</pre><br />
<br />
==Peter Müller ==<br />
<pre><br />
</pre><br />
==David A. Naumann ==<br />
<pre><br />
David Naumann<br />
Computer Science<br />
Stevens Institute of Technology<br />
Castle Point on Hudson<br />
Hoboken, NJ 07030 <br />
USA<br />
</pre><br />
<br />
==Greg Nelson ==<br />
<pre><br />
</pre><br />
==Collin O'Halloran ==<br />
<pre><br />
Colin O'Halloran<br />
33 Geraldine Road<br />
Malvern<br />
Worcestershire<br />
WR14 3NT<br />
UK<br />
</pre><br />
<br />
==Peter W. O'Hearn ==<br />
<pre><br />
</pre><br />
==Ernst-Rüdiger Olderog ==<br />
<pre><br />
</pre><br />
==Manuel Oriol ==<br />
<pre><br />
Chair of Software Engineering<br />
ETH Zentrum, RZ J9<br />
8092 Zürich<br />
Switzerland<br />
</pre><br />
<br />
==Wolfgang Paul ==<br />
<pre><br />
</pre><br />
==Amir Pnueli ==<br />
<pre><br />
</pre><br />
==Sanjiva Prasad ==<br />
<pre><br />
</pre><br />
==Ganesan Ramalingam ==<br />
<pre><br />
</pre><br />
==Mike Reed ==<br />
<pre><br />
</pre><br />
==Tom Reps ==<br />
<pre><br />
Thomas Reps<br />
Computer Sciences Department<br />
University of Wisconsin<br />
1210 West Dayton Street<br />
Madison, WI 53706<br />
USA<br />
</pre><br />
<br />
==Tamara Rezk ==<br />
<pre><br />
</pre><br />
==Martin Rinard ==<br />
<pre><br />
</pre><br />
==Grigore Rosu ==<br />
<pre><br />
</pre><br />
==Harald Ruess ==<br />
<pre><br />
</pre><br />
==John Rushby ==<br />
<pre><br />
</pre><br />
==Mooly Sagiv ==<br />
<pre><br />
</pre><br />
==Author Sagiv's ==<br />
<pre><br />
</pre><br />
==Peter Schmitt ==<br />
<pre><br />
</pre><br />
==Florian Schneider ==<br />
<pre><br />
</pre><br />
==Wolfram Schulte ==<br />
<pre><br />
Microsoft Research<br />
One Microsoft Way<br />
Redmond, WA 98052, USA<br />
</pre><br />
<br />
==Natarajan Shankar ==<br />
<pre><br />
</pre><br />
==Natasha Sharygina ==<br />
<pre><br />
</pre><br />
==Michel Sintzoff ==<br />
<pre><br />
</pre><br />
==Douglas Smith ==<br />
<pre><br />
</pre><br />
==Graham Steel ==<br />
<pre><br />
Laboratoire Spécification et Vérification<br />
École Normale Supérieure de Cachan<br />
61, avenue du Président Wilson<br />
94235 CACHAN Cedex - France <br />
</pre><br />
<br />
==Bernhard Steffen ==<br />
<pre><br />
</pre><br />
==Ofer Strichman ==<br />
<pre><br />
Ofer Strichman<br />
The Technion / Industrial Engineering<br />
Haifa 32000<br />
Israel<br />
</pre><br />
<br />
==Aaron Stump ==<br />
<pre><br />
Aaron Stump<br />
Department of Computer Science<br />
The University of Iowa<br />
201F MacLean Hall<br />
Iowa City, IA 52242-1419<br />
USA<br />
</pre><br />
<br />
==Carolyn Talcott ==<br />
<pre><br />
SRI International<br />
333 Ravenswood Avenue<br />
Menlo Park, CA 94025, USA<br />
</pre><br />
<br />
==Cesare Tinelli ==<br />
<pre><br />
</pre><br />
==Mark Utting ==<br />
<pre><br />
Mark Utting<br />
Department of Computer Science<br />
The University of Waikato<br />
Private Bag 3105<br />
Hamilton 3240<br />
NEW ZEALAND<br />
</pre><br />
<br />
==Wyk Eric Van ==<br />
<pre><br />
</pre><br />
==Helmut Veith ==<br />
<pre><br />
</pre><br />
==Arnaud Venet ==<br />
<pre><br />
</pre><br />
==Laurent Voisin ==<br />
<pre><br />
M. Laurent Voisin<br />
Systerel<br />
Portes de l'Arbois<br />
1090, rue René Descartes<br />
13857 Aix-en-Provence Cedex 3<br />
FRANCE<br />
</pre><br />
<br />
==Georg Weissenbacher ==<br />
<pre><br />
</pre><br />
==Jim Woodcock ==<br />
<pre><br />
Jim Woodcock<br />
Department of Computer Science<br />
University of York<br />
Heslington<br />
York YO10 5DD<br />
United Kingdom<br />
</pre><br />
<br />
==Eran Yahav ==<br />
<pre><br />
Eran Yahav<br />
IBM T.J. Watson Research Center<br />
19 Skyline Dr.<br />
Hawthorne, NY 10532<br />
USA<br />
</pre><br />
<br />
==Steve Zdancewic ==<br />
<pre><br />
</pre><br />
==Naijun Zhan ==<br />
<pre><br />
Naijun Zhan<br />
Lab. of Computer Science<br />
Institute of Software<br />
Chinese Academy of Sciences<br />
#4, South Fourth Str., Zhong Guan Cun<br />
Beijing, 100190<br />
P.R. China<br />
</pre><br />
<br />
==Jian Zhang ==<br />
<pre><br />
Prof. Jian Zhang<br />
Institute of Software<br />
Chinese Academy of Sciences<br />
#4, South Fourth Str., Zhong Guan Cun<br />
Beijing, 100190<br />
P.R. China<br />
</pre><br />
<br />
==Juanjun Zhao ==<br />
<pre><br />
</pre></div>Moriolhttps://dev.eiffel.com/index.php?title=CddBranch&diff=10914CddBranch2008-04-07T16:15:22Z<p>Moriol: /* Windows */</p>
<hr />
<div>[[Category:Testing]]<br />
[[Category:EiffelDebugger]]<br />
[[Category:CDD]]<br />
<br />
<br />
== What is the CDD EiffelStudio? ==<br />
<br />
[[Image:cdd_logo.png|center]]<br />
<center><br />
[http://se.ethz.ch/people/leitner/cdd/video/ '''Play CDD Video''', click here]<br />
</center><br />
CDD (short for Contract Driven Development) is a project developed at [http://se.ethz.ch ETH Zurich]. It adds advanced support for unit testing to EiffelStudio. With CDD EiffelStudio you can<br />
<br />
* Write test cases<br />
* Manage test cases (using tags)<br />
* Run test cases<br />
* View test outcomes<br />
* '''Automatically extract test cases'''<br />
<br />
If you have questions, feedback, or would like to report a bug please visit the [http://eiffelstudio.origo.ethz.ch/forum/20 CDD forum]. <br />
<br />
CDD EiffelStudio adds the following panel to regular EiffelStudio:<br />
<br />
[[Image:cdd_panel.png|center]]<br />
<br />
== News ==<br />
<br />
2.April.2008: CDD EiffelStudio Final 6 available<br />
* Less mess: Redundant or duplicate test cases are no longer extracted<br />
* Smoother upgrade: Cleaning a project will automatically clean the test suite<br />
* Fixed bug in invarant checking<br />
* Fixed bug that caused EiffelStudio to freeze in some situations<br />
* Improved logging<br />
* Installer ''might'' work with mingw on Windows now. (Not yet tested, reports welcome)<br />
<br />
== Download CDD ==<br />
<br />
The following packages contain the full EiffelStudio 6.1 plus the CDD extension. You do not need to have EiffelStudio installed already in order to install below packages. On Windows you do have to have either the Platform SDK or Visual C++ installed. Do not use EiffelStudio with the gcc/mingw or the .Net backend.<br />
<br />
=== Linux ===<br />
* Full Linux version: http://se.ethz.ch/people/leitner/cdd/Eiffel61_cdd_final_6.tar.bz2<br />
* Installation instructions: http://docs.eiffel.com/eiffelstudio/installation/studio/060_linux.html<br />
Notes:<br />
* If you are '''upgrading''' from a previous version, make sure you delete the old version first (rm -rf)<br />
<br />
Download the above file and install it just like you would install a EiffelStudio tar ball. Afterwards proceed to section "Using CDD". Make sure you set/update the environment variables PATH, ISE_EIFFEL, and ISE_PLATFORM according to the installation instructions.<br />
<br />
=== Windows ===<br />
<br />
* Full Windows version (with installer): http://n.ethz.ch/~moris/download/Eiffel61_cdd_final_6-windows.msi<br />
Notes:<br />
* Installation is independent of installations of official EiffelStudio 6.1 (neither overwrites nor invalidates nor is influenced by those) <br />
* If you are '''upgrading''' from a previous version, you first have to uninstall the old version then delete the existing precompilations (= delete EIFGENs in subdirectories of <INSTALL_DIRECTORY>/precomp/spec/windows/) and then install the new version.<br />
* Which C compiler to install?<br />
** Use the Microsoft C compiler either from Visual C++ or the Windows SDK:<br />
*** Visual C++ (up to 8.0, but no later, and only the non-express version)<br />
*** Windows SDK (up to version 6.0, but no later)<br />
** Do not use the gcc/mingw.<br />
** Do not use the .NET compiler backend. <br />
<br />
Have a look at http://dev.eiffel.com/Installing_Microsoft_C_compiler_6.1_and_older to learn how to install either Visual C++ or the Windows SDK for use with EiffelStudio. <br />
<br />
<br />
==== Windows Patch ====<br />
<br />
* Patch version for existing EiffelStudio CDD Edition Final 5 installation (does NOT work for official EiffelStudio 6.1 installation!): http://n.ethz.ch/~moris/download/Eiffel61_cdd_final_6-windows.zip<br />
* Replace <INSTALL_DIRECTORY>/studio/spec/windows/bin/ec.exe with ec.exe contained in archive<br />
* Delete existing precompilations (= delete EIFGENs in subdirectories of <INSTALL_DIRECTORY>/precomp/spec/windows/)<br />
* Recompile existing projects from scratch (use the "clean" option in the project load screen)<br />
<br />
== Documentation ==<br />
<br />
=== Manually Written Test Cases ===<br />
CDD Eiffelstudio allows you to create a new “empty” test case. These test cases are similar to jUnit test cases. A manually written test class must start with the word “TEST” and all test routines also have to start with the word “test”. It also has to inherit from class CDD_TEST_CASE.<br />
<br />
=== Extracted Test Cases ===<br />
CDD EiffelStudio automatically extracts test cases whenever you run your program and an exception is triggered. This feature is novel and not yet part of any other testing environment. You will be the first to try it out.<br />
<br />
=== Test outcomes ===<br />
A test case checks whether your program contains a particular bug. A test cases can fail indicating that the bug is present in your program, or pass indicating your program does not contain this bug. Sometimes test cases will be unresolved, in which case the testing framework was unable to find out whether the test case passed or failed. A test case can be unresolved for several reasons.<br />
<br />
<br />
[[Image:cdd_buttons.png|center]]<br />
<br />
=== Debug Test Case === <br />
Select a test case and press this button to run a test case in the debugger.<br />
<br />
=== Enable/Disable Execution of Test Cases in Background === <br />
If enabled, all test cases are retested every time you press compile. If disabled no test cases are executed.<br />
<br />
=== Enable/Disable automatic extraction of Test Cases === <br />
If enabled every time an exception is triggered a set of test cases that try to reproduce this exception is extracted. If disabled no test cases are extracted.<br />
<br />
=== Clean up/Delete === <br />
You can use the “Clean Up/Delete” button in two different ways. By simply pressing it you will delete all unresolved test cases. By pick and dropping a test case to the “Clean up/Delete” button (right click on test case, move mouse to button and right click again) you can delete a test case. By the way, test cases are just regular classes. So you can use all existing tools that apply to classes in EiffelStudio too.<br />
<br />
Update: To remove duplicate test cases (until the next cdd update), please use the command-line tool from the [http://clean-cdd.origo.ethz.ch/ clean-cdd project].<br />
<br />
=== Create new manual test class ===<br />
Press this button to create a empty test class. You can then edit the class to add manually written test cases. This is how a manually written test case can look like:<br />
<br />
<eiffel><br />
class TEST_BANK_ACCOUNT<br />
inherit CDD_TEST_CASE<br />
feature<br />
test_deposit<br />
local<br />
ba: BANK_ACCOUNT<br />
do<br />
create ba.make_with_balance (0)<br />
ba.deposit (100)<br />
check<br />
money_depisited: ba.balance = 100<br />
end<br />
end<br />
end<br />
</eiffel><br />
<br />
Redefine routine `set_up' or `tear_down' if you want something to be executed before resp. after every test routine of a class.<br />
<br />
[[Image:cdd_buttons_2.png|center]]<br />
<br />
=== Search for tags ===<br />
Enter keywords to search for paritcular test cases. Some tags are automatically set for you like the name of the test case. You can also easily add your own tags by adding an indexing item "tag" to your test class or routine:<br />
<br />
<eiffel><br />
indexing<br />
tag: "fixme"<br />
class TEST_BANK_ACCOUNT<br />
inherit CDD_TEST_CASE<br />
feature<br />
...<br />
end<br />
</eiffel><br />
<br />
Tags can be adde to all test routines and classes. Whether they are extracted or manually written does not matter.<br />
<br />
=== Restrict execution of test cases ===<br />
<br />
Once you have many test cases, you will run into situation where you don't want to execute all of them. The restrict button will help you to achieve this. As long as the "Restrict" button is pushed test cases that don't show up in the test case view will not be tested. Execution is restricted to those test cases that do show up.<br />
<br />
=== Change test case view ===<br />
<br />
Select one of several predefined test case views. For example you can group test cases by their outcome to quickly see only failing test cases.<br />
<br />
== Further Documentation and Common Problems ==<br />
Please visit [[Using CDD]] for further documentation or look at <br />
[[CDD Common Problems|Common Problems]] if you run into problems.<br />
<br />
== Related Publications ==<br />
<br />
* Leitner, A., Ciupa, I., Oriol, M., Meyer, B., Fiva, A., "Contract Driven Development = Test Driven Development - Writing Test Cases", Proceedings of ESEC/FSE'07: European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering 2007, (Dubrovnik, Croatia), September 2007 [http://se.ethz.ch/people/leitner/publications/cdd_leitner_esec_fse_2007.pdf (pdf)]<br />
* Sunghun Kim, Shay Artzi, and Michael D. Ernst, "reCrash: Making Crash Reproducible" MIT Computer Science and Artificial Intelligence Laboratory technical report MIT-CSAIL-TR-2007-054, (Cambridge, MA), November 20, 2007. [http://recrash.googlecode.com/files/MIT-CSAIL-TR-2007-054.pdf (pdf)]<br />
<br />
== Project Internal Stuff ==<br />
<br />
[[CddBranchInternal]]</div>Moriolhttps://dev.eiffel.com/index.php?title=Installing_Microsoft_C_compiler_6.1_and_older&diff=10913Installing Microsoft C compiler 6.1 and older2008-04-07T16:13:28Z<p>Moriol: /* Configuring C Compiler to Compile From the Command Line */</p>
<hr />
<div>[[Category:Windows]]<br />
In order to install EiffelStudio in Windows you will need to attain a C/C++ compiler. For 32-bit (x86) users, the installer comes complete with a free C/C++ compiler, which you can opt to install if no compatible C/C++ was detected on your system. For x86 users who do not want to use the packaged free C/C++ compiler, or if you are using an 64-bit (x64) operating system and are trying to install the 64-bit version of EiffelStudio, you will need to either attain a free Microsoft C/C++ compiler or use an installed version of [http://msdn2.microsoft.com/en-us/vstudio/default.aspx Visual Studio].<br />
<br />
== Using a Microsoft Visual C/C++ Compiler ==<br />
<br />
=== Attaining the Free Microsoft Windows SDK ===<br />
<br />
The Microsoft C compiler is now freely available by downloading the Windows SDK. Below you will find a description on how to set up the Microsoft SDK so that you can compile C code on Windows.<br />
<br />
The first thing to do is to download the Windows SDK from Microsoft's web site: [http://download.microsoft.com/download/a/7/7/a7767f09-0136-4a96-a1f8-276bf0ee31fa/Setup.exe Windows SDK setup.exe].<br />
<br />
{{Note| The Windows SDK download is currently called ''Microsoft Windows Software Development Kit for Windows Vista''. This is not a Windows Vista specific download! It can be used all Windows-based operating systems from Windows XP and up. See the Requirements section of the download page for more information. }}<br />
<br />
When installing it, make sure to install the '''Developer Tools''', in particular the '''Windows Vista Headers and Libraries''', the '''Visual C++ Compilers''' and the '''Windows Development Tools'''. Failure to do so would result in a non-working C compiler.<br />
<br />
=== Using Visual Studio ===<br />
<br />
If you already have [http://msdn2.microsoft.com/en-us/vstudio/default.aspx Visual Studio] on your system, that is Visual Studio and '''not''' one of the [http://www.microsoft.com/express/ Visual Studio Express] SKUs, EiffelStudio and the installer will utilize it.<br />
<br />
{{Note| Only [http://msdn2.microsoft.com/en-us/vstudio/default.aspx Visual Studio] versions released prior to a release of EiffelStudio are supported. For instance Visual Studio 2008 was released after EiffelStudio 6.1, as a result EiffelStudio 6.1 only supports Visual Studio versions up to the 2005 release. }}<br />
<br />
In order to use Visual Studio with EiffelStudio you need be sure you have installed the Visual C/C++ compiler and developer tools. It is also important you choose to install the correct compiler tools. As of Visual Studio 2008 the installation on a x64 operating system does '''not''', by default, install the x64 compiler tools. As a result the EiffelStudio installer will fail to find the installed C/C++ when using a x64 version of EiffelStudio. Be sure to customize the installation and under the '''Visual C++''' node, check '''X64 Compiler and Tools'''.<br />
<br />
== Configuring C Compiler to Compile From the Command Line ==<br />
After you have successfully installed the Windows SDK, the only thing you need to do is to configure some environment variables. The best way to configure them is to use the `setenv.cmd' batch file included in the Windows SDK:<br />
<br />
{{block| cmd.exe /V:ON /E:ON./K "C:\Program Files\Microsoft SDKs\Windows\v6.0\Bin\setenv.cmd" /Release }}<br />
<br />
After executing this command you can invoke the C compiler. Note that the prompt will change color, you may want to use `color' (taking no arguments) to restore to the default, or `color 07' to set it white on black.<br />
<br />
{{Note| Replace "C:\Program Files\Microsoft SDKs\Windows\v6.0" by the location where you installed the Windows SDK. }}<br />
<br />
=== Using espawn Instead ===<br />
Alternatively you can compile the utilize the [http://www.eiffelroom.com/tool/espawn espawn] tool. The tool mocks the environment used by the Eiffel compiler so global access to Windows SDK tools, such as the C/C++ compiler, is granted. As such there is no need to manually configure your system's environment variables or use the setenv.cmd.<br />
<br />
{{Note| espawn is not distributed with EiffelStudio so you will need a working Eiffel compiler to compile and make use of it, or you may visit [http://www.eiffelroom.com/tool/espawn eiffelroom] and download the tool.}}</div>Moriolhttps://dev.eiffel.com/index.php?title=Installing_Microsoft_C_compiler_6.1_and_older&diff=10912Installing Microsoft C compiler 6.1 and older2008-04-07T16:12:03Z<p>Moriol: /* Configuring C Compiler to Compile From the Command Line */</p>
<hr />
<div>[[Category:Windows]]<br />
In order to install EiffelStudio in Windows you will need to attain a C/C++ compiler. For 32-bit (x86) users, the installer comes complete with a free C/C++ compiler, which you can opt to install if no compatible C/C++ was detected on your system. For x86 users who do not want to use the packaged free C/C++ compiler, or if you are using an 64-bit (x64) operating system and are trying to install the 64-bit version of EiffelStudio, you will need to either attain a free Microsoft C/C++ compiler or use an installed version of [http://msdn2.microsoft.com/en-us/vstudio/default.aspx Visual Studio].<br />
<br />
== Using a Microsoft Visual C/C++ Compiler ==<br />
<br />
=== Attaining the Free Microsoft Windows SDK ===<br />
<br />
The Microsoft C compiler is now freely available by downloading the Windows SDK. Below you will find a description on how to set up the Microsoft SDK so that you can compile C code on Windows.<br />
<br />
The first thing to do is to download the Windows SDK from Microsoft's web site: [http://download.microsoft.com/download/a/7/7/a7767f09-0136-4a96-a1f8-276bf0ee31fa/Setup.exe Windows SDK setup.exe].<br />
<br />
{{Note| The Windows SDK download is currently called ''Microsoft Windows Software Development Kit for Windows Vista''. This is not a Windows Vista specific download! It can be used all Windows-based operating systems from Windows XP and up. See the Requirements section of the download page for more information. }}<br />
<br />
When installing it, make sure to install the '''Developer Tools''', in particular the '''Windows Vista Headers and Libraries''', the '''Visual C++ Compilers''' and the '''Windows Development Tools'''. Failure to do so would result in a non-working C compiler.<br />
<br />
=== Using Visual Studio ===<br />
<br />
If you already have [http://msdn2.microsoft.com/en-us/vstudio/default.aspx Visual Studio] on your system, that is Visual Studio and '''not''' one of the [http://www.microsoft.com/express/ Visual Studio Express] SKUs, EiffelStudio and the installer will utilize it.<br />
<br />
{{Note| Only [http://msdn2.microsoft.com/en-us/vstudio/default.aspx Visual Studio] versions released prior to a release of EiffelStudio are supported. For instance Visual Studio 2008 was released after EiffelStudio 6.1, as a result EiffelStudio 6.1 only supports Visual Studio versions up to the 2005 release. }}<br />
<br />
In order to use Visual Studio with EiffelStudio you need be sure you have installed the Visual C/C++ compiler and developer tools. It is also important you choose to install the correct compiler tools. As of Visual Studio 2008 the installation on a x64 operating system does '''not''', by default, install the x64 compiler tools. As a result the EiffelStudio installer will fail to find the installed C/C++ when using a x64 version of EiffelStudio. Be sure to customize the installation and under the '''Visual C++''' node, check '''X64 Compiler and Tools'''.<br />
<br />
== Configuring C Compiler to Compile From the Command Line ==<br />
After you have successfully installed the Windows SDK, the only thing you need to do is to configure some environment variables. The best way to configure them is to use the `setenv.cmd' batch file included in the Windows SDK:<br />
<br />
{{block| cmd.exe /V:ON /E:ON./K "C:\apps\Windows\v6.0\bin\setenv.cmd" /Release }}<br />
<br />
After executing this command you can invoke the C compiler. Note that the prompt will change color, you may want to use `color' (taking no arguments) to restore to the default, or `color 07' to set it white on black.<br />
<br />
{{Note| Replace ''c:\apps\Windows\v6.0'' by the location where you installed the Windows SDK.<br />
Generally it ends up being: cmd.exe /V:ON /E:ON./K "C:\Program Files\Microsoft SDKs\Windows\v6.0\Bin\setenv.cmd" /Release}}<br />
<br />
=== Using espawn Instead ===<br />
Alternatively you can compile the utilize the [http://www.eiffelroom.com/tool/espawn espawn] tool. The tool mocks the environment used by the Eiffel compiler so global access to Windows SDK tools, such as the C/C++ compiler, is granted. As such there is no need to manually configure your system's environment variables or use the setenv.cmd.<br />
<br />
{{Note| espawn is not distributed with EiffelStudio so you will need a working Eiffel compiler to compile and make use of it, or you may visit [http://www.eiffelroom.com/tool/espawn eiffelroom] and download the tool.}}</div>Moriolhttps://dev.eiffel.com/index.php?title=CddBranch&diff=10843CddBranch2008-03-18T17:47:38Z<p>Moriol: /* Clean up/Delete */</p>
<hr />
<div>[[Category:Testing]]<br />
[[Category:EiffelDebugger]]<br />
[[Category:CDD]]<br />
<br />
<br />
== What is the CDD EiffelStudio? ==<br />
<br />
[[Image:cdd_logo.png|center]]<br />
<br />
CDD (short for Contract Driven Development) is a project developed at [http://se.ethz.ch ETH Zurich]. It adds advanced support for unit testing to EiffelStudio. With CDD EiffelStudio you can<br />
<br />
* Write test cases<br />
* Manage test cases (using tags)<br />
* Run test cases<br />
* View test outcomes<br />
* ''''Automatically extract test cases''''<br />
<br />
If you have questions, feedback, or would like to report a bug please visit the [http://eiffelstudio.origo.ethz.ch/forum/20 CDD forum]. <br />
<br />
CDD EiffelStudio adds the following panel to regular EiffelStudio:<br />
<br />
[[Image:cdd_panel.png|center]]<br />
<br />
<br />
== Download CDD ==<br />
<br />
The following packages contain the full EiffelStudio 6.1 plus the CDD extension. You do not need to have EiffelStudio installed already in order to install below packages. On Windows you do have to have either the Platform SDK or Visual C++ installed. Do not use EiffelStudio with the gcc/mingw or the .Net backend.<br />
<br />
=== Linux ===<br />
* Full Linux version: http://se.ethz.ch/people/leitner/cdd/Eiffel61_cdd_final_5.tar.bz2<br />
* Installation instructions: http://docs.eiffel.com/eiffelstudio/installation/studio/060_linux.html<br />
<br />
Download the above file and install it just like you would install a EiffelStudio tar ball. Afterwards proceed to section "Using CDD". Make sure you set/update the environment variables PATH, ISE_EIFFEL, and ISE_PLATFORM according to the installation instructions.<br />
<br />
=== Windows ===<br />
<br />
* Full Windows version (with installer): http://n.ethz.ch/~moris/download/Eiffel61_cdd_final_5-windows.msi<br />
* Note 1: Installation is independent of installations of official EiffelStudio 6.1 (neither overwrites nor invalidates nor is influenced by those) <br />
* Note 2: If you have a previous installation of the CDD Edition of EiffelStudio installed, you need to uninstall it first. If you want to reuse the installation directory, you need to manually delete all EIFGENs in its subdirectories after the uninstall procedure.<br />
* Note 3: Do not use the gcc/mingw or the .NET compiler backend. You will have to use the Microsoft C compiler. You can get it either by installing Visual C++, or via (the freely available) Microsoft Platform SDK.Have a look at http://eiffelsoftware.origo.ethz.ch/Installing_Microsoft_C_compiler to learn how to install either compiler.<br />
<br />
== Documentation ==<br />
<br />
=== Manually Written Test Cases ===<br />
CDD Eiffelstudio allows you to create a new “empty” test case. These test cases are similar to jUnit test cases. A manually written test class must start with the word “TEST” and all test routines also have to start with the word “test”. It also has to inherit from class CDD_TEST_CASE.<br />
<br />
=== Extracted Test Cases ===<br />
CDD EiffelStudio automatically extracts test cases whenever you run your program and an exception is triggered. This feature is novel and not yet part of any other testing environment. You will be the first to try it out.<br />
<br />
=== Test outcomes ===<br />
A test case checks whether your program contains a particular bug. A test cases can fail indicating that the bug is present in your program, or pass indicating your program does not contain this bug. Sometimes test cases will be unresolved, in which case the testing framework was unable to find out whether the test case passed or failed. A test case can be unresolved for several reasons.<br />
<br />
<br />
[[Image:cdd_buttons.png|center]]<br />
<br />
=== Debug Test Case === <br />
Select a test case and press this button to run a test case in the debugger.<br />
<br />
=== Enable/Disable Execution of Test Cases in Background === <br />
If enabled, all test cases are retested every time you press compile. If disabled no test cases are executed.<br />
<br />
=== Enable/Disable automatic extraction of Test Cases === <br />
If enabled every time an exception is triggered a set of test cases that try to reproduce this exception is extracted. If disabled no test cases are extracted.<br />
<br />
=== Clean up/Delete === <br />
You can use the “Clean Up/Delete” button in two different ways. By simply pressing it you will delete all unresolved test cases. By pick and dropping a test case to the “Clean up/Delete” button (right click on test case, move mouse to button and right click again) you can delete a test case. By the way, test cases are just regular classes. So you can use all existing tools that apply to classes in EiffelStudio too.<br />
<br />
Update: To remove duplicate test cases (until the next cdd update), please use the command-line tool from the [http://clean-cdd.origo.ethz.ch/ clean-cdd project].<br />
<br />
=== Create new manual test class ===<br />
Press this button to create a empty test class. You can then edit the class to add manually written test cases. This is how a manually written test case can look like:<br />
<br />
<eiffel><br />
class TEST_BANK_ACCOUNT<br />
inherit CDD_TEST_CASE<br />
feature<br />
test_deposit<br />
local<br />
ba: BANK_ACCOUNT<br />
do<br />
create ba.make_with_balance (0)<br />
ba.deposit (100)<br />
check<br />
money_depisited: ba.balance = 100<br />
end<br />
end<br />
end<br />
</eiffel><br />
<br />
[[Image:cdd_buttons_2.png|center]]<br />
<br />
=== Search for tags ===<br />
Enter keywords to search for paritcular test cases. Some tags are automatically set for you like the name of the test case. You can also easily add your own tags by adding an indexing item "tag" to your test class or routine:<br />
<br />
<eiffel><br />
indexing<br />
tag: "fixme"<br />
class TEST_BANK_ACCOUNT<br />
inherit CDD_TEST_CASE<br />
feature<br />
...<br />
end<br />
</eiffel><br />
<br />
Tags can be adde to all test routines and classes. Whether they are extracted or manually written does not matter.<br />
<br />
=== Restrict execution of test cases ===<br />
<br />
Once you have many test cases, you will run into situation where you don't want to execute all of them. The restrict button will help you to achieve this. As long as the "Restrict" button is pushed test cases that don't show up in the test case view will not be tested. Execution is restricted to those test cases that do show up.<br />
<br />
=== Change test case view ===<br />
<br />
Select one of several predefined test case views. For example you can group test cases by their outcome to quickly see only failing test cases.<br />
<br />
== Further Documentation and Common Problems ==<br />
Please visit [[Using CDD]] for further documentation or look at <br />
[[CDD Common Problems|Common Problems]] if you run into problems.<br />
<br />
== Related Publications ==<br />
<br />
* Leitner, A., Ciupa, I., Oriol, M., Meyer, B., Fiva, A., "Contract Driven Development = Test Driven Development - Writing Test Cases", Proceedings of ESEC/FSE'07: European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering 2007, (Dubrovnik, Croatia), September 2007 [http://se.ethz.ch/people/leitner/publications/cdd_leitner_esec_fse_2007.pdf (pdf)]<br />
* Sunghun Kim, Shay Artzi, and Michael D. Ernst, "reCrash: Making Crash Reproducible" MIT Computer Science and Artificial Intelligence Laboratory technical report MIT-CSAIL-TR-2007-054, (Cambridge, MA), November 20, 2007. [http://recrash.googlecode.com/files/MIT-CSAIL-TR-2007-054.pdf (pdf)]<br />
<br />
== Project Internal Stuff ==<br />
<br />
[[CddBranchInternal]]</div>Moriolhttps://dev.eiffel.com/index.php?title=CddBranch&diff=10842CddBranch2008-03-18T17:46:40Z<p>Moriol: /* Clean up/Delete */</p>
<hr />
<div>[[Category:Testing]]<br />
[[Category:EiffelDebugger]]<br />
[[Category:CDD]]<br />
<br />
<br />
== What is the CDD EiffelStudio? ==<br />
<br />
[[Image:cdd_logo.png|center]]<br />
<br />
CDD (short for Contract Driven Development) is a project developed at [http://se.ethz.ch ETH Zurich]. It adds advanced support for unit testing to EiffelStudio. With CDD EiffelStudio you can<br />
<br />
* Write test cases<br />
* Manage test cases (using tags)<br />
* Run test cases<br />
* View test outcomes<br />
* ''''Automatically extract test cases''''<br />
<br />
If you have questions, feedback, or would like to report a bug please visit the [http://eiffelstudio.origo.ethz.ch/forum/20 CDD forum]. <br />
<br />
CDD EiffelStudio adds the following panel to regular EiffelStudio:<br />
<br />
[[Image:cdd_panel.png|center]]<br />
<br />
<br />
== Download CDD ==<br />
<br />
The following packages contain the full EiffelStudio 6.1 plus the CDD extension. You do not need to have EiffelStudio installed already in order to install below packages. On Windows you do have to have either the Platform SDK or Visual C++ installed. Do not use EiffelStudio with the gcc/mingw or the .Net backend.<br />
<br />
=== Linux ===<br />
* Full Linux version: http://se.ethz.ch/people/leitner/cdd/Eiffel61_cdd_final_5.tar.bz2<br />
* Installation instructions: http://docs.eiffel.com/eiffelstudio/installation/studio/060_linux.html<br />
<br />
Download the above file and install it just like you would install a EiffelStudio tar ball. Afterwards proceed to section "Using CDD". Make sure you set/update the environment variables PATH, ISE_EIFFEL, and ISE_PLATFORM according to the installation instructions.<br />
<br />
=== Windows ===<br />
<br />
* Full Windows version (with installer): http://n.ethz.ch/~moris/download/Eiffel61_cdd_final_5-windows.msi<br />
* Note 1: Installation is independent of installations of official EiffelStudio 6.1 (neither overwrites nor invalidates nor is influenced by those) <br />
* Note 2: If you have a previous installation of the CDD Edition of EiffelStudio installed, you need to uninstall it first. If you want to reuse the installation directory, you need to manually delete all EIFGENs in its subdirectories after the uninstall procedure.<br />
* Note 3: Do not use the gcc/mingw or the .NET compiler backend. You will have to use the Microsoft C compiler. You can get it either by installing Visual C++, or via (the freely available) Microsoft Platform SDK.Have a look at http://eiffelsoftware.origo.ethz.ch/Installing_Microsoft_C_compiler to learn how to install either compiler.<br />
<br />
== Documentation ==<br />
<br />
=== Manually Written Test Cases ===<br />
CDD Eiffelstudio allows you to create a new “empty” test case. These test cases are similar to jUnit test cases. A manually written test class must start with the word “TEST” and all test routines also have to start with the word “test”. It also has to inherit from class CDD_TEST_CASE.<br />
<br />
=== Extracted Test Cases ===<br />
CDD EiffelStudio automatically extracts test cases whenever you run your program and an exception is triggered. This feature is novel and not yet part of any other testing environment. You will be the first to try it out.<br />
<br />
=== Test outcomes ===<br />
A test case checks whether your program contains a particular bug. A test cases can fail indicating that the bug is present in your program, or pass indicating your program does not contain this bug. Sometimes test cases will be unresolved, in which case the testing framework was unable to find out whether the test case passed or failed. A test case can be unresolved for several reasons.<br />
<br />
<br />
[[Image:cdd_buttons.png|center]]<br />
<br />
=== Debug Test Case === <br />
Select a test case and press this button to run a test case in the debugger.<br />
<br />
=== Enable/Disable Execution of Test Cases in Background === <br />
If enabled, all test cases are retested every time you press compile. If disabled no test cases are executed.<br />
<br />
=== Enable/Disable automatic extraction of Test Cases === <br />
If enabled every time an exception is triggered a set of test cases that try to reproduce this exception is extracted. If disabled no test cases are extracted.<br />
<br />
=== Clean up/Delete === <br />
You can use the “Clean Up/Delete” button in two different ways. By simply pressing it you will delete all unresolved test cases. By pick and dropping a test case to the “Clean up/Delete” button (right click on test case, move mouse to button and right click again) you can delete a test case. By the way, test cases are just regular classes. So you can use all existing tools that apply to classes in EiffelStudio too.<br />
<br />
Update: To remove duplicate test cases, until the next cdd update, please use the command-line tool from the [http://clean-cdd.origo.ethz.ch/ clean-cdd project].<br />
<br />
=== Create new manual test class ===<br />
Press this button to create a empty test class. You can then edit the class to add manually written test cases. This is how a manually written test case can look like:<br />
<br />
<eiffel><br />
class TEST_BANK_ACCOUNT<br />
inherit CDD_TEST_CASE<br />
feature<br />
test_deposit<br />
local<br />
ba: BANK_ACCOUNT<br />
do<br />
create ba.make_with_balance (0)<br />
ba.deposit (100)<br />
check<br />
money_depisited: ba.balance = 100<br />
end<br />
end<br />
end<br />
</eiffel><br />
<br />
[[Image:cdd_buttons_2.png|center]]<br />
<br />
=== Search for tags ===<br />
Enter keywords to search for paritcular test cases. Some tags are automatically set for you like the name of the test case. You can also easily add your own tags by adding an indexing item "tag" to your test class or routine:<br />
<br />
<eiffel><br />
indexing<br />
tag: "fixme"<br />
class TEST_BANK_ACCOUNT<br />
inherit CDD_TEST_CASE<br />
feature<br />
...<br />
end<br />
</eiffel><br />
<br />
Tags can be adde to all test routines and classes. Whether they are extracted or manually written does not matter.<br />
<br />
=== Restrict execution of test cases ===<br />
<br />
Once you have many test cases, you will run into situation where you don't want to execute all of them. The restrict button will help you to achieve this. As long as the "Restrict" button is pushed test cases that don't show up in the test case view will not be tested. Execution is restricted to those test cases that do show up.<br />
<br />
=== Change test case view ===<br />
<br />
Select one of several predefined test case views. For example you can group test cases by their outcome to quickly see only failing test cases.<br />
<br />
== Further Documentation and Common Problems ==<br />
Please visit [[Using CDD]] for further documentation or look at <br />
[[CDD Common Problems|Common Problems]] if you run into problems.<br />
<br />
== Related Publications ==<br />
<br />
* Leitner, A., Ciupa, I., Oriol, M., Meyer, B., Fiva, A., "Contract Driven Development = Test Driven Development - Writing Test Cases", Proceedings of ESEC/FSE'07: European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering 2007, (Dubrovnik, Croatia), September 2007 [http://se.ethz.ch/people/leitner/publications/cdd_leitner_esec_fse_2007.pdf (pdf)]<br />
* Sunghun Kim, Shay Artzi, and Michael D. Ernst, "reCrash: Making Crash Reproducible" MIT Computer Science and Artificial Intelligence Laboratory technical report MIT-CSAIL-TR-2007-054, (Cambridge, MA), November 20, 2007. [http://recrash.googlecode.com/files/MIT-CSAIL-TR-2007-054.pdf (pdf)]<br />
<br />
== Project Internal Stuff ==<br />
<br />
[[CddBranchInternal]]</div>Moriolhttps://dev.eiffel.com/index.php?title=CddBranch&diff=10841CddBranch2008-03-18T17:45:54Z<p>Moriol: /* Clean up/Delete */</p>
<hr />
<div>[[Category:Testing]]<br />
[[Category:EiffelDebugger]]<br />
[[Category:CDD]]<br />
<br />
<br />
== What is the CDD EiffelStudio? ==<br />
<br />
[[Image:cdd_logo.png|center]]<br />
<br />
CDD (short for Contract Driven Development) is a project developed at [http://se.ethz.ch ETH Zurich]. It adds advanced support for unit testing to EiffelStudio. With CDD EiffelStudio you can<br />
<br />
* Write test cases<br />
* Manage test cases (using tags)<br />
* Run test cases<br />
* View test outcomes<br />
* ''''Automatically extract test cases''''<br />
<br />
If you have questions, feedback, or would like to report a bug please visit the [http://eiffelstudio.origo.ethz.ch/forum/20 CDD forum]. <br />
<br />
CDD EiffelStudio adds the following panel to regular EiffelStudio:<br />
<br />
[[Image:cdd_panel.png|center]]<br />
<br />
<br />
== Download CDD ==<br />
<br />
The following packages contain the full EiffelStudio 6.1 plus the CDD extension. You do not need to have EiffelStudio installed already in order to install below packages. On Windows you do have to have either the Platform SDK or Visual C++ installed. Do not use EiffelStudio with the gcc/mingw or the .Net backend.<br />
<br />
=== Linux ===<br />
* Full Linux version: http://se.ethz.ch/people/leitner/cdd/Eiffel61_cdd_final_5.tar.bz2<br />
* Installation instructions: http://docs.eiffel.com/eiffelstudio/installation/studio/060_linux.html<br />
<br />
Download the above file and install it just like you would install a EiffelStudio tar ball. Afterwards proceed to section "Using CDD". Make sure you set/update the environment variables PATH, ISE_EIFFEL, and ISE_PLATFORM according to the installation instructions.<br />
<br />
=== Windows ===<br />
<br />
* Full Windows version (with installer): http://n.ethz.ch/~moris/download/Eiffel61_cdd_final_5-windows.msi<br />
* Note 1: Installation is independent of installations of official EiffelStudio 6.1 (neither overwrites nor invalidates nor is influenced by those) <br />
* Note 2: If you have a previous installation of the CDD Edition of EiffelStudio installed, you need to uninstall it first. If you want to reuse the installation directory, you need to manually delete all EIFGENs in its subdirectories after the uninstall procedure.<br />
* Note 3: Do not use the gcc/mingw or the .NET compiler backend. You will have to use the Microsoft C compiler. You can get it either by installing Visual C++, or via (the freely available) Microsoft Platform SDK.Have a look at http://eiffelsoftware.origo.ethz.ch/Installing_Microsoft_C_compiler to learn how to install either compiler.<br />
<br />
== Documentation ==<br />
<br />
=== Manually Written Test Cases ===<br />
CDD Eiffelstudio allows you to create a new “empty” test case. These test cases are similar to jUnit test cases. A manually written test class must start with the word “TEST” and all test routines also have to start with the word “test”. It also has to inherit from class CDD_TEST_CASE.<br />
<br />
=== Extracted Test Cases ===<br />
CDD EiffelStudio automatically extracts test cases whenever you run your program and an exception is triggered. This feature is novel and not yet part of any other testing environment. You will be the first to try it out.<br />
<br />
=== Test outcomes ===<br />
A test case checks whether your program contains a particular bug. A test cases can fail indicating that the bug is present in your program, or pass indicating your program does not contain this bug. Sometimes test cases will be unresolved, in which case the testing framework was unable to find out whether the test case passed or failed. A test case can be unresolved for several reasons.<br />
<br />
<br />
[[Image:cdd_buttons.png|center]]<br />
<br />
=== Debug Test Case === <br />
Select a test case and press this button to run a test case in the debugger.<br />
<br />
=== Enable/Disable Execution of Test Cases in Background === <br />
If enabled, all test cases are retested every time you press compile. If disabled no test cases are executed.<br />
<br />
=== Enable/Disable automatic extraction of Test Cases === <br />
If enabled every time an exception is triggered a set of test cases that try to reproduce this exception is extracted. If disabled no test cases are extracted.<br />
<br />
=== Clean up/Delete === <br />
You can use the “Clean Up/Delete” button in two different ways. By simply pressing it you will delete all unresolved test cases. By pick and dropping a test case to the “Clean up/Delete” button (right click on test case, move mouse to button and right click again) you can delete a test case. By the way, test cases are just regular classes. So you can use all existing tools that apply to classes in EiffelStudio too.<br />
<br />
Update: To clean up duplicate test cases, until the next cdd update, please use the command-line tool from the [http://clean-cdd.origo.ethz.ch/ clean-cdd project].<br />
<br />
=== Create new manual test class ===<br />
Press this button to create a empty test class. You can then edit the class to add manually written test cases. This is how a manually written test case can look like:<br />
<br />
<eiffel><br />
class TEST_BANK_ACCOUNT<br />
inherit CDD_TEST_CASE<br />
feature<br />
test_deposit<br />
local<br />
ba: BANK_ACCOUNT<br />
do<br />
create ba.make_with_balance (0)<br />
ba.deposit (100)<br />
check<br />
money_depisited: ba.balance = 100<br />
end<br />
end<br />
end<br />
</eiffel><br />
<br />
[[Image:cdd_buttons_2.png|center]]<br />
<br />
=== Search for tags ===<br />
Enter keywords to search for paritcular test cases. Some tags are automatically set for you like the name of the test case. You can also easily add your own tags by adding an indexing item "tag" to your test class or routine:<br />
<br />
<eiffel><br />
indexing<br />
tag: "fixme"<br />
class TEST_BANK_ACCOUNT<br />
inherit CDD_TEST_CASE<br />
feature<br />
...<br />
end<br />
</eiffel><br />
<br />
Tags can be adde to all test routines and classes. Whether they are extracted or manually written does not matter.<br />
<br />
=== Restrict execution of test cases ===<br />
<br />
Once you have many test cases, you will run into situation where you don't want to execute all of them. The restrict button will help you to achieve this. As long as the "Restrict" button is pushed test cases that don't show up in the test case view will not be tested. Execution is restricted to those test cases that do show up.<br />
<br />
=== Change test case view ===<br />
<br />
Select one of several predefined test case views. For example you can group test cases by their outcome to quickly see only failing test cases.<br />
<br />
== Further Documentation and Common Problems ==<br />
Please visit [[Using CDD]] for further documentation or look at <br />
[[CDD Common Problems|Common Problems]] if you run into problems.<br />
<br />
== Related Publications ==<br />
<br />
* Leitner, A., Ciupa, I., Oriol, M., Meyer, B., Fiva, A., "Contract Driven Development = Test Driven Development - Writing Test Cases", Proceedings of ESEC/FSE'07: European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering 2007, (Dubrovnik, Croatia), September 2007 [http://se.ethz.ch/people/leitner/publications/cdd_leitner_esec_fse_2007.pdf (pdf)]<br />
* Sunghun Kim, Shay Artzi, and Michael D. Ernst, "reCrash: Making Crash Reproducible" MIT Computer Science and Artificial Intelligence Laboratory technical report MIT-CSAIL-TR-2007-054, (Cambridge, MA), November 20, 2007. [http://recrash.googlecode.com/files/MIT-CSAIL-TR-2007-054.pdf (pdf)]<br />
<br />
== Project Internal Stuff ==<br />
<br />
[[CddBranchInternal]]</div>Moriolhttps://dev.eiffel.com/index.php?title=CddBranch&diff=10840CddBranch2008-03-18T17:44:50Z<p>Moriol: </p>
<hr />
<div>[[Category:Testing]]<br />
[[Category:EiffelDebugger]]<br />
[[Category:CDD]]<br />
<br />
<br />
== What is the CDD EiffelStudio? ==<br />
<br />
[[Image:cdd_logo.png|center]]<br />
<br />
CDD (short for Contract Driven Development) is a project developed at [http://se.ethz.ch ETH Zurich]. It adds advanced support for unit testing to EiffelStudio. With CDD EiffelStudio you can<br />
<br />
* Write test cases<br />
* Manage test cases (using tags)<br />
* Run test cases<br />
* View test outcomes<br />
* ''''Automatically extract test cases''''<br />
<br />
If you have questions, feedback, or would like to report a bug please visit the [http://eiffelstudio.origo.ethz.ch/forum/20 CDD forum]. <br />
<br />
CDD EiffelStudio adds the following panel to regular EiffelStudio:<br />
<br />
[[Image:cdd_panel.png|center]]<br />
<br />
<br />
== Download CDD ==<br />
<br />
The following packages contain the full EiffelStudio 6.1 plus the CDD extension. You do not need to have EiffelStudio installed already in order to install below packages. On Windows you do have to have either the Platform SDK or Visual C++ installed. Do not use EiffelStudio with the gcc/mingw or the .Net backend.<br />
<br />
=== Linux ===<br />
* Full Linux version: http://se.ethz.ch/people/leitner/cdd/Eiffel61_cdd_final_5.tar.bz2<br />
* Installation instructions: http://docs.eiffel.com/eiffelstudio/installation/studio/060_linux.html<br />
<br />
Download the above file and install it just like you would install a EiffelStudio tar ball. Afterwards proceed to section "Using CDD". Make sure you set/update the environment variables PATH, ISE_EIFFEL, and ISE_PLATFORM according to the installation instructions.<br />
<br />
=== Windows ===<br />
<br />
* Full Windows version (with installer): http://n.ethz.ch/~moris/download/Eiffel61_cdd_final_5-windows.msi<br />
* Note 1: Installation is independent of installations of official EiffelStudio 6.1 (neither overwrites nor invalidates nor is influenced by those) <br />
* Note 2: If you have a previous installation of the CDD Edition of EiffelStudio installed, you need to uninstall it first. If you want to reuse the installation directory, you need to manually delete all EIFGENs in its subdirectories after the uninstall procedure.<br />
* Note 3: Do not use the gcc/mingw or the .NET compiler backend. You will have to use the Microsoft C compiler. You can get it either by installing Visual C++, or via (the freely available) Microsoft Platform SDK.Have a look at http://eiffelsoftware.origo.ethz.ch/Installing_Microsoft_C_compiler to learn how to install either compiler.<br />
<br />
== Documentation ==<br />
<br />
=== Manually Written Test Cases ===<br />
CDD Eiffelstudio allows you to create a new “empty” test case. These test cases are similar to jUnit test cases. A manually written test class must start with the word “TEST” and all test routines also have to start with the word “test”. It also has to inherit from class CDD_TEST_CASE.<br />
<br />
=== Extracted Test Cases ===<br />
CDD EiffelStudio automatically extracts test cases whenever you run your program and an exception is triggered. This feature is novel and not yet part of any other testing environment. You will be the first to try it out.<br />
<br />
=== Test outcomes ===<br />
A test case checks whether your program contains a particular bug. A test cases can fail indicating that the bug is present in your program, or pass indicating your program does not contain this bug. Sometimes test cases will be unresolved, in which case the testing framework was unable to find out whether the test case passed or failed. A test case can be unresolved for several reasons.<br />
<br />
<br />
[[Image:cdd_buttons.png|center]]<br />
<br />
=== Debug Test Case === <br />
Select a test case and press this button to run a test case in the debugger.<br />
<br />
=== Enable/Disable Execution of Test Cases in Background === <br />
If enabled, all test cases are retested every time you press compile. If disabled no test cases are executed.<br />
<br />
=== Enable/Disable automatic extraction of Test Cases === <br />
If enabled every time an exception is triggered a set of test cases that try to reproduce this exception is extracted. If disabled no test cases are extracted.<br />
<br />
=== Clean up/Delete === <br />
You can use the “Clean Up/Delete” button in two different ways. By simply pressing it you will delete all unresolved test cases. By pick and dropping a test case to the “Clean up/Delete” button (right click on test case, move mouse to button and right click again) you can delete a test case. By the way, test cases are just regular classes. So you can use all existing tools that apply to classes in EiffelStudio too.<br />
<br />
Update: To clean up duplicate test cases, please test the [http://clean-cdd.origo.ethz.ch/ clean-cdd project].<br />
<br />
=== Create new manual test class ===<br />
Press this button to create a empty test class. You can then edit the class to add manually written test cases. This is how a manually written test case can look like:<br />
<br />
<eiffel><br />
class TEST_BANK_ACCOUNT<br />
inherit CDD_TEST_CASE<br />
feature<br />
test_deposit<br />
local<br />
ba: BANK_ACCOUNT<br />
do<br />
create ba.make_with_balance (0)<br />
ba.deposit (100)<br />
check<br />
money_depisited: ba.balance = 100<br />
end<br />
end<br />
end<br />
</eiffel><br />
<br />
[[Image:cdd_buttons_2.png|center]]<br />
<br />
=== Search for tags ===<br />
Enter keywords to search for paritcular test cases. Some tags are automatically set for you like the name of the test case. You can also easily add your own tags by adding an indexing item "tag" to your test class or routine:<br />
<br />
<eiffel><br />
indexing<br />
tag: "fixme"<br />
class TEST_BANK_ACCOUNT<br />
inherit CDD_TEST_CASE<br />
feature<br />
...<br />
end<br />
</eiffel><br />
<br />
Tags can be adde to all test routines and classes. Whether they are extracted or manually written does not matter.<br />
<br />
=== Restrict execution of test cases ===<br />
<br />
Once you have many test cases, you will run into situation where you don't want to execute all of them. The restrict button will help you to achieve this. As long as the "Restrict" button is pushed test cases that don't show up in the test case view will not be tested. Execution is restricted to those test cases that do show up.<br />
<br />
=== Change test case view ===<br />
<br />
Select one of several predefined test case views. For example you can group test cases by their outcome to quickly see only failing test cases.<br />
<br />
== Further Documentation and Common Problems ==<br />
Please visit [[Using CDD]] for further documentation or look at <br />
[[CDD Common Problems|Common Problems]] if you run into problems.<br />
<br />
== Related Publications ==<br />
<br />
* Leitner, A., Ciupa, I., Oriol, M., Meyer, B., Fiva, A., "Contract Driven Development = Test Driven Development - Writing Test Cases", Proceedings of ESEC/FSE'07: European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering 2007, (Dubrovnik, Croatia), September 2007 [http://se.ethz.ch/people/leitner/publications/cdd_leitner_esec_fse_2007.pdf (pdf)]<br />
* Sunghun Kim, Shay Artzi, and Michael D. Ernst, "reCrash: Making Crash Reproducible" MIT Computer Science and Artificial Intelligence Laboratory technical report MIT-CSAIL-TR-2007-054, (Cambridge, MA), November 20, 2007. [http://recrash.googlecode.com/files/MIT-CSAIL-TR-2007-054.pdf (pdf)]<br />
<br />
== Project Internal Stuff ==<br />
<br />
[[CddBranchInternal]]</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=6567EiffelOnMac2006-12-07T13:09:32Z<p>Moriol: /* Installation using MacPorts */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
<br />
This page gives you an overview about how to get Eiffel Studio running on your Mac.<br />
<br />
<br />
== Installation using MacPorts ==<br />
<br />
MacPorts is a great tool that allows you to use many unix applications on the mac. We have created a package in the MacPorts repository that allows you to to install a fairly recent build with all dependencies in a convenient way:<br />
After installing MacPorts as described [http://trac.macosforge.org/projects/macports/wiki/InstallingMacPorts here] simply type<br />
<pre><br />
sudo port install eiffelstudio<br />
</pre><br />
and you're ready to go (after a few hours compiling that is :)).<br />
<br />
Note that you may need to precompile the libraries once with admin rights. To do that, you can type: "sudo estudio" on the command-line and then use the precompilation wizard (Tools->Precompilation wizard) or simply create a new project that will be precompiled.<br />
<br />
== Installing our builds ==<br />
Alternatively you can also use one of the binary packages we provide here:<br />
===PPC===<br />
If you use a Mac, that '''does not have an Intel Processor''', you can download EiffelStudio here:<br />
*[http://se.inf.ethz.ch/builds/es/EiffelStudio57-ppc.zip EiffelStudio57.app] (19.10.2006 - Revision 64380)<br />
----<br />
*or maybe you just want the [http://se.inf.ethz.ch/builds/es/Eiffel57.zip Eiffel57] folder (19.10.2006 - Revision 64380)<br />
<br />
===Intel===<br />
If yor use a Mac that '''has an Intel processor''', you can download EiffelStudio here:<br />
<br />
[http://se.inf.ethz.ch/builds/es/EiffelStudio57-intel.zip EiffelStudio57.app] (Revision 64493)<br />
----<br />
Or maybe you just want to get the [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-MacPorts_64493.tar.gz Eiffel57] folder. (Revision 64493)<br />
<br />
<br />
== FAQ ==<br />
Any more questions?<br />
<br />
<br />
==Hints==<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click<br />
* To set up the correct (default) browsers use "open" as your command-line browser in Tools>Preferences...<br />
[[Image:preferences_open_mac.jpg]]</div>Moriolhttps://dev.eiffel.com/index.php?title=CddBranch&diff=6005CddBranch2006-11-10T16:00:00Z<p>Moriol: /* How to Use */</p>
<hr />
<div>== Summary ==<br />
CDD is an extension to EiffelStudio that provides support for both automatic test case extraction and test execution.<br />
It is undistruptive to the development process of the user. The tool is in its earlys stages. Feedback and bug reports are <br />
very much appreciated. Please send them to mailto:andreas.leitner@inf.ethz.ch and or use the discussion page for this article.<br />
<br />
<br />
[[Image:video_still.png|center]]<br />
<br />
<center><br />
<h1><br />
[http://se.ethz.ch/people/leitner/cdd/video Play Video!]<br />
</h1><br />
</center><br />
<br />
== Installation ==<br />
<br />
=== Requirements ===<br />
* ISE Eiffel 5.7 (below version is recommended, other versions may or may not work)<br />
** Linux-x86: http://se.ethz.ch/people/leitner/cdd/Eiffel57_gpl_64493-linux-x86.tar.gz<br />
** Win32: http://se.ethz.ch/people/leitner/cdd/Eiffel57_gpl_64493-windows.msi<br />
<br />
=== Install CDD-Extension for EiffelStudio ===<br />
<br />
* Linux<br />
** Delete the directory $HOME/.es<br />
** Download http://se.ethz.ch/people/leitner/cdd/cdd_linux_x86_0_1_0.tgz<br />
** Unpack it over your existing EiffelStudio installation. (You have done it right when you are overwriting a few files in the process.)<br />
<br />
* Windows<br />
** Start the registry editor (regedit.exe) and delete the key "HKEY_CURRENT_USER\Software\ISE\Eiffel57"<br />
** Download http://se.ethz.ch/people/leitner/cdd/cdd_win32_0_1_0.zip<br />
** Unpack it over your existing EiffelStudio installation. (You have done it right when you are overwriting a few files in the process.)<br />
<br />
== How to Use ==<br />
Make sure you also have assertion checking enabled.<br />
This can be done easily in: "Project->Project Settings..." select assertions and select "True" for all of them (the more the better cdd will work).<br />
<br />
=== Step 1: Show Testing Window ===<br />
<br />
If not already visible, you need to make sure the testing windows are all properly displayed. You can make them appear by following the menu "View->Tools->Testing":<br />
<br />
[[Image:show_testing.png]]<br />
<br />
=== Step 2: Enable CDD-Testing ===<br />
To enable CDD-testing for your project, open your project and then enable CDD-testing, by clicking on the half-black / half-white button in the testing window. You can disable testing again at any time by pressing this button again.<br />
<br />
[[Image:enable_testing.png]]<br />
<br />
Now continue developing your project as usual. <br />
You will notice that for every exception that occurs a new test case shows up in the testing window. Test cases are automatically executed on each compilation to see whether you fixed that particular bug or not. A test case can be in one of three states:<br />
<br />
* "F" for failing - last time the test case was executed the original problem was reproduced<br />
* "OK" for passing - last time the test case was executed the original problem appeared fixed<br />
* "INV" for invalid - the test case is out of date (it can no longer run your program in the expected way)<br />
<br />
[[Image:test_case_states.png]]<br />
<br />
You can now delete test cases with the delete button and debug test cases with the debug button as shown below:<br />
<br />
[[Image:testing_buttons.png]]<br />
<br />
=== "bank_account" example walkthrough ===<br />
<br />
TODO: ...<br />
<br />
=== How Test Cases Are Extracted ===<br />
<br />
TODO: ...<br />
<br />
=== How to modify test cases by hand ===<br />
<br />
TODO: ...<br />
<br />
=== Re-extracting test cases ===<br />
<br />
TODO: ...<br />
<br />
== Release Notes ==<br />
<br />
* CDD can be quite fragile, if there you encounter problems you can do the following:<br />
** Look into the testing-log-window (bottom half of screen) and see what went wrong<br />
** Remove the directory EIFGENs/cdd_tester from your projects directory.<br />
** Disable precompiles if having problems<br />
** Have a look at the test cases (you can just pick&drop them into the editor)<br />
** Make sure your root cluster is not recursive.<br />
** Do enable assertion checking!<br />
<br />
<br />
<br />
== Source Code ==<br />
<br />
The source can be found on the cdd branch of the EiffelStudio svn repository (https://origo.ethz.ch/eiffelsoftware/es/branches/cdd/es).<br />
After compiling it you need to do the following to create a delivery<br />
<br />
* Take an existing delivery (5.7 final should be fine)<br />
* Copy the resulting executable ec.exe resp. ec to $ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin/<br />
* Copy the the file Delivery/eifinit/studio/default.xml to $ISE_EIFFEL/eifinit/studio/default.xml<br />
* Copy the directory Src/library/cdd to $ISE_EIFFEL/library/cdd<br />
<br />
<br />
== Development: TODO ==<br />
<br />
TODO:<br />
* Unit test suite for extraction<br />
* Sample apps with errors<br />
* Extract test case<br />
* Compile and run to see if we reproduce failure<br />
* Features under test, that are not exported to ANY are not supported.<br />
* When an inv violation occurs after a feature has been executed, the debugger does not give access to routine args.<br />
* Postcondition/Inv violation in creation procedures not covered yet?<br />
* object_under_test.withdraw ("Unable to get the arguments") ? when does this happen?<br />
* Test case result OK->Pass<br />
* POINTER in test case -> default_pointer<br />
* logging<br />
* Capture Prestate<br />
* ask for rerun (verification)<br />
* delivery (linux/windows)<br />
* better icons<br />
<br />
* when not possible to disable cdd, gray-out enable/disable button<br />
* be easy on the processor in the presence of many test cases<br />
* run relevant test cases first, show results as they tickle in<br />
* give lower priority to bg testing<br />
* always also capture prestate of routines down the stack -> new tc if current one goes invalid<br />
* BackInTimeDebuggerLight<br />
* Generate test suite root class already when enabling cdd (and compile test suite for the first time already too)<br />
* Invariant violation on creaton proc exit blames routine that contains create instruction not creation procedure<br />
<br />
=== Design rework ===<br />
* currently a test case knows if it is running or not.<br />
** a test case should not know this (it could be executed by several processes)<br />
*** a bg tester is executing a test case<br />
*** -> move status indication from test case to runner<br />
* dont pour everything through output<br />
** compiler stuff<br />
** test exe stuff<br />
* CDD_PRINTER, have a look at gobo printer for et<br />
** specifically the variable indentation support</div>Moriolhttps://dev.eiffel.com/index.php?title=CddBranch&diff=6004CddBranch2006-11-10T15:58:18Z<p>Moriol: /* How to Use */</p>
<hr />
<div>== Summary ==<br />
CDD is an extension to EiffelStudio that provides support for both automatic test case extraction and test execution.<br />
It is undistruptive to the development process of the user. The tool is in its earlys stages. Feedback and bug reports are <br />
very much appreciated. Please send them to mailto:andreas.leitner@inf.ethz.ch and or use the discussion page for this article.<br />
<br />
<br />
[[Image:video_still.png|center]]<br />
<br />
<center><br />
<h1><br />
[http://se.ethz.ch/people/leitner/cdd/video Play Video!]<br />
</h1><br />
</center><br />
<br />
== Installation ==<br />
<br />
=== Requirements ===<br />
* ISE Eiffel 5.7 (below version is recommended, other versions may or may not work)<br />
** Linux-x86: http://se.ethz.ch/people/leitner/cdd/Eiffel57_gpl_64493-linux-x86.tar.gz<br />
** Win32: http://se.ethz.ch/people/leitner/cdd/Eiffel57_gpl_64493-windows.msi<br />
<br />
=== Install CDD-Extension for EiffelStudio ===<br />
<br />
* Linux<br />
** Delete the directory $HOME/.es<br />
** Download http://se.ethz.ch/people/leitner/cdd/cdd_linux_x86_0_1_0.tgz<br />
** Unpack it over your existing EiffelStudio installation. (You have done it right when you are overwriting a few files in the process.)<br />
<br />
* Windows<br />
** Start the registry editor (regedit.exe) and delete the key "HKEY_CURRENT_USER\Software\ISE\Eiffel57"<br />
** Download http://se.ethz.ch/people/leitner/cdd/cdd_win32_0_1_0.zip<br />
** Unpack it over your existing EiffelStudio installation. (You have done it right when you are overwriting a few files in the process.)<br />
<br />
== How to Use ==<br />
Make sure you also have assertion checking enabled (the more the better cdd will work).<br />
This can be done easily in: "Project->Project Settings..." and then set assertions to True.<br />
<br />
=== Step 1: Show Testing Window ===<br />
<br />
If not already visible, you need to make sure the testing windows are all properly displayed. You can make them appear by following the menu "View->Tools->Testing":<br />
<br />
[[Image:show_testing.png]]<br />
<br />
=== Step 2: Enable CDD-Testing ===<br />
To enable CDD-testing for your project, open your project and then enable CDD-testing, by clicking on the half-black / half-white button in the testing window. You can disable testing again at any time by pressing this button again.<br />
<br />
[[Image:enable_testing.png]]<br />
<br />
Now continue developing your project as usual. <br />
You will notice that for every exception that occurs a new test case shows up in the testing window. Test cases are automatically executed on each compilation to see whether you fixed that particular bug or not. A test case can be in one of three states:<br />
<br />
* "F" for failing - last time the test case was executed the original problem was reproduced<br />
* "OK" for passing - last time the test case was executed the original problem appeared fixed<br />
* "INV" for invalid - the test case is out of date (it can no longer run your program in the expected way)<br />
<br />
[[Image:test_case_states.png]]<br />
<br />
You can now delete test cases with the delete button and debug test cases with the debug button as shown below:<br />
<br />
[[Image:testing_buttons.png]]<br />
<br />
=== "bank_account" example walkthrough ===<br />
<br />
TODO: ...<br />
<br />
=== How Test Cases Are Extracted ===<br />
<br />
TODO: ...<br />
<br />
=== How to modify test cases by hand ===<br />
<br />
TODO: ...<br />
<br />
=== Re-extracting test cases ===<br />
<br />
TODO: ...<br />
<br />
== Release Notes ==<br />
<br />
* CDD can be quite fragile, if there you encounter problems you can do the following:<br />
** Look into the testing-log-window (bottom half of screen) and see what went wrong<br />
** Remove the directory EIFGENs/cdd_tester from your projects directory.<br />
** Disable precompiles if having problems<br />
** Have a look at the test cases (you can just pick&drop them into the editor)<br />
** Make sure your root cluster is not recursive.<br />
** Do enable assertion checking!<br />
<br />
<br />
<br />
== Source Code ==<br />
<br />
The source can be found on the cdd branch of the EiffelStudio svn repository (https://origo.ethz.ch/eiffelsoftware/es/branches/cdd/es).<br />
After compiling it you need to do the following to create a delivery<br />
<br />
* Take an existing delivery (5.7 final should be fine)<br />
* Copy the resulting executable ec.exe resp. ec to $ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin/<br />
* Copy the the file Delivery/eifinit/studio/default.xml to $ISE_EIFFEL/eifinit/studio/default.xml<br />
* Copy the directory Src/library/cdd to $ISE_EIFFEL/library/cdd<br />
<br />
<br />
== Development: TODO ==<br />
<br />
TODO:<br />
* Unit test suite for extraction<br />
* Sample apps with errors<br />
* Extract test case<br />
* Compile and run to see if we reproduce failure<br />
* Features under test, that are not exported to ANY are not supported.<br />
* When an inv violation occurs after a feature has been executed, the debugger does not give access to routine args.<br />
* Postcondition/Inv violation in creation procedures not covered yet?<br />
* object_under_test.withdraw ("Unable to get the arguments") ? when does this happen?<br />
* Test case result OK->Pass<br />
* POINTER in test case -> default_pointer<br />
* logging<br />
* Capture Prestate<br />
* ask for rerun (verification)<br />
* delivery (linux/windows)<br />
* better icons<br />
<br />
* when not possible to disable cdd, gray-out enable/disable button<br />
* be easy on the processor in the presence of many test cases<br />
* run relevant test cases first, show results as they tickle in<br />
* give lower priority to bg testing<br />
* always also capture prestate of routines down the stack -> new tc if current one goes invalid<br />
* BackInTimeDebuggerLight<br />
* Generate test suite root class already when enabling cdd (and compile test suite for the first time already too)<br />
* Invariant violation on creaton proc exit blames routine that contains create instruction not creation procedure<br />
<br />
=== Design rework ===<br />
* currently a test case knows if it is running or not.<br />
** a test case should not know this (it could be executed by several processes)<br />
*** a bg tester is executing a test case<br />
*** -> move status indication from test case to runner<br />
* dont pour everything through output<br />
** compiler stuff<br />
** test exe stuff<br />
* CDD_PRINTER, have a look at gobo printer for et<br />
** specifically the variable indentation support</div>Moriolhttps://dev.eiffel.com/index.php?title=CddBranch&diff=6003CddBranch2006-11-10T15:57:55Z<p>Moriol: /* How to Use */</p>
<hr />
<div>== Summary ==<br />
CDD is an extension to EiffelStudio that provides support for both automatic test case extraction and test execution.<br />
It is undistruptive to the development process of the user. The tool is in its earlys stages. Feedback and bug reports are <br />
very much appreciated. Please send them to mailto:andreas.leitner@inf.ethz.ch and or use the discussion page for this article.<br />
<br />
<br />
[[Image:video_still.png|center]]<br />
<br />
<center><br />
<h1><br />
[http://se.ethz.ch/people/leitner/cdd/video Play Video!]<br />
</h1><br />
</center><br />
<br />
== Installation ==<br />
<br />
=== Requirements ===<br />
* ISE Eiffel 5.7 (below version is recommended, other versions may or may not work)<br />
** Linux-x86: http://se.ethz.ch/people/leitner/cdd/Eiffel57_gpl_64493-linux-x86.tar.gz<br />
** Win32: http://se.ethz.ch/people/leitner/cdd/Eiffel57_gpl_64493-windows.msi<br />
<br />
=== Install CDD-Extension for EiffelStudio ===<br />
<br />
* Linux<br />
** Delete the directory $HOME/.es<br />
** Download http://se.ethz.ch/people/leitner/cdd/cdd_linux_x86_0_1_0.tgz<br />
** Unpack it over your existing EiffelStudio installation. (You have done it right when you are overwriting a few files in the process.)<br />
<br />
* Windows<br />
** Start the registry editor (regedit.exe) and delete the key "HKEY_CURRENT_USER\Software\ISE\Eiffel57"<br />
** Download http://se.ethz.ch/people/leitner/cdd/cdd_win32_0_1_0.zip<br />
** Unpack it over your existing EiffelStudio installation. (You have done it right when you are overwriting a few files in the process.)<br />
<br />
== How to Use ==<br />
Make sure you also have assertion checking enabled (the more the better cdd will work).<br />
This can be done easily in: Project->Project Settings and then set assertions to True.<br />
<br />
=== Step 1: Show Testing Window ===<br />
<br />
If not already visible, you need to make sure the testing windows are all properly displayed. You can make them appear by following the menu "View->Tools->Testing":<br />
<br />
[[Image:show_testing.png]]<br />
<br />
=== Step 2: Enable CDD-Testing ===<br />
To enable CDD-testing for your project, open your project and then enable CDD-testing, by clicking on the half-black / half-white button in the testing window. You can disable testing again at any time by pressing this button again.<br />
<br />
[[Image:enable_testing.png]]<br />
<br />
Now continue developing your project as usual. <br />
You will notice that for every exception that occurs a new test case shows up in the testing window. Test cases are automatically executed on each compilation to see whether you fixed that particular bug or not. A test case can be in one of three states:<br />
<br />
* "F" for failing - last time the test case was executed the original problem was reproduced<br />
* "OK" for passing - last time the test case was executed the original problem appeared fixed<br />
* "INV" for invalid - the test case is out of date (it can no longer run your program in the expected way)<br />
<br />
[[Image:test_case_states.png]]<br />
<br />
You can now delete test cases with the delete button and debug test cases with the debug button as shown below:<br />
<br />
[[Image:testing_buttons.png]]<br />
<br />
=== "bank_account" example walkthrough ===<br />
<br />
TODO: ...<br />
<br />
=== How Test Cases Are Extracted ===<br />
<br />
TODO: ...<br />
<br />
=== How to modify test cases by hand ===<br />
<br />
TODO: ...<br />
<br />
=== Re-extracting test cases ===<br />
<br />
TODO: ...<br />
<br />
== Release Notes ==<br />
<br />
* CDD can be quite fragile, if there you encounter problems you can do the following:<br />
** Look into the testing-log-window (bottom half of screen) and see what went wrong<br />
** Remove the directory EIFGENs/cdd_tester from your projects directory.<br />
** Disable precompiles if having problems<br />
** Have a look at the test cases (you can just pick&drop them into the editor)<br />
** Make sure your root cluster is not recursive.<br />
** Do enable assertion checking!<br />
<br />
<br />
<br />
== Source Code ==<br />
<br />
The source can be found on the cdd branch of the EiffelStudio svn repository (https://origo.ethz.ch/eiffelsoftware/es/branches/cdd/es).<br />
After compiling it you need to do the following to create a delivery<br />
<br />
* Take an existing delivery (5.7 final should be fine)<br />
* Copy the resulting executable ec.exe resp. ec to $ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin/<br />
* Copy the the file Delivery/eifinit/studio/default.xml to $ISE_EIFFEL/eifinit/studio/default.xml<br />
* Copy the directory Src/library/cdd to $ISE_EIFFEL/library/cdd<br />
<br />
<br />
== Development: TODO ==<br />
<br />
TODO:<br />
* Unit test suite for extraction<br />
* Sample apps with errors<br />
* Extract test case<br />
* Compile and run to see if we reproduce failure<br />
* Features under test, that are not exported to ANY are not supported.<br />
* When an inv violation occurs after a feature has been executed, the debugger does not give access to routine args.<br />
* Postcondition/Inv violation in creation procedures not covered yet?<br />
* object_under_test.withdraw ("Unable to get the arguments") ? when does this happen?<br />
* Test case result OK->Pass<br />
* POINTER in test case -> default_pointer<br />
* logging<br />
* Capture Prestate<br />
* ask for rerun (verification)<br />
* delivery (linux/windows)<br />
* better icons<br />
<br />
* when not possible to disable cdd, gray-out enable/disable button<br />
* be easy on the processor in the presence of many test cases<br />
* run relevant test cases first, show results as they tickle in<br />
* give lower priority to bg testing<br />
* always also capture prestate of routines down the stack -> new tc if current one goes invalid<br />
* BackInTimeDebuggerLight<br />
* Generate test suite root class already when enabling cdd (and compile test suite for the first time already too)<br />
* Invariant violation on creaton proc exit blames routine that contains create instruction not creation procedure<br />
<br />
=== Design rework ===<br />
* currently a test case knows if it is running or not.<br />
** a test case should not know this (it could be executed by several processes)<br />
*** a bg tester is executing a test case<br />
*** -> move status indication from test case to runner<br />
* dont pour everything through output<br />
** compiler stuff<br />
** test exe stuff<br />
* CDD_PRINTER, have a look at gobo printer for et<br />
** specifically the variable indentation support</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=5365EiffelOnMac2006-10-25T09:03:12Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently three separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (19.10.2006 - Revision 64380) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_64380-macosx-ppc.tar.7z Eiffel57_gpl_64380-macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from macports and use this command: <pre>7za x -so Eiffel57_gpl_64380-macosx-ppc.tar.7z | tar xfv - </pre> Or get the [http://sixtyfive.xmghosting.com/ 7zX] tool to unpack the 7z file.<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
* '''MacOS X - Intel''' (25.10.2006 - Revision 64493) : <br />
** Compiled Archive with darwinports (the archive is compiled using darwin ports - so you SHOULD have installed the latest version of darwin ports): [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-DarwinPorts_64493.tar.gz Eiffel57_gpl_macosx-intel-DarwinPorts_64493.tar.gz]<br />
** Compiled Archive with macports (the archive is compiled using mac ports - so you SHOULD have installed the latest version of mac ports): [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-MacPorts_64493.tar.gz Eiffel57_gpl_macosx-intel-MacPorts_64493.tar.gz]<br />
<br />
==Compiling Eiffel Studio using the Porter Package==<br />
Since the binaries above are often out of date, you might want to build the latest release yourself.<br />
# Make sure that you have all requirements that are listed in the readme section and that you have set the ISE_PLATFORM environment variable to macosx-ppc or macosx-x86 depending on your platform.<br />
# Download the latest Porter Package from [http://eiffelsoftware.origo.ethz.ch/downloads/builds/ here] (PorterPackage_57_XXXXX.tar)<br />
# Extract the PorterPackage, double-clicking should work<br />
# Open a Terminal window and cd into the PorterPackage directory<br />
# Compile the Porter Package:<pre>./compile_exes $ISE_PLATFORM</pre> This will compile the complete EiffelStudio Package. This takes 1-2 hours depending on your machine.<br />
# '''IMPORTANT''' : The installation now resides in PorterPackage/Eiffel57. In order to make it work you have to set execution permissions on the ec executable. <pre>chmod a+x Eiffel57/studio/spec/$ISE_PLATFORM/bin/ec</pre><br />
# Now you can move the Eiffel57 directory to any place you want. Just make sure to set the ISE_EIFFEL evironment variable accordingly.<br />
# If you want the gobo tools you can compile them using this script, which will place them in the correct directory and clean up: [http://n.ethz.ch/student/roederja/download/gobo-script.sh gobo-script.sh]<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
Note: For Mac OS 10.4 users, X11 is on the install Disk 1 (in System/Installation/Packages/X11User.pkg)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* MacPorts (http://www.macports.org) previously known as [http://darwinports.opendarwin.org/ Darwin Ports]<br />
* GTK2 from MacPorts: Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.7z or the tgz file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$ISE_EIFFEL # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your macports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click<br />
* To set up the correct (default) browsers use extensively "open" as your command-line browser in Tools>Preferences...<br />
[[Image:preferences_open_mac.jpg]]</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=5364EiffelOnMac2006-10-25T09:02:41Z<p>Moriol: /* Hints */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently three separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (19.10.2006 - Revision 64380) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_64380-macosx-ppc.tar.7z Eiffel57_gpl_64380-macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from macports and use this command: <pre>7za x -so Eiffel57_gpl_64380-macosx-ppc.tar.7z | tar xfv - </pre> Or get the [http://sixtyfive.xmghosting.com/ 7zX] tool to unpack the 7z file.<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
* '''MacOS X - Intel''' (20.10.2006 - Revision 64493) : <br />
** Compiled Archive with darwinports (the archive is compiled using darwin ports - so you SHOULD have installed the latest version of darwin ports): [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-DarwinPorts_64493.tar.gz Eiffel57_gpl_macosx-intel-DarwinPorts_64493.tar.gz]<br />
** Compiled Archive with macports (the archive is compiled using mac ports - so you SHOULD have installed the latest version of mac ports): [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-MacPorts_64493.tar.gz Eiffel57_gpl_macosx-intel-MacPorts_64493.tar.gz]<br />
<br />
==Compiling Eiffel Studio using the Porter Package==<br />
Since the binaries above are often out of date, you might want to build the latest release yourself.<br />
# Make sure that you have all requirements that are listed in the readme section and that you have set the ISE_PLATFORM environment variable to macosx-ppc or macosx-x86 depending on your platform.<br />
# Download the latest Porter Package from [http://eiffelsoftware.origo.ethz.ch/downloads/builds/ here] (PorterPackage_57_XXXXX.tar)<br />
# Extract the PorterPackage, double-clicking should work<br />
# Open a Terminal window and cd into the PorterPackage directory<br />
# Compile the Porter Package:<pre>./compile_exes $ISE_PLATFORM</pre> This will compile the complete EiffelStudio Package. This takes 1-2 hours depending on your machine.<br />
# '''IMPORTANT''' : The installation now resides in PorterPackage/Eiffel57. In order to make it work you have to set execution permissions on the ec executable. <pre>chmod a+x Eiffel57/studio/spec/$ISE_PLATFORM/bin/ec</pre><br />
# Now you can move the Eiffel57 directory to any place you want. Just make sure to set the ISE_EIFFEL evironment variable accordingly.<br />
# If you want the gobo tools you can compile them using this script, which will place them in the correct directory and clean up: [http://n.ethz.ch/student/roederja/download/gobo-script.sh gobo-script.sh]<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
Note: For Mac OS 10.4 users, X11 is on the install Disk 1 (in System/Installation/Packages/X11User.pkg)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* MacPorts (http://www.macports.org) previously known as [http://darwinports.opendarwin.org/ Darwin Ports]<br />
* GTK2 from MacPorts: Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.7z or the tgz file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$ISE_EIFFEL # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your macports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click<br />
* To set up the correct (default) browsers use extensively "open" as your command-line browser in Tools>Preferences...<br />
[[Image:preferences_open_mac.jpg]]</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=5363EiffelOnMac2006-10-25T09:02:02Z<p>Moriol: /* Hints */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently three separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (19.10.2006 - Revision 64380) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_64380-macosx-ppc.tar.7z Eiffel57_gpl_64380-macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from macports and use this command: <pre>7za x -so Eiffel57_gpl_64380-macosx-ppc.tar.7z | tar xfv - </pre> Or get the [http://sixtyfive.xmghosting.com/ 7zX] tool to unpack the 7z file.<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
* '''MacOS X - Intel''' (20.10.2006 - Revision 64493) : <br />
** Compiled Archive with darwinports (the archive is compiled using darwin ports - so you SHOULD have installed the latest version of darwin ports): [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-DarwinPorts_64493.tar.gz Eiffel57_gpl_macosx-intel-DarwinPorts_64493.tar.gz]<br />
** Compiled Archive with macports (the archive is compiled using mac ports - so you SHOULD have installed the latest version of mac ports): [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-MacPorts_64493.tar.gz Eiffel57_gpl_macosx-intel-MacPorts_64493.tar.gz]<br />
<br />
==Compiling Eiffel Studio using the Porter Package==<br />
Since the binaries above are often out of date, you might want to build the latest release yourself.<br />
# Make sure that you have all requirements that are listed in the readme section and that you have set the ISE_PLATFORM environment variable to macosx-ppc or macosx-x86 depending on your platform.<br />
# Download the latest Porter Package from [http://eiffelsoftware.origo.ethz.ch/downloads/builds/ here] (PorterPackage_57_XXXXX.tar)<br />
# Extract the PorterPackage, double-clicking should work<br />
# Open a Terminal window and cd into the PorterPackage directory<br />
# Compile the Porter Package:<pre>./compile_exes $ISE_PLATFORM</pre> This will compile the complete EiffelStudio Package. This takes 1-2 hours depending on your machine.<br />
# '''IMPORTANT''' : The installation now resides in PorterPackage/Eiffel57. In order to make it work you have to set execution permissions on the ec executable. <pre>chmod a+x Eiffel57/studio/spec/$ISE_PLATFORM/bin/ec</pre><br />
# Now you can move the Eiffel57 directory to any place you want. Just make sure to set the ISE_EIFFEL evironment variable accordingly.<br />
# If you want the gobo tools you can compile them using this script, which will place them in the correct directory and clean up: [http://n.ethz.ch/student/roederja/download/gobo-script.sh gobo-script.sh]<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
Note: For Mac OS 10.4 users, X11 is on the install Disk 1 (in System/Installation/Packages/X11User.pkg)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* MacPorts (http://www.macports.org) previously known as [http://darwinports.opendarwin.org/ Darwin Ports]<br />
* GTK2 from MacPorts: Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.7z or the tgz file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$ISE_EIFFEL # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your macports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click<br />
* To set up the correct (default) browsers use extensively "open" as your command-line browser e.g.<br />
[[Image:preferences_open_mac.jpg]]</div>Moriolhttps://dev.eiffel.com/index.php?title=File:Preferences_open_mac.jpg&diff=5362File:Preferences open mac.jpg2006-10-25T09:01:21Z<p>Moriol: </p>
<hr />
<div></div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=5361EiffelOnMac2006-10-25T08:36:28Z<p>Moriol: /* Hints */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently three separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (19.10.2006 - Revision 64380) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_64380-macosx-ppc.tar.7z Eiffel57_gpl_64380-macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from macports and use this command: <pre>7za x -so Eiffel57_gpl_64380-macosx-ppc.tar.7z | tar xfv - </pre> Or get the [http://sixtyfive.xmghosting.com/ 7zX] tool to unpack the 7z file.<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
* '''MacOS X - Intel''' (20.10.2006 - Revision 64493) : <br />
** Compiled Archive with darwinports (the archive is compiled using darwin ports - so you SHOULD have installed the latest version of darwin ports): [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-DarwinPorts_64493.tar.gz Eiffel57_gpl_macosx-intel-DarwinPorts_64493.tar.gz]<br />
** Compiled Archive with macports (the archive is compiled using mac ports - so you SHOULD have installed the latest version of mac ports): [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-MacPorts_64493.tar.gz Eiffel57_gpl_macosx-intel-MacPorts_64493.tar.gz]<br />
<br />
==Compiling Eiffel Studio using the Porter Package==<br />
Since the binaries above are often out of date, you might want to build the latest release yourself.<br />
# Make sure that you have all requirements that are listed in the readme section and that you have set the ISE_PLATFORM environment variable to macosx-ppc or macosx-x86 depending on your platform.<br />
# Download the latest Porter Package from [http://eiffelsoftware.origo.ethz.ch/downloads/builds/ here] (PorterPackage_57_XXXXX.tar)<br />
# Extract the PorterPackage, double-clicking should work<br />
# Open a Terminal window and cd into the PorterPackage directory<br />
# Compile the Porter Package:<pre>./compile_exes $ISE_PLATFORM</pre> This will compile the complete EiffelStudio Package. This takes 1-2 hours depending on your machine.<br />
# '''IMPORTANT''' : The installation now resides in PorterPackage/Eiffel57. In order to make it work you have to set execution permissions on the ec executable. <pre>chmod a+x Eiffel57/studio/spec/$ISE_PLATFORM/bin/ec</pre><br />
# Now you can move the Eiffel57 directory to any place you want. Just make sure to set the ISE_EIFFEL evironment variable accordingly.<br />
# If you want the gobo tools you can compile them using this script, which will place them in the correct directory and clean up: [http://n.ethz.ch/student/roederja/download/gobo-script.sh gobo-script.sh]<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
Note: For Mac OS 10.4 users, X11 is on the install Disk 1 (in System/Installation/Packages/X11User.pkg)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* MacPorts (http://www.macports.org) previously known as [http://darwinports.opendarwin.org/ Darwin Ports]<br />
* GTK2 from MacPorts: Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.7z or the tgz file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$ISE_EIFFEL # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your macports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click<br />
* To set up the correct (default) browsers use extensively "open" as your command-line browser e.g.</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=5360EiffelOnMac2006-10-25T08:35:27Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently three separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (19.10.2006 - Revision 64380) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_64380-macosx-ppc.tar.7z Eiffel57_gpl_64380-macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from macports and use this command: <pre>7za x -so Eiffel57_gpl_64380-macosx-ppc.tar.7z | tar xfv - </pre> Or get the [http://sixtyfive.xmghosting.com/ 7zX] tool to unpack the 7z file.<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
* '''MacOS X - Intel''' (20.10.2006 - Revision 64493) : <br />
** Compiled Archive with darwinports (the archive is compiled using darwin ports - so you SHOULD have installed the latest version of darwin ports): [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-DarwinPorts_64493.tar.gz Eiffel57_gpl_macosx-intel-DarwinPorts_64493.tar.gz]<br />
** Compiled Archive with macports (the archive is compiled using mac ports - so you SHOULD have installed the latest version of mac ports): [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-MacPorts_64493.tar.gz Eiffel57_gpl_macosx-intel-MacPorts_64493.tar.gz]<br />
<br />
==Compiling Eiffel Studio using the Porter Package==<br />
Since the binaries above are often out of date, you might want to build the latest release yourself.<br />
# Make sure that you have all requirements that are listed in the readme section and that you have set the ISE_PLATFORM environment variable to macosx-ppc or macosx-x86 depending on your platform.<br />
# Download the latest Porter Package from [http://eiffelsoftware.origo.ethz.ch/downloads/builds/ here] (PorterPackage_57_XXXXX.tar)<br />
# Extract the PorterPackage, double-clicking should work<br />
# Open a Terminal window and cd into the PorterPackage directory<br />
# Compile the Porter Package:<pre>./compile_exes $ISE_PLATFORM</pre> This will compile the complete EiffelStudio Package. This takes 1-2 hours depending on your machine.<br />
# '''IMPORTANT''' : The installation now resides in PorterPackage/Eiffel57. In order to make it work you have to set execution permissions on the ec executable. <pre>chmod a+x Eiffel57/studio/spec/$ISE_PLATFORM/bin/ec</pre><br />
# Now you can move the Eiffel57 directory to any place you want. Just make sure to set the ISE_EIFFEL evironment variable accordingly.<br />
# If you want the gobo tools you can compile them using this script, which will place them in the correct directory and clean up: [http://n.ethz.ch/student/roederja/download/gobo-script.sh gobo-script.sh]<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
Note: For Mac OS 10.4 users, X11 is on the install Disk 1 (in System/Installation/Packages/X11User.pkg)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* MacPorts (http://www.macports.org) previously known as [http://darwinports.opendarwin.org/ Darwin Ports]<br />
* GTK2 from MacPorts: Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.7z or the tgz file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$ISE_EIFFEL # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your macports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=5334EiffelOnMac2006-10-24T16:13:37Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently three separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (19.10.2006 - Revision 64380) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_64380-macosx-ppc.tar.7z Eiffel57_gpl_64380-macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from macports and use this command: <pre>7za x -so Eiffel57_gpl_64380-macosx-ppc.tar.7z | tar xfv - </pre> Or get the [http://sixtyfive.xmghosting.com/ 7zX] tool to unpack the 7z file.<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
* '''MacOS X - Intel''' (20.10.2006 - Revision 64380) : <br />
** Compiled Archive (the archive is compiled using darwin ports - so you SHOULD have installed the latest version of darwin ports): [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-64380.tgz Eiffel57_gpl_macosx-intel-64380.tgz]<br />
<br />
==Compiling Eiffel Studio using the Porter Package==<br />
Since the binaries above are often out of date, you might want to build the latest release yourself.<br />
# Make sure that you have all requirements that are listed in the readme section and that you have set the ISE_PLATFORM environment variable to macosx-ppc or macosx-x86 depending on your platform.<br />
# Download the latest Porter Package from [http://eiffelsoftware.origo.ethz.ch/downloads/builds/ here] (PorterPackage_57_XXXXX.tar)<br />
# Extract the PorterPackage, double-clicking should work<br />
# Open a Terminal window and cd into the PorterPackage directory<br />
# Compile the Porter Package:<pre>./compile_exes $ISE_PLATFORM</pre> This will compile the complete EiffelStudio Package. This takes 1-2 hours depending on your machine.<br />
# '''IMPORTANT''' : The installation now resides in PorterPackage/Eiffel57. In order to make it work you have to set execution permissions on the ec executable. <pre>chmod a+x Eiffel57/studio/spec/$ISE_PLATFORM/bin/ec</pre><br />
# Now you can move the Eiffel57 directory to any place you want. Just make sure to set the ISE_EIFFEL evironment variable accordingly.<br />
# If you want the gobo tools you can compile them using this script, which will place them in the correct directory and clean up: [http://n.ethz.ch/student/roederja/download/gobo-script.sh gobo-script.sh]<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
Note: For Mac OS 10.4 users, X11 is on the install Disk 1 (in System/Installation/Packages/X11User.pkg)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* MacPorts (http://www.macports.org) previously known as [http://darwinports.opendarwin.org/ Darwin Ports]<br />
* GTK2 from MacPorts: Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.7z or the tgz file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$ISE_EIFFEL # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your macports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=5297EiffelOnMac2006-10-20T09:17:05Z<p>Moriol: /* Readme */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently three separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (19.10.2006 - Revision 64380) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_64380-macosx-ppc.tar.7z Eiffel57_gpl_64380-macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from macports and use this command: <pre>7za x -so Eiffel57_gpl_64380-macosx-ppc.tar.7z | tar xfv - </pre> Or get the [http://sixtyfive.xmghosting.com/ 7zX] tool to unpack the 7z file.<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
* '''MacOS X - Intel''' (20.10.2006 - Revision 64380) : <br />
** Compiled Archive: [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-64380.tgz Eiffel57_gpl_macosx-intel-64380.tgz]<br />
<br />
==Compiling Eiffel Studio using the Porter Package==<br />
Since the binaries above are often out of date, you might want to build the latest release yourself.<br />
# Make sure that you have all requirements that are listed in the readme section and that you have set the ISE_PLATFORM environment variable to macosx-ppc or macosx-x86 depending on your platform.<br />
# Download the latest Porter Package from [http://eiffelsoftware.origo.ethz.ch/downloads/builds/ here] (PorterPackage_57_XXXXX.tar)<br />
# Extract the PorterPackage, double-clicking should work<br />
# Open a Terminal window and cd into the PorterPackage directory<br />
# Compile the Porter Package:<pre>./compile_exes $ISE_PLATFORM</pre> This will compile the complete EiffelStudio Package. This takes 1-2 hours depending on your machine.<br />
# '''IMPORTANT''' : The installation now resides in PorterPackage/Eiffel57. In order to make it work you have to set execution permissions on the ec executable. <pre>chmod a+x Eiffel57/studio/spec/$ISE_PLATFORM/bin/ec</pre><br />
# Now you can move the Eiffel57 directory to any place you want. Just make sure to set the ISE_EIFFEL evironment variable accordingly.<br />
# If you want the gobo tools you can compile them using this script, which will place them in the correct directory and clean up: [http://n.ethz.ch/student/roederja/download/gobo-script.sh gobo-script.sh]<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
Note: for Intel Macs, X11 is on the install Disk 1 (in System/Installation/Packages/X11User.pkg)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* MacPorts (http://www.macports.org) or Darwin Ports (http://darwinports.opendarwin.org/)<br />
* GTK2 from MacPorts: Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.7z or the tgz file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your macports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=5296EiffelOnMac2006-10-20T09:16:35Z<p>Moriol: /* Installation */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently three separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (19.10.2006 - Revision 64380) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_64380-macosx-ppc.tar.7z Eiffel57_gpl_64380-macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from macports and use this command: <pre>7za x -so Eiffel57_gpl_64380-macosx-ppc.tar.7z | tar xfv - </pre> Or get the [http://sixtyfive.xmghosting.com/ 7zX] tool to unpack the 7z file.<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
* '''MacOS X - Intel''' (20.10.2006 - Revision 64380) : <br />
** Compiled Archive: [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-64380.tgz Eiffel57_gpl_macosx-intel-64380.tgz]<br />
<br />
==Compiling Eiffel Studio using the Porter Package==<br />
Since the binaries above are often out of date, you might want to build the latest release yourself.<br />
# Make sure that you have all requirements that are listed in the readme section and that you have set the ISE_PLATFORM environment variable to macosx-ppc or macosx-x86 depending on your platform.<br />
# Download the latest Porter Package from [http://eiffelsoftware.origo.ethz.ch/downloads/builds/ here] (PorterPackage_57_XXXXX.tar)<br />
# Extract the PorterPackage, double-clicking should work<br />
# Open a Terminal window and cd into the PorterPackage directory<br />
# Compile the Porter Package:<pre>./compile_exes $ISE_PLATFORM</pre> This will compile the complete EiffelStudio Package. This takes 1-2 hours depending on your machine.<br />
# '''IMPORTANT''' : The installation now resides in PorterPackage/Eiffel57. In order to make it work you have to set execution permissions on the ec executable. <pre>chmod a+x Eiffel57/studio/spec/$ISE_PLATFORM/bin/ec</pre><br />
# Now you can move the Eiffel57 directory to any place you want. Just make sure to set the ISE_EIFFEL evironment variable accordingly.<br />
# If you want the gobo tools you can compile them using this script, which will place them in the correct directory and clean up: [http://n.ethz.ch/student/roederja/download/gobo-script.sh gobo-script.sh]<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
Note: for Intel Macs, X11 is on the install Disk 1 (in System/Installation/Packages/X11User.pkg)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* MacPorts (http://www.macports.org) or Darwin Ports (http://darwinports.opendarwin.org/)<br />
* GTK2 from MacPorts: Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.7z or the tgz file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your macports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=5295EiffelOnMac2006-10-20T09:14:50Z<p>Moriol: /* Requirements */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently three separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (19.10.2006 - Revision 64380) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_64380-macosx-ppc.tar.7z Eiffel57_gpl_64380-macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from macports and use this command: <pre>7za x -so Eiffel57_gpl_64380-macosx-ppc.tar.7z | tar xfv - </pre> Or get the [http://sixtyfive.xmghosting.com/ 7zX] tool to unpack the 7z file.<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
* '''MacOS X - Intel''' (20.10.2006 - Revision 64380) : <br />
** Compiled Archive: [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-64380.tgz Eiffel57_gpl_macosx-intel-64380.tgz]<br />
<br />
==Compiling Eiffel Studio using the Porter Package==<br />
Since the binaries above are often out of date, you might want to build the latest release yourself.<br />
# Make sure that you have all requirements that are listed in the readme section and that you have set the ISE_PLATFORM environment variable to macosx-ppc or macosx-x86 depending on your platform.<br />
# Download the latest Porter Package from [http://eiffelsoftware.origo.ethz.ch/downloads/builds/ here] (PorterPackage_57_XXXXX.tar)<br />
# Extract the PorterPackage, double-clicking should work<br />
# Open a Terminal window and cd into the PorterPackage directory<br />
# Compile the Porter Package:<pre>./compile_exes $ISE_PLATFORM</pre> This will compile the complete EiffelStudio Package. This takes 1-2 hours depending on your machine.<br />
# '''IMPORTANT''' : The installation now resides in PorterPackage/Eiffel57. In order to make it work you have to set execution permissions on the ec executable. <pre>chmod a+x Eiffel57/studio/spec/$ISE_PLATFORM/bin/ec</pre><br />
# Now you can move the Eiffel57 directory to any place you want. Just make sure to set the ISE_EIFFEL evironment variable accordingly.<br />
# If you want the gobo tools you can compile them using this script, which will place them in the correct directory and clean up: [http://n.ethz.ch/student/roederja/download/gobo-script.sh gobo-script.sh]<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
Note: for Intel Macs, X11 is on the install Disk 1 (in System/Installation/Packages/X11User.pkg)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* MacPorts (http://www.macports.org) or Darwin Ports (http://darwinports.opendarwin.org/)<br />
* GTK2 from MacPorts: Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.7z file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your macports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=5294EiffelOnMac2006-10-20T09:08:39Z<p>Moriol: /* Readme */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently three separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (19.10.2006 - Revision 64380) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_64380-macosx-ppc.tar.7z Eiffel57_gpl_64380-macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from macports and use this command: <pre>7za x -so Eiffel57_gpl_64380-macosx-ppc.tar.7z | tar xfv - </pre> Or get the [http://sixtyfive.xmghosting.com/ 7zX] tool to unpack the 7z file.<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
* '''MacOS X - Intel''' (20.10.2006 - Revision 64380) : <br />
** Compiled Archive: [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-64380.tgz Eiffel57_gpl_macosx-intel-64380.tgz]<br />
<br />
==Compiling Eiffel Studio using the Porter Package==<br />
Since the binaries above are often out of date, you might want to build the latest release yourself.<br />
# Make sure that you have all requirements that are listed in the readme section and that you have set the ISE_PLATFORM environment variable to macosx-ppc or macosx-x86 depending on your platform.<br />
# Download the latest Porter Package from [http://eiffelsoftware.origo.ethz.ch/downloads/builds/ here] (PorterPackage_57_XXXXX.tar)<br />
# Extract the PorterPackage, double-clicking should work<br />
# Open a Terminal window and cd into the PorterPackage directory<br />
# Compile the Porter Package:<pre>./compile_exes $ISE_PLATFORM</pre> This will compile the complete EiffelStudio Package. This takes 1-2 hours depending on your machine.<br />
# '''IMPORTANT''' : The installation now resides in PorterPackage/Eiffel57. In order to make it work you have to set execution permissions on the ec executable. <pre>chmod a+x Eiffel57/studio/spec/$ISE_PLATFORM/bin/ec</pre><br />
# Now you can move the Eiffel57 directory to any place you want. Just make sure to set the ISE_EIFFEL evironment variable accordingly.<br />
# If you want the gobo tools you can compile them using this script, which will place them in the correct directory and clean up: [http://n.ethz.ch/student/roederja/download/gobo-script.sh gobo-script.sh]<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* MacPorts (http://www.macports.org)<br />
* GTK2 from MacPorts: Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.7z file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your macports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=5293EiffelOnMac2006-10-20T09:06:32Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently three separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (19.10.2006 - Revision 64380) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_64380-macosx-ppc.tar.7z Eiffel57_gpl_64380-macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from macports and use this command: <pre>7za x -so Eiffel57_gpl_64380-macosx-ppc.tar.7z | tar xfv - </pre> Or get the [http://sixtyfive.xmghosting.com/ 7zX] tool to unpack the 7z file.<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
* '''MacOS X - Intel''' (20.10.2006 - Revision 64380) : <br />
** Compiled Archive: [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-64380.tgz Eiffel57_gpl_macosx-intel-64380.tgz]<br />
<br />
==Compiling Eiffel Studio using the Porter Package==<br />
Since the binaries above are often out of date, you might want to build the latest release yourself.<br />
# Make sure that you have all requirements that are listed in the readme section and that you have set the ISE_PLATFORM environment variable to macosx-ppc or macosx-x86 depending on your platform.<br />
# Download the latest Porter Package from [http://eiffelsoftware.origo.ethz.ch/downloads/builds/ here] (PorterPackage_57_XXXXX.tar)<br />
# Extract the PorterPackage, double-clicking should work<br />
# Open a Terminal window and cd into the PorterPackage directory<br />
# Compile the Porter Package:<pre>./compile_exes $ISE_PLATFORM</pre> This will compile the complete EiffelStudio Package. This takes 1-2 hours depending on your machine.<br />
# '''IMPORTANT''' : The installation now resides in PorterPackage/Eiffel57. In order to make it work you have to set execution permissions on the ec executable. <pre>chmod a+x Eiffel57/studio/spec/$ISE_PLATFORM/bin/ec</pre><br />
# Now you can move the Eiffel57 directory to any place you want. Just make sure to set the ISE_EIFFEL evironment variable accordingly.<br />
# If you want the gobo tools you can compile them using this script, which will place them in the correct directory and clean up: [http://n.ethz.ch/student/roederja/download/gobo-script.sh gobo-script.sh]<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
It is not yet tested if the behavior of the generated code is not correct.<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* MacPorts (http://www.macports.org)<br />
* GTK2 from MacPorts: Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.7z file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your macports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=5292EiffelOnMac2006-10-20T09:06:01Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently three separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (19.10.2006 - Revision 64380) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_64380-macosx-ppc.tar.7z Eiffel57_gpl_64380-macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from macports and use this command: <pre>7za x -so Eiffel57_gpl_64380-macosx-ppc.tar.7z | tar xfv - </pre> Or get the [http://sixtyfive.xmghosting.com/ 7zX] tool to unpack the 7z file.<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
* '''MacOS X - Intel''' (20.10.2006 - Revision 64380) : <br />
** Compile Archive: [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-64380.tgz Eiffel57_gpl_macosx-intel-64380.tgz]<br />
<br />
==Compiling Eiffel Studio using the Porter Package==<br />
Since the binaries above are often out of date, you might want to build the latest release yourself.<br />
# Make sure that you have all requirements that are listed in the readme section and that you have set the ISE_PLATFORM environment variable to macosx-ppc or macosx-x86 depending on your platform.<br />
# Download the latest Porter Package from [http://eiffelsoftware.origo.ethz.ch/downloads/builds/ here] (PorterPackage_57_XXXXX.tar)<br />
# Extract the PorterPackage, double-clicking should work<br />
# Open a Terminal window and cd into the PorterPackage directory<br />
# Compile the Porter Package:<pre>./compile_exes $ISE_PLATFORM</pre> This will compile the complete EiffelStudio Package. This takes 1-2 hours depending on your machine.<br />
# '''IMPORTANT''' : The installation now resides in PorterPackage/Eiffel57. In order to make it work you have to set execution permissions on the ec executable. <pre>chmod a+x Eiffel57/studio/spec/$ISE_PLATFORM/bin/ec</pre><br />
# Now you can move the Eiffel57 directory to any place you want. Just make sure to set the ISE_EIFFEL evironment variable accordingly.<br />
# If you want the gobo tools you can compile them using this script, which will place them in the correct directory and clean up: [http://n.ethz.ch/student/roederja/download/gobo-script.sh gobo-script.sh]<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
It is not yet tested if the behavior of the generated code is not correct.<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* MacPorts (http://www.macports.org)<br />
* GTK2 from MacPorts: Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.7z file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your macports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=5291EiffelOnMac2006-10-20T09:04:57Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently two separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (19.10.2006 - Revision 64380) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_64380-macosx-ppc.tar.7z Eiffel57_gpl_64380-macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from macports and use this command: <pre>7za x -so Eiffel57_gpl_64380-macosx-ppc.tar.7z | tar xfv - </pre> Or get the [http://sixtyfive.xmghosting.com/ 7zX] tool to unpack the 7z file.<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
* '''MacOS X - Intel''' (20.10.2006 - Revision 64380) : [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_macosx-intel-64380.tgz]<br />
<br />
==Compiling Eiffel Studio using the Porter Package==<br />
Since the binaries above are often out of date, you might want to build the latest release yourself.<br />
# Make sure that you have all requirements that are listed in the readme section and that you have set the ISE_PLATFORM environment variable to macosx-ppc or macosx-x86 depending on your platform.<br />
# Download the latest Porter Package from [http://eiffelsoftware.origo.ethz.ch/downloads/builds/ here] (PorterPackage_57_XXXXX.tar)<br />
# Extract the PorterPackage, double-clicking should work<br />
# Open a Terminal window and cd into the PorterPackage directory<br />
# Compile the Porter Package:<pre>./compile_exes $ISE_PLATFORM</pre> This will compile the complete EiffelStudio Package. This takes 1-2 hours depending on your machine.<br />
# '''IMPORTANT''' : The installation now resides in PorterPackage/Eiffel57. In order to make it work you have to set execution permissions on the ec executable. <pre>chmod a+x Eiffel57/studio/spec/$ISE_PLATFORM/bin/ec</pre><br />
# Now you can move the Eiffel57 directory to any place you want. Just make sure to set the ISE_EIFFEL evironment variable accordingly.<br />
# If you want the gobo tools you can compile them using this script, which will place them in the correct directory and clean up: [http://n.ethz.ch/student/roederja/download/gobo-script.sh gobo-script.sh]<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
It is not yet tested if the behavior of the generated code is not correct.<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* MacPorts (http://www.macports.org)<br />
* GTK2 from MacPorts: Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.7z file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your macports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=5290EiffelOnMac2006-10-20T09:03:57Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently two separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (19.10.2006 - Revision 64380) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_64380-macosx-ppc.tar.7z Eiffel57_gpl_64380-macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from macports and use this command: <pre>7za x -so Eiffel57_gpl_64380-macosx-ppc.tar.7z | tar xfv - </pre> Or get the [http://sixtyfive.xmghosting.com/ 7zX] tool to unpack the 7z file.<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
* '''MacOS X - Intel''' (20.10.2006 - Revision 64380) : [http://se.inf.ethz.ch/~moriol/www/EiffelStudioMacOSXIntel/Eiffel57_gpl_64380.tgz]<br />
<br />
==Compiling Eiffel Studio using the Porter Package==<br />
Since the binaries above are often out of date, you might want to build the latest release yourself.<br />
# Make sure that you have all requirements that are listed in the readme section and that you have set the ISE_PLATFORM environment variable to macosx-ppc or macosx-x86 depending on your platform.<br />
# Download the latest Porter Package from [http://eiffelsoftware.origo.ethz.ch/downloads/builds/ here] (PorterPackage_57_XXXXX.tar)<br />
# Extract the PorterPackage, double-clicking should work<br />
# Open a Terminal window and cd into the PorterPackage directory<br />
# Compile the Porter Package:<pre>./compile_exes $ISE_PLATFORM</pre> This will compile the complete EiffelStudio Package. This takes 1-2 hours depending on your machine.<br />
# '''IMPORTANT''' : The installation now resides in PorterPackage/Eiffel57. In order to make it work you have to set execution permissions on the ec executable. <pre>chmod a+x Eiffel57/studio/spec/$ISE_PLATFORM/bin/ec</pre><br />
# Now you can move the Eiffel57 directory to any place you want. Just make sure to set the ISE_EIFFEL evironment variable accordingly.<br />
# If you want the gobo tools you can compile them using this script, which will place them in the correct directory and clean up: [http://n.ethz.ch/student/roederja/download/gobo-script.sh gobo-script.sh]<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
It is not yet tested if the behavior of the generated code is not correct.<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* MacPorts (http://www.macports.org)<br />
* GTK2 from MacPorts: Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.7z file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your macports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Pick and Drop works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=4331EiffelOnMac2006-08-22T21:42:25Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently two separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (14.08.2006 - Revision 62488) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_62488_macosx-ppc.tar.7z Eiffel57_gpl_62488_macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from darwinports and use this command: <pre>7za x -so Eiffel57_gpl_62488.tar.7z | tar xfv - </pre> Or get [http://sixtyfive.xmghosting.com/ 7zX]<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
It is not yet tested if the behavior of the generated code is not correct.<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* DarwinPorts (http://www.darwinports.org)<br />
* GTK2 from darwinports Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.bz2 file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your darwin ports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
* Precompilation doesn't work<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Click and Pull works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=4330EiffelOnMac2006-08-22T21:42:13Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently two separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (14.08.2006 - Revision 62488) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_62488_macosx-ppc.tar.7z Eiffel57_gpl_62488_macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from darwinports and use this command: <pre>7za x -so Eiffel57_gpl_62488.tar.7z | tar xfv - </pre> Or get [http://sixtyfive.xmghosting.com/ 7zX]<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_FALLBACK_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_FALLBACK_LIBRARY_PATH=$HOME/lib:/usr/local/lib:/lib:/usr/lib:/opt/local/lib</pre><br />
<pre><br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
It is not yet tested if the behavior of the generated code is not correct.<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* DarwinPorts (http://www.darwinports.org)<br />
* GTK2 from darwinports Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.bz2 file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your darwin ports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
* Precompilation doesn't work<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Click and Pull works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=4320EiffelOnMac2006-08-22T12:21:55Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently two separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (14.08.2006 - Revision 62488) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_62488_macosx-ppc.tar.7z Eiffel57_gpl_62488_macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from darwinports and use this command: <pre>7za x -so Eiffel57_gpl_62488.tar.7z | tar xfv - </pre> Or get [http://sixtyfive.xmghosting.com/ 7zX]<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_LIBRARY_PATH=/opt/local/lib:$DYLD_LIBRARY_PATH</pre><br />
<br />
<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
It is not yet tested if the behavior of the generated code is not correct.<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* DarwinPorts (http://www.darwinports.org)<br />
* GTK2 from darwinports Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.bz2 file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your darwin ports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
* Precompilation doesn't work<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Click and Pull works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=4319EiffelOnMac2006-08-22T12:21:35Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently two separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (14.08.2006 - Revision 62488) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_62488_macosx-ppc.tar.7z Eiffel57_gpl_62488_macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from darwinports and use this command: <pre>7za x -so Eiffel57_gpl_62488.tar.7z | tar xfv - </pre> Or get [http://sixtyfive.xmghosting.com/ 7zX]<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_LIBRARY_PATH=/opt/local/lib:$DYLD_LIBRARY_PATH<br><br />
<br />
<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
It is not yet tested if the behavior of the generated code is not correct.<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* DarwinPorts (http://www.darwinports.org)<br />
* GTK2 from darwinports Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.bz2 file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your darwin ports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
* Precompilation doesn't work<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Click and Pull works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=4318EiffelOnMac2006-08-22T12:21:23Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently two separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (14.08.2006 - Revision 62488) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_62488_macosx-ppc.tar.7z Eiffel57_gpl_62488_macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from darwinports and use this command: <pre>7za x -so Eiffel57_gpl_62488.tar.7z | tar xfv - </pre> Or get [http://sixtyfive.xmghosting.com/ 7zX]<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_LIBRARY_PATH=/opt/local/lib:$DYLD_LIBRARY_PATH<br />
<br />
<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
It is not yet tested if the behavior of the generated code is not correct.<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* DarwinPorts (http://www.darwinports.org)<br />
* GTK2 from darwinports Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.bz2 file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your darwin ports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
* Precompilation doesn't work<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Click and Pull works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=4317EiffelOnMac2006-08-22T12:21:01Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently two separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (14.08.2006 - Revision 62488) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_62488_macosx-ppc.tar.7z Eiffel57_gpl_62488_macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from darwinports and use this command: <pre>7za x -so Eiffel57_gpl_62488.tar.7z | tar xfv - </pre> Or get [http://sixtyfive.xmghosting.com/ 7zX]<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_LIBRARY_PATH in your .bash_profile and .bashrc: <pre>export DYLD_LIBRARY_PATH=/opt/local/lib:$DYLD_LIBRARY_PATH<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
It is not yet tested if the behavior of the generated code is not correct.<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* DarwinPorts (http://www.darwinports.org)<br />
* GTK2 from darwinports Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.bz2 file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your darwin ports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
* Precompilation doesn't work<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Click and Pull works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=4316EiffelOnMac2006-08-22T12:20:33Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently two separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (14.08.2006 - Revision 62488) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_62488_macosx-ppc.tar.7z Eiffel57_gpl_62488_macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from darwinports and use this command: <pre>7za x -so Eiffel57_gpl_62488.tar.7z | tar xfv - </pre> Or get [http://sixtyfive.xmghosting.com/ 7zX]<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br />
**Note that you have to manually add /opt/local/lib to your DYLD_LIBRARY_PATH in your .bash_profile and .bashrc:<br />
<br />
export DYLD_LIBRARY_PATH=/opt/local/lib:$DYLD_LIBRARY_PATH<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
It is not yet tested if the behavior of the generated code is not correct.<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* DarwinPorts (http://www.darwinports.org)<br />
* GTK2 from darwinports Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.bz2 file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your darwin ports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
* Precompilation doesn't work<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Click and Pull works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=4315EiffelOnMac2006-08-22T12:20:13Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently two separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (14.08.2006 - Revision 62488) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_62488_macosx-ppc.tar.7z Eiffel57_gpl_62488_macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from darwinports and use this command: <pre>7za x -so Eiffel57_gpl_62488.tar.7z | tar xfv - </pre> Or get [http://sixtyfive.xmghosting.com/ 7zX]<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br><br />
<br />
**Note that you have to manually add /opt/local/lib to your DYLD_LIBRARY_PATH in your .bash_profile and .bashrc:<br />
<br />
export DYLD_LIBRARY_PATH=/opt/local/lib:$DYLD_LIBRARY_PATH<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
It is not yet tested if the behavior of the generated code is not correct.<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* DarwinPorts (http://www.darwinports.org)<br />
* GTK2 from darwinports Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.bz2 file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your darwin ports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
* Precompilation doesn't work<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Click and Pull works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=4314EiffelOnMac2006-08-22T12:19:32Z<p>Moriol: /* Eiffel Studio binaries for Mac OS X */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently two separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
<br />
* '''MacOS X - PPC''' (14.08.2006 - Revision 62488) : [http://n.ethz.ch/student/roederja/download/Eiffel57_gpl_62488_macosx-ppc.tar.7z Eiffel57_gpl_62488_macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from darwinports and use this command: <pre>7za x -so Eiffel57_gpl_62488.tar.7z | tar xfv - </pre> Or get [http://sixtyfive.xmghosting.com/ 7zX]<br />
<br />
* '''MacOS X - Intel''' (21.08.2006 - Revision 62801) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/vision4mac/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br><br />
<br />
Note: you have to manually add /opt/local/lib to your DYLD_LIBRARY_PATH in your .bash_profile and .bashrc:<br />
<br />
export DYLD_LIBRARY_PATH=/opt/local/lib:$DYLD_LIBRARY_PATH<br />
<br />
==Readme==<br />
<br />
NOTE: Since the C code generated by Eiffel Studio might not work properly if compiled with gcc 4, you might want to switch to GCC 3 by doing a "sudo gcc_select 3.3". However I've never encountered this problem with GCC4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
It is not yet tested if the behavior of the generated code is not correct.<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X11 (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* DarwinPorts (http://www.darwinports.org)<br />
* GTK2 from darwinports Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.bz2 file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your darwin ports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
* Precompilation doesn't work<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Click and Pull works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=3917EiffelOnMac2006-07-04T12:38:42Z<p>Moriol: /* Readme */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently two separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
We should however have a universal build available Really Soon Now.<br />
<br />
* '''MacOS X - PPC''' (28.06.2006 - Revision 60489) : [http://n.ethz.ch/student/roederja/download/Eiffel57_60489_macosx-ppc.tar.7z Eiffel57_60489_macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from darwinports and use this command: <pre>7za x -so Eiffel_57_60489.tar.7z | tar xfv - </pre> Or get [http://sixtyfive.xmghosting.com/ 7zX]<br />
<br />
* '''MacOS X - Intel''' (22.06.2006 - Revision 59914) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br><br />
**Normal Unix distribution (Revision 59091) : [http://n.ethz.ch/student/roederja/download/Eiffel57_59091_macosx-x86.tar.bz2 Eiffel57_59091_macosx-x86.tar.bz2] (This is the same as the PowerPC version only for intel)<br />
<br />
==Readme==<br />
<br />
IMPORTANT: Before compiling projects with Eiffel Studio do a "sudo gcc_select 3.3".<br><br />
The C code generated by Eiffel Studio might not work properly if compiled with gcc 4.<br />
<br />
MacOS Intel: it seems that compilation fails for some people if not using gcc 4.0... <br />
It is not yet tested if the behavior of the generated code is not correct.<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X server (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* DarwinPorts (http://www.darwinports.org)<br />
* GTK2 from darwinports Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br>Alternatively you can download this installer: [http://n.ethz.ch/student/roederja/download/gtk2-2.8.17-ppc.mpkg.tar.bz2 GTK 2.8.17 (PPC)], [http://n.ethz.ch/student/roederja/download/gtk2-2.8.17-x86.mpkg.tar.bz2 GTK 2.8.17 (x86)]<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.bz2 file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your darwin ports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
* Precompilation doesn't work<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Click and Pull works with Apple-key + mouse click</div>Moriolhttps://dev.eiffel.com/index.php?title=EiffelOnMac&diff=3916EiffelOnMac2006-07-04T12:37:09Z<p>Moriol: /* Readme */</p>
<hr />
<div>[[Category:EiffelStudio]]<br />
==Eiffel Studio binaries for Mac OS X==<br />
<br />
There are currently two separate distributions of Eiffel Studio for the PPC and the Intel platform.<br />
We should however have a universal build available Really Soon Now.<br />
<br />
* '''MacOS X - PPC''' (28.06.2006 - Revision 60489) : [http://n.ethz.ch/student/roederja/download/Eiffel57_60489_macosx-ppc.tar.7z Eiffel57_60489_macosx-ppc.tar.7z]<br />
** Note: This file is compressed using [http://www.7-zip.org 7-zip]. 7z compresses the Eiffel57 distribution 15 MB smaller than bzip2. To uncompress it either get the p7zip package from darwinports and use this command: <pre>7za x -so Eiffel_57_60489.tar.7z | tar xfv - </pre> Or get [http://sixtyfive.xmghosting.com/ 7zX]<br />
<br />
* '''MacOS X - Intel''' (22.06.2006 - Revision 59914) :<br />
**App Package : [http://n.ethz.ch/student/dfurrer/files/EiffelStudio57.app.zip EiffelStudio57.app.zip] <br><br />
**Normal Unix distribution (Revision 59091) : [http://n.ethz.ch/student/roederja/download/Eiffel57_59091_macosx-x86.tar.bz2 Eiffel57_59091_macosx-x86.tar.bz2] (This is the same as the PowerPC version only for intel)<br />
<br />
==Readme==<br />
<br />
IMPORTANT: Before compiling projects with Eiffel Studio do a "sudo gcc_select 3.3".<br><br />
The C code generated by Eiffel Studio might not work properly if compiled with gcc 4.<br />
<br />
MacOS Intel: Hum it seems that compilation fails if not using gcc 4.0<br />
<br />
===Requirements===<br />
* At least Mac OS 10.3 I guess<br />
* Apple's X server (http://www.apple.com/downloads/macosx/apple/x11formacosx.html)<br />
* Xcode (http://developer.apple.com/tools/)<br />
* DarwinPorts (http://www.darwinports.org)<br />
* GTK2 from darwinports Do a "sudo port install gtk2" , this will install gtk2 and all required dependencies<br>Alternatively you can download this installer: [http://n.ethz.ch/student/roederja/download/gtk2-2.8.17-ppc.mpkg.tar.bz2 GTK 2.8.17 (PPC)], [http://n.ethz.ch/student/roederja/download/gtk2-2.8.17-x86.mpkg.tar.bz2 GTK 2.8.17 (x86)]<br />
<br />
===Installation===<br />
Extract the Eiffel57 directory from the tar.bz2 file anywhere you like, and set up your environment accordingly.<br />
<br />
===Environment===<br />
Eiffel Studio needs several environment variables in order to work properly. I suggest you put them into your .bashrc and .profile file in your home directory. (on my system .bashrc is a symlink to .profile)<br />
<br />
You need to define the following variables:<br />
<br />
<pre>export ISE_PLATFORM=macosx-ppc # macosx-x86 on intel<br />
export ISE_EIFFEL=<PATH TO YOUR Eiffel57 directory e.g. /Developer/Applications/Eiffel57><br />
export EIFFEL_SRC=<PATH TO YOUR EIFFEL SVN CHECKOUT, only needed if you want to compile ES yourself><br />
export ISE_LIBRARY=$EIFFEL_SRC # If this is not defined it defaults to ISE_EIFFEL<br />
export GOBO=$ISE_EIFFEL/library/gobo # Only needed if you want to use gobo<br />
<br />
export PATH=$PATH:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin:$GOBO/bin</pre><br />
<br />
===Running Eiffel Studio===<br />
Enter "estudio" in a X-Term window. Make sure that your darwin ports installation is the '''first''' item in your PATH environment variable.<br />
<br />
===Known issues===<br />
* Precompilation doesn't work<br />
<br />
===Hints===<br />
* Use Helvetica 12 as Editor font<br />
* Click and Pull works with Apple-key + mouse click</div>Moriol