Non-Projected Co-ordinate systems support /export error

[Robert Jones]

Hi, Olly,

Yes, I was trying to build from git. A build from the source tarball and
external dependencies was successful with a couple of adjustments:

1- Don't set WX_CONFIG=$WX_CONFIG' --static' when using a local WX install
- by default wx doesn't have this enabled
2- Symlink local Cellar PROJ install to ./PROJINSTALL

A build with local dependencies fails due to the WX version downloaded
failing to build. Bumping this and patching it results in a successful
build. Rather than update buildmacosx.sh I installed the
already-patched-and-tested homebrew version with static linking enabled:

Source : https://github.com/Homebrew/homebrew-core/blob/master/
Formula/wxmac.rb
$brew install --with-static wxwidgets
$export WX_CONFIG /usr/local/Cellar/wxmac/3.0.3.1_1/bin/wx-config

1.2.32 build:
https://www.dropbox.com/s/wzd742092sn3xou/survex-macosx-1.2.32.dmg?dl=0

So, perhaps using the homebrew dependency management might make tracking
these dependency changes easier longer term.

I'll put the homebrew ruby script together and try this on a clean OSX
install to make sure I've got all the dependencies resolved. A dev build in
a homebrew package is 'nice to have' but more useful is the release build
so I'll get this working first. Given the success above I don't forsee too
many problems here.

Rob



On 1 November 2017 at 10:20, Olly Betts <olly at survex.com> wrote:

> On Wed, Nov 01, 2017 at 09:27:57AM +1100, Robert Jones wrote:
> > I've managed to produce a functional but incomplete  HEAD build on OSX
> > after installing a few additional dependencies and commenting out a few
> > items in the build that are breaking. I'm happy to write a homebrew
> script
> > and submit it to one of the GIS/science cask repositories if we can
> resolve
> > these. Perhaps you have some thoughts.
>
> Thanks for looking at this.
>
> > 1- unifont.hex - Currently manually downloading this from
> [...]
> > 2- Additional doc dependency on docbook2x - Once installed I get an XML
> [...]
> > 3-Icons
> > There are a few lines in buildmacosx.sh that pull in various icons:
> > lib/icons/*.iconset.zip
> [...]
>
> I guess you're trying to build from git?  The above should all be solved by
> building from a release tarball (which contains the processed unifont
> data, the generated documentation and the iconset files).
>
> > 4-PROJ dependencies/packaging
> > The buildmacosx.sh script pulls some projection data out of the locally
> > downloaded PROJ and copies it into the build. I am able to dynamically
> link
> > against the homebrew supplied PROJ package, so is this step necessary?
>
> This is just done to simplify things when building the disk image, and
> shouldn't be needed if there's a full proj install available.  You may
> need to disable the pj_set_finder() calls though - the thing to check is
> that EPSG and ESRI codes work - try processing "tests/cs.svx".
>
> Also, if homebrew installs files under a prefix you'll probably need to
> stop defining MACOSX_BUNDLE.
>
> > That said, it may be more appropriate to keep the static linking or at
> > least offer it as an option - I've had more changes to upstream
> > dependencies breaking builds in homebrew than I care to remember, and
> > it's not previously made pinning dependency versions easy.
>
> It probably makes sense to follow homebrew conventions here.
>
> Cheers,
>     Olly
>