|
From: Jonathan M. <me...@un...> - 2007-11-09 01:36:23
|
Hi Guys,
I'm a post-doc in Marcus Pandy's lab (University of Melbourne), and
I'm interested in creating an OS X port of JointTrack. (I don't use
JointTrack directly, but others in our lab may do soon.) Initially, I
am targeting an Intel-only build for OS X 10.5 (Leopard).
The dependency situation under OS X is as follows:
- WxWidgets. Version 2.8 is actually included with OS X!
- ICE. Zero C provide OS X Intel headers and libraries.
- Boost. Can compile if necessary (haven't checked if your usage
is headers-only).
- VTK. Compiles. (Should work - used by other OS X projects
like OsiriX.)
- OpenCV. OS X instructions here: http://opencvlibrary.sourceforge.net/Mac_OS_X_OpenCV_Port
I have noticed that your code uses some Microsoft-specific functions
(such as _access() to determine whether a file exists and can be
opened). In order to get an OS X build working, I will need to swap
these out for cross-platform equivalents.
I guess at this stage, I have a few questions:
- Is anyone currently working on OS X or Linux ports? (i.e. am I
duplicating any efforts?)
- I plan to set up an XCode project to handle the build. (XCode
is the free-as-in-beer IDE that Apple provide as part of OS X.) Is
this OK?
- What is your policy on including OS X headers and libraries for
the dependencies (ICE, Boost, VTK, OpenCV) in the JointTrack SVN
repository? Quite a few other projects (e.g. Blender and OsiriX) do
this to make things easier on developers.
- Are there any major problems you can foresee with the porting
task?
Thanks,
Jonathan Merritt.
PS - I CC'd this to the project admins since I'm not sure whether
you're using your SourceForge devel list.
|