[Qgis-user] SAGA-GIS on OS X 10.7

[William Kyngesburye]

On Apr 4, 2013, at 7:52 AM, Agustin Diez-Castillo wrote:

> Other approaches compile in 10.7. Thanks William
> >SDKs are really only needed when you compile on one system for an earlier system, like on Lion (10.7) for >Snow Leopard (10.6)
> So, maybe my first compilation should work with 10.6 and 10.8. I did check both with no stable results.

The binaries created should not work on 10.6 because you used a 10.7 SDK.  It should work on 10.8.  The compilation method should work on all systems as long as the SDK, macosx-version-min and CXX options are adjusted to match (no need to set CXX on 10.6).

> I prepared a package [1] in case anyone want to test this.
> Anyhow, if we're discussing that here is because we want to use SAGA via SEXTANTE in Qgis and there I have no success whatsoever. In my system, saga_cmd works but Qgis tells me that the SAGA installation maybe is not correct. I did put /usr/local/lib/saga on my path as well.

How did you add it to your path?  Adding it to .bash_profile will not work.  And that's the wrong path anyways, it should be /usr/local/bin.

If QGIS can't find /usr/local/bin without help (no way to do that in QGIS 1.8, unless Sextante has a configuration option for the SAGA path), one way would be to compile directly into the QGIS app.  Add to the SAGA configure command:

 --prefix=/Applications/QGIS.app/Content/MacOS

it will then install into the QGIS app bin/ folder which QGIS/Sextante should find automatically.  Though you can't move or rename QGIS now or it will break SAGA.

> There are other issues when running SAGA but I guess those belong to the SAGA list.
> Agustin
> [1] https://www.dropbox.com/s/ufzsq7h826jp4u8/SAGA21.dmg
> 
> 
> On Thu, Mar 28, 2013 at 12:35 AM, William Kyngesburye <woklist at kyngchaos.com> wrote:
> OK.  2 simple choices of solutions:
> 
> Don't use a SDK.  SDKs are really only needed when you compile on one system for an earlier system, like on Lion (10.7) for Snow Leopard (10.6), or when only the Xcode app is used (ie with an Xcode project).  With this, just remove the -isysroot up to .sdk in the configuration.
> 
> Or if you need the SDK, add "-F /Library/Frameworks" to LINK_MISC.  The documentation for the isysroot flag appears to be a little misleading.  It says that the sysroot specified is added to all search paths, but I think it really means all search paths that are within the scope of the SDK.  /Library is not.  But /usr is, so it would still catch /usr/local, so the wx libraries would be a problem...
> 

-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/

First Pogril: Why is life like sticking your head in a bucket filled with hyena offal?
Second Pogril: I don't know.  Why IS life like sticking your head in a bucket filled with hyena offal?
First Pogril: I don't know either.  Wretched, isn't it?

-HitchHiker's Guide to the Galaxy