EiffelVision Cocoa

Revision as of 22:19, 20 August 2009 by Dfurrer (Talk | contribs) (Solution)


This project was created with the goal of running Eiffel Studio natively on the Mac and succeeds the previous Carbon based EiffelVision implementation.

Build instructions

  1. Get the latest EiffelStudio for the Mac. If you have MacPorts installed you can do this by typing
    port install eiffelstudio65
  2. Check out the latest source code from the trunk
    svn co https://svn.origo.ethz.ch/eiffelstudio/trunk
  3. Set your EIFFEL_SRC and ISE_LIBRARY to the directory
       export EIFFEL_SRC=/directory/to/your/checkout/trunk/Src
  4. Locate EiffelStudio's config.sh file (probably /Applications/MacPorts/Eiffel65/studio/spec/macosx-x86/include/config.sh) and add the flag -ObjC to the definition of the ccflags, like this:
       ccflags='-ObjC -pipe -no-cpp-precomp -fno-common -fPIC'
  5. Compile the C-parts of the library
       cd $ISE_LIBRARY/experimental/library/objc_base/Clib
       finish_freezing -library
       cd $ISE_LIBRARY/experimental/library/cocoa/Clib
       finish_freezing -library
  6. Now open the .ecf file of your project and add the following line to your target:
       <variable name="vision_implementation" value="cocoa"/>

    alternatively you can add another target which will allow you to easily compile both, a GTK+ and a Cocoa version of your application:

       <target name="cocoa" extends="classic">
          <variable name="vision_implementation" value="cocoa"/>

    If you want to compile Eiffel Studio there is already a target called "bench_cocoa" which you can select.

  7. Use ec -experiment (or estudio -experiment) to compile



  Compiling C code in C1
  Compiling C code in E1
  Undefined symbols:
    "_bridge_void_general", referenced from:
        _bridge_void_general$non_lazy_ptr in Cobj160.o
    "_bridge_void_ptr_ptr", referenced from:
        _bridge_void_ptr_ptr$non_lazy_ptr in Cobj160.o
  ld: symbol(s) not found
  collect2: ld returned 1 exit status
  make: *** [ec] Error 1


Make sure you compiled the C-parts of the libraries (see step 5 above).


If you run into any problems or have any other feedback I'll be happy to hear from you.