Nowadays, compiling C/C++ for iPhone, isn’t to easy like before, there are three major problems:

- No LibGCC available on Cydia. The famous GCC Compiler has been ported to the iPhone (you can found it as GNU C Compiler on Cydia). GCC depends on LibGCC  witch is no longer available on Cydia (since iOS 2.0) so it’s impossible to install CGG.

- The C Standard Library is not completely installed on iOS.

- Apple Code Sign. Saurik (Cydia developer) has already explain that…

“Starting with the recent beta releases of the iPhoneOS, Apple has started requiring that all code on the device is signed. This is mostly to make it impossible for programs running through Apple’s AppStore to download more software and run it (so no competition for AppStore).”

Fortunately right now an compatible with iOS 5 there’s an open source project that aims to port GCC and it’s dependencies to the iPhone. The project is called iPhone-GCC-Full.

To start you’ll need to get some components:

• CSU – Go to Cydia and search and install csu.
• Link Identify Editor (aka ldid) – Go to Cydia and search and install ldid.
• LibGCC: http://code.google.com/p/iphone-gcc-full/downloads/detail?name=libgcc.deb
• GCC: http://code.google.com/p/iphone-gcc-full/downloads/detail?name=iphone-gcc.deb
• Headers/Libraries: http://code.google.com/p/iphone-gcc-full/downloads/detail?name=headers-libs.deb

After downloading those components, launch Cyberduck or your favorite SFTP software and upload the files into /private/var/root on your iPhone.

Now, connect to your iPhone via SSH using Terminal in your Mac and install the downloaded packages:

your-mac:~ you$  ssh root@your-iphone.local

root@your-iphone.local’s password: : …   // The default password is “alpine”

your-iphone:~ you$ dpkg -install libgcc.deb

your-iphone:~ you$  dpkg -install iphone-gcc.deb

your-iphone:~ you$  dpkg -install headers-libs.deb

Now you can compile your applications like you do in your computer, by issuing for e.g. “cpp -o helloworld helloworld.c”.

After compiling if you try to run your app iPhone just says “Killed” when you launch it! This is Code Sign working… In order to solve this issue it’s necessary to sign the application. There are 3 options to sign apps or make it run but, the best option is called Pseudo-Signing:

“To get around this, I wrote a tool called ldid that, among other things, can generate the SHA1 hashes that are checked by Apple’s iPhoneOS kernel” - (The other signing options are here: http://www.saurik.com/id/8)

Issue the following on your iPhone Terminal:

your-iphone:~ you$ ldid -S helloworld

Now if you try to run your app it will work!! Enjoy the freedom of having your small or huge utilities running in your pocket anytime you need them! Don’t forget to install MobileTerminal to run your Apps.

Hope this guide was helpful!

Yes… You read it, ” with no user intervention and no option for disabling it”. This is… evil and will waste your bandwidth so you should have an option to disable it.

At Google’s FAQ pages, they say that there’s an option to manage this:

How will I know when there are updates or new programs available?

Google Updater keeps track of the programs you have installed and can alert you when new versions become available. By default, updates are installed automatically. If you don’t want to be notified when updates are available, follow these steps:

From the Finder, choose Go > Applications..
Double-click the Google Updater icon.
Choose Google Updater > Preferences.
Uncheck the box labeled “Notify me when updates are installed”.
Click “Done”.

But seems like now there isn’t a “Google Updater icon” at all. So in this post, will be showing you a possible solution to disable the annoying Google Keystone…

In a first try, I thought I could completely remove the Google Software Update, but… When I did it, google products began to preset some error messages, telling me that there were some missing components and they all just stop working! Well seems like google is doing it’s job.

In a second approach, I thought a different thing. I’ve noticed that Google Keystone has an launchd an it starts with the computer.

So, the following steps, on terminal, will disable Google’s Keystone from booting with the computer and automatically check for updates!

First step, remove all the Keystone info stored in the computer:

sudo rm /Library/LaunchAgents/com.google.keystone.agent.plist
sudo rm /Library/LaunchDaemons/com.google.keystone.daemon.plist
sudo rm /Library/LaunchDaemons/com.google.keystone.daemon4.plist

Second step! Create some new info files, to ensure that Keystone will still work after this when you need it:

sudo touch /Library/LaunchAgents/com.google.keystone.agent.plist
sudo touch /Library/LaunchDaemons/com.google.keystone.daemon.plist
sudo touch /Library/LaunchDaemons/com.google.keystone.daemon4.plist

Last step, give 000 permissions to the files! With means that nobody can write on the files, including Keystone:

sudo chmod 000 /Library/LaunchAgents/com.google.keystone.agent.plist
sudo chmod 000 /Library/LaunchDaemons/com.google.keystone.daemon.plist
sudo chmod 000 /Library/LaunchDaemons/com.google.keystone.daemon4.plist

Creating inaccessible dummy files is important. Without them, the launchd entries can simply be replaced whenever Google Software run. But with these steps taken, no Google App can reinstall the Keystrone launchd entry, unless they:

• ask for your username and password (to authenticate as root)
• use different filenames
• create local launchd entries (~/Library/Launch[…])

Have fun without Google Software Update!

I almost forgot… If someday you need to update google software, just open this cmd file:

~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/CheckForUpdatesNow.command

After running it, Keystone will check and download available updates.

This update issue the following new features/bug fixes: (4.1 – localized)

• Experimental Portuguese localization
• Support for the new 2012 thomson routers

Update your STKeys now, to get the latest features.

If you don’t already have STKeys, check it out here: STKeys 4

Well, I have! Furtonalty for us, Apple’s background software in OSX is nicely developed and it’s always there to help us.

To “dump” a Keychain just issue this command on Terminal:

$ sudo security dump-keychain -d login.keychain 

This will output everything you’ve in the Keychain defined with the “-d” option.

For your default OSX Keychain issue:

$ sudo security dump-keychain -d ~/Library/Keychains/login.keychain 

Hope this little tip helps someone!

The current problem that Qt tries to compile everything using versioned GCC paths: /usr/bin/g++-4.2 and /usr/bin/gcc-4.2. In OSX Lion these files are not available.

The most easy and useful solution to the problem I found is to simply create two symlinks in /usr/bin/ from the old gcc name to the standard one.

To create the links issue the following on your Terminal:

$ sudo ln -s /usr/bin/g++ /usr/bin/g++-4.2

$ sudo ln -s /usr/bin/gcc /usr/bin/gcc-4.2

 

Now you’re almost done! At this point should be possible to compile your Apps again.

Please Remember: OSX Lion 10.7 is not a (fully) supported platform of Qt 4.7. Compiling code with the MacOS 10.7 SDK might break stuff and output errors.

You should stick to the MacOS 10.6 SDK to avoid issues. Simply add a deployment target to your QMake project (.pro file) like this:

macx: QMAKE_MAC_SDK = /Developer/SDKs/MacOSX10.6.sdk

Now you’re done! Open Qt Creator and start building your Apps again!

This update issue the following new features/bug fixes: (4.0.5 – cloudy-storm)

• Improved compatibility for some 2011 Thomson routers.

Update your STKeys now, to get the latest features.

If you don’t already have STKeys, check it out here: STKeys 4

At this new website you can read all the latest news about iKlive Networks and directly buy hosting plans, and register domains and much more online.

This is the blog the place where you can read the latest news and IT tricks and tips!