Ticket #27 (closed task: fixed)

Opened 10 years ago

Last modified 9 years ago

Simplify compilation and deployment of FARSIGHT+Bio-Formats

Reported by: curtis Owned by: hinerm
Priority: minor Milestone: biweekly-2010: Dec-13 to Dec-23
Component: FARSIGHT Version:
Severity: non-issue Keywords:
Cc: Blocked By:
Blocking:

Description

To facilitate using  Bio-Formats from within  FARSIGHT, we have created a  Bio-Formats ITK ImageIO plugin, which uses  CMake for build configuration.

Unfortunately, it is a complex, time-consuming process to actually build all the tools involved in deploying Bio-Formats within FARSIGHT:

We would like to minimize the complexity of building these tools on each of the three major target platforms—Windows, Mac OS X and Linux—in both 32-bit and 64-bit modes.

CMake is a good start for cross-platform C++ compilation, but it still exposes a lot of complexity in the form of build settings and flags. We would like to create a more streamlined means of building the system on each platform. The cache folder in the  FARSIGHT source code distribution has build scripts for Mac OS X that set various CMake build flags appropriately for the system, but the scripts still need work.

Ultimately,  CTest should be used somehow to verify that builds continue to be functional (see  this page for more details).

Change History

comment:1 Changed 9 years ago by curtis

  • Owner changed from bselinsky to hiner
  • Status changed from new to assigned
  • Milestone changed from progress-report to biweekly-2010: Nov-01 to Nov-12

comment:2 Changed 9 years ago by curtis

  • Owner changed from hiner to hinerm

comment:3 Changed 9 years ago by hinerm

  • Status changed from assigned to accepted

comment:4 Changed 9 years ago by curtis

  • Status changed from accepted to closed
  • Resolution set to fixed

Rather than using CTest, we can use our Hudson system. See ticket #141.

As for the complexity of building, it is difficult to fully escape it. In the case of bf-cpp, one thing that will help will be to convert jar2lib into a Maven plugin (ticket #173). But building VXL, QT, ITK, VTK, FTK et. al will still be a pain.

Note: See TracTickets for help on using tickets.