Re: [NGL-devel] OS X Updates

[Brian H. <br...@ab...>]

* Sebastien Metrot <me...@me...> [2003-06-09 19:43]:
> I think everybody is happy to count you in. As for the direct CVS access 
> we preffer generally to delay things a bit, just the time for everyone 
> to know each other and for you to get a more complete understanding of 
> the project. Don't see this as a rebutal at all but more like the normal 
> path of admition :).

Ah, thanks. Ok, some updates on progress... 

- PB project for creating an OS X framework based on Carbon is done
    
    - Using UNIX versions for Carbon implementations of a few NGL
      interfaces (nglFile, etc)... for now.
    
    - Public headers vs private, etc.
    
    - Apple recommends that frameworks be setup to be embedded in host
      apps.  This is what NGL.framework is setup to do.

- PB project template for creating "NGL Application"s is done; this
  embeds the framework and links application code to NGL framework code.

- Shell scripts to install the external libs required for building the
  NGL.framework are done (FreeType 2.1.4, libjpeg 6b, libpng 1.2.5, and
  zlib 1.1.4).

The idea of the NGL.framework would be to give end-users of NGL a PKG
that they can double click to install a developer version of the
NGL.framework and the PB NGL Application template.  I don't want them to
have to deal with installing the external libs (FreeType, etc),
including the search paths in every project, etc.  

This is doable as long as the NGL headers do not reference
implementation details.  I was kind of surprised that the nglFontBase.h
includes FreeType headers (USE_FREETYPE).  I would think that for a
public interface, it should be free of any impl details... IMHO that's
much cleaner and also allows the OS X NGL developers to not have to
install _any_ external libs (and their headers) to build NGL apps.  I
have a lot of notes on this if anyone is interested.

- Working on getting samples to build using the PB template.

    - helloworld works no problem

    - Just tried the Gears sample.  It fails because it includes the
      NGL.framework (of course) whose headers reference the FreeType
      headers, but those are NOT to be required by end-users of
      NGL.framework (at least, if I get my way).  See above.

- Documentation for the NGL.framework maintainer (me) with all the funky
  steps (-seg1addr, @executable_path/../Frameworks, etc).

- Haven't started to create a dummy makefile that delegates to pbxbuild
  to build the framework.  This would allow a autotools based
  installation.

- Haven't started on input device code nor a nice console.

Brian -+- http://brianhammond.com