diff options
| author | Manolo Gouy <Manolo> | 2011-02-24 10:27:33 +0000 |
|---|---|---|
| committer | Manolo Gouy <Manolo> | 2011-02-24 10:27:33 +0000 |
| commit | 8d9f90e416b90af9a33931be0cda93d5e8c217ce (patch) | |
| tree | 98a98ffd3e840658f0b4bfe9755782bbc40a06ae /README.OSX.txt | |
| parent | d8822aa74af1c886f7ef4df58e42f52af397042d (diff) | |
Mac OS only: Added the architecture flags to the dynamic library-creating command
in configure.in. Also, applied suggestion in "Fixing configure.in for OSX universal builds"
from the fltk.development forum that architecture flags are not transmitted from
configure to the fltk-config script. This brings 2 benefits:
- A universal library can be prepared, and then used to build applications of any sort
of architectures.
- Makefiles using non-Apple compilers that don't know the -arch option can call fltk-config.
This new behavior in now made clear in file README.OSX.txt.
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@8469 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'README.OSX.txt')
| -rw-r--r-- | README.OSX.txt | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/README.OSX.txt b/README.OSX.txt index fbe6ccc81..bc7652361 100644 --- a/README.OSX.txt +++ b/README.OSX.txt @@ -91,7 +91,7 @@ Now configure your FLTK installation: ./configure ADVANCED: type "./configure --help" to get a complete list of optional -configurations parameters. These should be pretty self-explenatory. Some +configurations parameters. These should be pretty self-explanatory. Some more details can be found in README. To create Universal Binaries, start "configure" with these flags: @@ -141,8 +141,11 @@ installation path to a location within the user account by adding the FLTK provides a neat script named "fltk-config" that can provide all the flags needed to build FLTK applications using the same flags that were used to build -the library itself. Running "fltk-config" without arguments will print a list -options. The easiest call to compile an FLTK application from a single source +the library itself. Architecture flags (e.g., -arch i386) used to build the +library, though, are not provided by the fltk-config script. This allows to +build universal libraries and to produce applications of any architecture +from them. Running "fltk-config" without arguments will print a list +of options. The easiest call to compile an FLTK application from a single source file is: fltk-config --compile myProgram.cxx @@ -312,3 +315,4 @@ Oct 29 2010 - matt: removed warnings Oct 24 2010 - matt: restructured entire document and verified instructions Dec 19 2010 - Manolo: corrected typos Dec 29 2010 - Manolo: removed reference to AudioToolbox.framework that's no longer needed +Feb 24 2011 - Manolo: architecture flags are not propagated to the fltk-config script. |