Changes between Initial Version and Version 1 of MacOSXBuild


Ignore:
Timestamp:
May 14, 2007, 10:09:39 AM (17 years ago)
Author:
mlucas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MacOSXBuild

    v1 v1  
     1= MacOSX Build =
     2
     3 ossimPlanet is being initially developed on the OSX platform with the XCode developer tools.
     4
     5== Binary Installer ==
     6The easiest way to get up and running is to install the latest binary installer.  During initial development, a fairly recent version of the software will be available at http://ossim.telascience.org/ossimdata/MacOSX/ .   Look for and download the dmg file which will should mount after download. (e.g.  ossim_1.6.6rc20.pkg.dmg )  Double click the package installer and the libararies and frameworks will be installed in [[standard locations]]:
     7
     8==Development ==
     9
     10=== Dependencies ===
     11All dependencies necessary to build ossim and ossimplanet can now be downloaded from [http://ossim.telascience.org/ossimdata/MacOSX/ossim_dependencies.tgz here].  Download and unpack in your /Users/Shared/Development directory.
     12
     13unpack and place in /Users/Shared/Development
     14run ranlib on all of the static libraries there.
     15
     16 cd /Users/Shared/Development/ossim_dependencies/lib
     17 ranlib *.a
     18 cd ../nuiSDK/lib
     19 ranlib *.a
     20
     21=== svn checkout summary ===
     22
     23svn will now checkout a master ossim repository, functionality is divided into the subdirectories shown below:
     24
     25* ossim - base library for image and geospatial processing
     26* ossim_qt - qt3 interface (imagelinker, iview applications)
     27* libwms - provides OGC Web Mapping Services interface
     28* ossimPlanet - base library for planet visualization
     29* ossimPlanetQt - qt4 interface for ossimPlanet application
     30* ossim_plugins - dynamic plugins for ossim
     31* ossimplanetCocoa - Cocoa version of ossimplanet
     32
     33Follow the [[cvs instructions | svn instructions]] to checkout the source code trees.  We recommend you set up your source code under /Users/Shared/Development to match up with the path settings in the xcode projects.
     34
     35xcode assumes that all modules are located side by side in:
     36
     37 /Users/Shared/Development/ossim
     38
     39== Building and Running in Xcode ==
     40
     41The MacOSX build is performed with xcode.  It assumes that all of the svn subtrees have been checked out per the svn instructions and are sitting side by side in your development directory.  Navigate into the ossim subdirectory and load the xcode project
     42
     43   /Users/Shared/Development/ossim/xcode/ossim/ossim.xcodeproj
     44
     45Loading this project into xcode will reveal Targets and subtargets that will build all of the ossim related frameworks and apps.  It assumes ossim_dependencies has been downloaded and placed in /Users/Shared/Development.
     46
     47There are xcode projects in each of these directories with appropriate dependencies between the projects.  All projects now load a common_settings xcode config file where cross project settings and environmental variables are maintained.  The projects now build into a shared build directory located in /var/tmp.  We have taken steps to minimize the potential conflicts with other paths and projects and reduce start up effort with common settings.
     48
     49In the ossim.xcodeproj select the All target and build.  The All target is an aggregate target that will build all of the dependencies.  Select the ossimPlanet application as the executable and run.  Note, ossimplanetCocoa has its own xcode project.
     50
     51== Package Building==
     52
     53Here are some quick notes on building and packaging.  After building the All target, select the build_package_dir target and build.  This target creates a package directory in the xcode build directory.  Applications, tools, frameworks, support files and dependencies are then staged into the package directory. 
     54
     55Next, in the Developer/Applications/Utilities folder open up PackageMaker and open the ossim package maker file that is located in the ossim_package_support directory.  Note that the ossim_package_support directory is available as a module checkout at www.remotesensing.org:/cvs.  It contains geoids and initial reference images for the packaging.  Once you have opened the ossim packagemaker file, select build and an installer package will be generated.  Optionally, you can use a utility such as DropDMG to create a dmg disk image for distribution.  This is a universal installer for ossim applications and frameworks.
     56
     57updated 18 Apr 2007 mrl