Scratch Offline Editor. Updates. The Offline Editor can update itself (with user permission). It will check for updates at startup or you can use the "Check for updates" command in the file menu. The current version is . Other Versions of Scratch. If you have an older computer, or cannot install the Scratch 2.
Newsletters Mac. Shop smart for a Mac, and master Mac OS X. Then, make the most of Mac applications, e-mail, networking, iPhone and iPad, the Internet, and more.
Scratch 1. 4. If you are a network administrator: a Scratch 2. MSI has been created and maintained by a member of the community and hosted for public download here.
Installing Code: :Blocks from source on Mac OS XThese are instructions on how to build Code: :Blocks under Apple Mac OS X. They have been tested under Mac OS X version 1. Power. PC and Intel). Mac OS X 1. 0. 5 and 1. We will be building everything from scratch using the source code, and.
Packaging can be done later, once it has reached a more stable release. Update: building for Mac. Ports can be found at the end of the document.
Install Developer Tools. If they didn't come bundled with Mac OS X, get the Xcode Tools (or Developer Tools for older Mac OS X) from http: //developer. This will install Apple versions of. Apple regularly pulls all older links in order to promote newer Mac OS X, but all the. ADC at http: //connect. You need a (free) developer registration with Apple first, in order to log in there. For Mac OS X 1. 0.
Xcode 2. 2, since earlier versions were buggy. Mac How. Check Autotools versions. Depending on your OS version, you might need to download and compile new versions of these. Check what you have, with - -version (note that GNU libtool is called "glibtool" on Mac OS X). Currently Code: :Blocks requires versions. Automake example. For Mac OS X 1. 0.
You can download "automake- 1. Since it's now known as "automake- 1. If you would rather have the new version to be called when calling "automake", let it install into /usr/local and put /usr/local/bin before /usr/bin in your PATH. Libtool example. Download libtool source. The following instructions will overwrite your current version of libtool with the one you just downloaded.
Note that this will replace the system version of glibtool, which might have some compatibility issues with building other software. FYI: Universal Binaries. If you are building for Mac OS X 1. Universal Binaries ".
The latest version of OS X, 10.9 Mavericks, is here. But before you rush to install Mavericks, you'll want to check out our in-depth guide to preparing your Mac for the new OS, downloading and installing it, creating a. Scratch 1.4 For Mac OS X Compatible with Mac OSX 10.4 or later. MacScratch1.4.dmg. Scratch 1.4 for Windows Compatible with Windows 2000, XP, Vista, 7, and 8. ScratchInstaller1.4.exe. For network deployments, use the Scratch1.4. Installation. In order to connect Scratch 2.0 with Hummingbird or Finch, you will need to install a helper application, the BirdBrain Robot Server or the Finch Connection app. Follow the instructions for your OS. These are instructions on how to build Code::Blocks under Apple Mac OS X. They have been tested under Mac OS X version 10.4 (PowerPC and Intel), and should work similarly on the newer Mac OS X 10.5 and 10.6 as well. We will be.
These are binaries that contain code for both Power. PC ("ppc" arch) and Intel ("i. The basic flags that needs to be added are.
CFLAGS += "- isysroot /Developer/SDKs/Mac. OSX1. 0. 4u. sdk - arch i.
CXXFLAGS += "- isysroot /Developer/SDKs/Mac. OSX1. 0. 4u. sdk - arch i. You only need the sysroot parameter on Power. PC Macintosh, not on a Intel Macintosh). The "- arch i. 38. Usually it's easiest to build one version for "powerpc- apple- darwin. If they do, add a - c to only compile them when cross- compiling, tools like auto_revision might fail to build.
Tiger compilers might crash from time to time, but that is only to be expected (it seems).. See Technical Note TN2. Building Universal. Binaries from "configure"- based Open Source Projects. FYI: Compilers. When building for older versions of the SDK, you want to make sure to use the same compiler. Mac OS X 1. 0. 6 has GCC 4.
Mac OS X 1. 0. 4 SDK. FYI: ANSI or UNICODEFor the moment we are using "ANSI" (- -disable- unicode, default) for Mac OS X 1. UNICODE" (- -enable- unicode, optional) for Mac OS X 1.
See http: //www. wxwidgets. FYI: 3. 2- bit or 6. Code: :Blocks currently uses wx. Mac (wx. OSX/Carbon), which is 3. So it's not possible to build for "x. When Code: :Blocks (and requirements) has been updated to use wx.
OSX/Cocoa, then a 6. Build wx. Widgets. Download the source code. Download the tarball for the wx.
Mac release. http: //wxwidgets. Apply necessary patches. Don't forget to apply any released patches! Configure and (GNU) Make. Universal Binary with wx. Widgets is. the new flag: - -enable- universal_binary (you need wx.
Widgets 2. 6. 4+). Developer/SDKs/Mac. OSX1. 0. 4u. sdk - -with- macosx- version- min=1. Install into Destination. Bundle library for Mac. To avoid having the Code: :Blocks user having to compile or install wx.
Widgets themselves. This could also be done by statically linking wx.
Widgets, but with dynamic linking we can. Widgets library between all applications using wx. Widgets (not just Code: :Blocks).
Way One: Library (dynamic). To bundle our shared library with the application, we include it in "Mac. OS" and change the path. Developer/Applications/Code. Blocks. app/Contents/Mac. OS. Way Two: Framework (bundle).
Library/Frameworks/wx. Headers - > Versions/Current/Headers. Library/Frameworks/wx. Versions/Current/wx. Library/Frameworks/wx. Versions/Current - > 2.
Library/Frameworks/wx. Versions/2. 8/Headers/wx.
Library/Frameworks/wx. Versions/2. 8/wx - > libwx_macu- 2. Library/Frameworks/wx. Versions/2. 8/libwx_macu- 2. Library/Frameworks/wx. Versions/2. 8/libwx_macu- 2. To bundle our framework with the application, we include it in "Frameworks" and change the path.
Frameworks/wx. framework/Versions/2. This way it will first look in the framework path (- F), and then in for the shared library path (- L) as usual. Install Subversion client. On Mac OS X 1. 0. Subversion (svn) program. Note: you need SVN for the Code: :Blocks revision scripts to work!
Build Code. Blocks from SVNDownload the source codehttp: //www. Apply necessary patches. For a list of all available patches, see. You might need to convert line endings from DOS to Unix first. Bootstrap with Autotools. You need to use the newer version of automake (see above), for the "bootstrap". OS X 1. 0. 5 users may have recent enough autotools so they may not need to install them).
AUTOMAKE=automake- 1. ACLOCAL=aclocal- 1.
ACLOCAL_FLAGS="- I /usr/share/aclocal" ./bootstrap. Mono Fix. If you have the Mono.
Library/Frameworks/Mono. Commands/pkg- config. Unless you have a "proper" pkg- config installation the Code: :Blocks configure will fail, so move this symbolic link aside. Note: the easiest way to build a Universal Binary for Code: :Blocks is to build once for Power. PC (- arch ppc) and once for Intel (- arch i. Note: You need to patch the location of the pre- compiled headers, or it will generate them in the same place for both arch.
Tiger Fix. There is a bug in the glibtool of Mac OS X 1. C++ libs. ld: multiple definitions of symbol ___umoddi. TEXT,__text). /usr/lib/gcc/powerpc- apple- darwin. TEXT,__text). /usr/lib/gcc/i.
To work around this, you need to edit the generated "libtool" script manually. This bug has been fixed in GNU libtool 1. GNU) Make"nice" isn't strictly needed, it just makes the compile run at a lower process priority. For the Universal Binary build. Install into Destination"sudo" asks you for an admin password, in order to get install permissions. For the Universal Binary build. DESTDIR=/tmp/ppc.
DESTDIR=/tmp/x. 86. Where "lipomerge" is a custom shell script.
Bundle application for Mac. After building codeblocks in the regular Unix way, you need to bundle it with the icons. Macintosh application. There are two ways of accomplishing this, old Mac OS- style resource or Ne. XT- style bundle. The old resources are handy while developing, while bundles are more suitable for release. Note: You need to use either of these methods, or your application will launch.
Way One: Mac OS (resource)http: //developer. Carbon/Reference/Resource_Manager/Handy while developing, as you don't need to create a whole bundle. First we install the program to the PREFIX directory of your choice. PREFIX/share/codeblocks. Note: on the Intel Macintoshes, the icon comes up as "broken". Classic). Start the application with a small prefix shell wrapper like this.
DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH: $PREFIX/lib. DYLD_LIBRARY_PATH.
PREFIX/bin/codeblocks - -prefix=$PREFIX. You don't need the "DYLD_LIBRARY_PATH" stuff.
Common PREFIX Settings. Local: PREFIX=/usr/local. System: PREFIX=/usr.
Mac. Ports: PREFIX=/opt/local. Fink: PREFIX=/sw. Way Two: Ne. XT (bundle)http: //developer. Core. Foundation/Conceptual/CFBundles/This does not involve resources, and is more relocatable. Info. plist") codeblocks. Code. Blocks"). DIR="`dirname \"$0\"`/.". DYLD_LIBRARY_PATH="$DYLD_LIBRARY_PATH: $LIB".
DYLD_LIBRARY_PATH. BIN/codeblocks" - -prefix="$DIR".
The Mac. OS program will just be a shell wrapper that calls "bin/codeblocks", like above. Traditionally the bundle would include Frameworks and Resources, but we'll just avoid those. These temporary directories are listed in italic below, they're not really used in bundles.. Setup a hierarchy like this, and copy the files from the regular build/install and the above file list to it. Code. Blocks. app. Code. Blocks. app/Contents/. Code. Blocks. app/Contents/Info.
Code. Blocks. app/Contents/Mac. OS/. Code. Blocks. Contents/Mac. OS/Code.
Blocks. Code. Blocks. Contents/Resources/. Code. Blocks. app/Contents/Resources/app. Code. Blocks. app/Contents/bin/Code.
Blocks. app/Contents/lib/Code. Blocks. app/Contents/share/codeblocks/The Code.
Blocks application can now be moved with the Finder, and started up like a regular Mac application. Info. plist and more icons - for also mapping all the files that the application can open, like source code and header files and such).
Proper Application Bundling. To avoid the shell wrapper, the binary can now be moved from "bin/codeblocks" to "Mac. OS/Code. Blocks".
Helper files are moved from "share/codeblocks" to "Resources". The dynamic libraries are moved from "lib" to "Mac. OS". mv bin/codeblocks Mac.
OS/Code. Blocks. mv lib/* Mac. OS/. mv share Resources/. To avoid having to use a DYLD_LIBRARY_PATH, we rename the shared libraries (with the install_name_tool program) from e. Mac. OS/Code. Blocks. The libraries can have their names changed using the - id parameter. Mac. OS/libcodeblocks. You also need to change all of the loadable bundles for the plugins.
Resources/plugins/*. You can check the result, what libraries/frameworks it links to, with. L Code. Blocks. Optionally you can then repeat the process, for the wx library too..
Here is a full script to do the job.. It assumes to be executed at the same directory level as the Code. Block. SVN. app directory that will receive all the stuff.. OS X SVN build. cp /usr/local/bin/codeblocks ./Code. Blocks. SVN. app/Contents/Mac. OS/Code. Blocks. cp /usr/local/bin/cb_share_config ./Code. Blocks. SVN. app/Contents/Mac.
OS. cp /usr/local/bin/cb_console_runner ./Code. Blocks. SVN. app/Contents/Mac. OS. cp /usr/local/bin/codesnippets ./Code. Blocks. SVN. app/Contents/Mac. OS. cp /usr/local/lib/libwxsmithlib.
Code. Blocks. SVN. Contents/Mac. OS. Code. Blocks. SVN. Contents/Mac. OS.
Code. Blocks. SVN. Contents/Mac. OS. Code. Blocks. SVN.