Monday, February 27, 2012

Chimera 1.8.0 Source

The Chimera 1.8.0 source is now available for downloading. Here is the link to the commit: http://forge.voodooprojects.org/p/chameleon/source/commit/1832/
    There is a standalone installer, available at tonymacx86.com/downloads. For bug reporting, feature requests, and general feedback please use the Chimera forum.

    -tonymacx86 & MacMan

    Related Posts:
    Chimera 1.8 Change Log
    Chimera 1.8 Update: OS X 10.8 Mountain Lion Support
    For discussions on this and other topics, register today at tonymacx86.com!

    4 comments:

    1. how can i compile chimera using xcode 4.3 ? i'm getting quite much compile errors, mostly pointing to not so good coding standards techniques like missing parentheses... is there a switch to turn this checks off somewhere?

      ReplyDelete
    2. I built Chimera 1.8.0 using Xcode 4.2.1 so I was unaware of this issue.

      There is a very easy fix for this. Edit Make.rules and change CC = cc to CC = gcc. That is how they fixed this in Chameleon 2.1svn, http://forge.voodooprojects.org/p/chameleon/source/commit/1830/

      ReplyDelete
    3. cool, thanks, that's what i needed. hopefully i'll make myself useful now :) if there is something i can help with, feel free to contact me at rasta rasta.fukka at gmail dottt com. for now my goal is to try to get the autoresolution patch/branch to work, hopefully i'll find some time to get into it

      ReplyDelete
    4. well, one more thing. i succesfully compiled the source, i even ported the autoresulution code to the current chimera source (at least i suppose so, because i was able to succesfuly compile and link the changed code). but i can't make the 'boot' file from the sym folder to work when i copy it to the '/' folder... even when i compile the original chimera source code, the boot file doesn't work - after the boot0 stage my computer is rebooted. the boot0 and boot1h files work, i already checked that by writing them to the MBR of the disk and to the boot sector of my Lion partition. but not my own compiled boot file. has this ever happened to you? any advice appreciated, thx

      ReplyDelete