correct typo, format line breaks < 80 columns in README.OSX.txt

git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3-porting@11496 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
This commit is contained in:
Albrecht Schlosser 2016-04-01 11:11:11 +00:00
parent f1a157bdd9
commit 88ab084e9a
1 changed files with 84 additions and 80 deletions

View File

@ -1,4 +1,4 @@
README.OSX.txt - 2010-10-23 - Building FLTK under Apple OS X
README.OSX.txt - 2016-04-01 - Building FLTK under Apple OS X
------------------------------------------------------------
@ -64,8 +64,8 @@ In order to build FLTK from the command line, you need to install the Xcode
developer environment. It can be downloaded from the Apple Store for free.
After downloading and installing, you need to launch the Terminal. Terminal.app
is located in the "Utilities" folder inside the "Applications" folder. I like to
keep the Terminal in the Dock.
is located in the "Utilities" folder inside the "Applications" folder. I like
to keep the Terminal in the Dock.
2.2 Downloading and Unpacking
@ -87,8 +87,8 @@ dev directory:
tar xvfz fltk-1.3.xxxx.tar.gz
cd fltk-1.3.xxxx
If you got FLTK via subversion then you need one extra step: build the configure script.
Otherwise skip the following part marked ADVANCED:
If you got FLTK via subversion then you need one extra step: build the
configure script. Otherwise skip the following part marked ADVANCED:
ADVANCED: (only if you got FLTK via subversion)
- The preferred procedure is to build the configure script using tools
@ -111,7 +111,8 @@ ADVANCED: (only if you got FLTK via subversion)
-----------------------
Now configure your FLTK installation: stay in your FLTK source-code directory and type
Now configure your FLTK installation: stay in your FLTK source-code directory
and type
./configure
@ -192,7 +193,8 @@ recommend that you add it to the command search path.
--------------------
In order to build FLTK from within Xcode 3, you need to have the Xcode 3
developer environment on your computer. If you don't, go to: 'HOW TO BUILD FLTK USING XCODE4'
developer environment on your computer. If you don't, go to: 'HOW TO BUILD
FLTK USING XCODE4'
3.2 Downloading and Unpacking
@ -224,13 +226,13 @@ Use the "Project" pulldown menu to change "Active Build Configuration" to
3.4 Building FLTK
--------------------
Use the "Project" pulldown menu to set the "Active Target" to "Demo".
Select "Build" from the "Build" menu to create all libraries and test applications.
Use the "Project" pulldown menu to set the "Active Target" to "Demo". Select
"Build" from the "Build" menu to create all libraries and test applications.
By default, the Xcode4 project builds applications that run under Mac OS X 10.5 and above.
To build applications that run under older Mac OS versions, select "Edit Project Settings"
of the Project menu, then select the Build panel, and modify the "Mac OS X Deployment Target"
item.
By default, the Xcode4 project builds applications that run under Mac OS X 10.5
and above. To build applications that also run under older Mac OS versions,
select "Edit Project Settings" of the Project menu, then select the Build panel,
and modify the "Mac OS X Deployment Target" item.
All frameworks and apps will be located in "./ide/Xcode4/build/Release/".
@ -346,10 +348,10 @@ follow the instructions.
4.1 Prerequisites
--------------------
In order to build FLTK from within Xcode 4, 5, 6 or 7, you need to install the Xcode
developer environment via the Apple App Store that comes with Lion and up.
If you also want the command line version of gcc, you can use the
Download section in the Preferences dialog.
In order to build FLTK from within Xcode 4, 5, 6 or 7, you need to install
the Xcode developer environment via the Apple App Store that comes with
Lion and up. If you also want the command line version of gcc, you can use
the Download section in the Preferences dialog.
4.2 Downloading and Unpacking
@ -384,9 +386,9 @@ Use the "Scheme" pulldown menu to change the active target to "Demo" and
"My Mac 32-bit" or "My Mac 64-bit". Select "Build for" -> "Running"Run" from
the "Product" menu to create all libraries and test applications.
By default, the Xcode4 project builds applications that run under Mac OS X 10.5 and above.
To build applications that also run under older Mac OS versions, modify the "OS X Deployment
Target" item of the FLTK project build settings.
By default, the Xcode4 project builds applications that run under Mac OS X 10.5
and above. To build applications that also run under older Mac OS versions,
modify the "OS X Deployment Target" item of the FLTK project build settings.
All frameworks and apps will be located in a private directory. Use
"Window"->"Organizer" to find the full path.
@ -418,11 +420,12 @@ When distributing FLTK applications, the FLTK frameworks should be made part of
the application package. For development however, it is very convenient to have
the Release-mode Frameworks in a standard location.
For Xcode project template use, all FLTK frameworks should ibe built using
For Xcode project template use, all FLTK frameworks should be built using
"Build for Archiving" and then copied from
"./(Organizer->Derived Data Path)/Release/" to "/Library/Frameworks/". The FLTK header files
for all FLTK frameworks will then be at "/Library/Frameworks/fltk.framework/
Headers/". Add this path to the header search path of your projects.
"./(Organizer->Derived Data Path)/Release/" to "/Library/Frameworks/".
The FLTK header files for all FLTK frameworks will then be at
"/Library/Frameworks/fltk.framework/Headers/". Add this path to the header
search path of your projects.
sudo rm -f -r /Library/Frameworks/fltk*
sudo cp -R (Organizer->Derived Data Path)/Release/fltk*.framework /Library/Frameworks/
@ -447,11 +450,11 @@ test/editor-Info.plist which allows any file to be dropped
on the application icon.
You can edit this file in Xcode and change
Document types/Item 0/CFBundleTypeExtensions/Item 0
from the current "*" to the desired file extension. Use several items to declare
several extensions.
from the current "*" to the desired file extension. Use several items to
declare several extensions.
- Call fl_open_callback() at the beginning of your main() function that
sets what function will be called when a file is dropped on the application icon.
- Call fl_open_callback() at the beginning of your main() function that sets
what function will be called when a file is dropped on the application icon.
- In Xcode, set the "Info.plist File" build setting of your target application
to the Info.plist file you have prepared.
@ -471,3 +474,4 @@ Apr 17 2012 - matt: added Xcode4 documentation
Nov 13 2012 - Manolo: added "MAKE AN APPLICATION LAUNCHABLE BY DROPPING FILES ON ITS ICON"
Apr 28 2014 - Manolo: how to build programs that run on various Mac OS X versions
Mar 18 2015 - Manolo: removed uses of the Xcode3 project
Apr 01 2016 - AlbrechtS: corrected typo, formatted most line breaks < 80 columns