On 16-05-2012 15:12, William Kyngesburye wrote:
On May 16, 2012, at 9:08 AM, William Kyngesburye wrote:
On May 16, 2012, at 8:50 AM, William Kyngesburye wrote:
I didn't mentioned explicitly but I did a svn update so the code should be very
close to what's in 1.9.1rc
Anyone building the relea
On May 16, 2012, at 9:08 AM, William Kyngesburye wrote:
> On May 16, 2012, at 8:50 AM, William Kyngesburye wrote:
>
>>> I didn't mentioned explicitly but I did a svn update so the code should be
>>> very close to what's in 1.9.1rc
>>> Anyone building the release candidate on OSX with XCode 4.3.2
On May 16, 2012, at 8:50 AM, William Kyngesburye wrote:
>> I didn't mentioned explicitly but I did a svn update so the code should be
>> very close to what's in 1.9.1rc
>> Anyone building the release candidate on OSX with XCode 4.3.2 successfully?
>>
>> Joaquim
>
> 1.9.1rc compiles with no prob
On May 16, 2012, at 6:03 AM, J Luis wrote:
>
> From it's placement in the above and a vague memory of the old ecw builds, I
> suspect the carbon part comes from ECW. those separate libNCEcw* libraries
> are an old way of building ECW, the newer method builds as a single libecwj2.
> ECW is a
From it's placement in the above and a vague memory of the old ecw builds, I
suspect the carbon part comes from ECW. those separate libNCEcw* libraries are
an old way of building ECW, the newer method builds as a single libecwj2. ECW
is a PITA to compile on OSX (my notes still leave some u
On May 15, 2012, at 9:07 PM, Joaquim Luis wrote:
>> Has this worked in the past? Did you change any configuration options from
>> then? Or update any dependent libraries?
>
> Yes, it did work several times in the past. But also yes, I updated
> dependencies using homebrew. Started by netcdf,
On 16-05-2012 02:50, William Kyngesburye wrote:
forget the directory problem - nothing should be linking the Carbon framework
in the first place. Especially on OSX 10.7, since carbon 64bit does not exist,
only 32bit. But then, that's just a warning, and may have nothing to do with
the actual
forget the directory problem - nothing should be linking the Carbon framework
in the first place. Especially on OSX 10.7, since carbon 64bit does not exist,
only 32bit. But then, that's just a warning, and may have nothing to do with
the actual error.
Has this worked in the past? Did you cha
Hi,
Sorry to come again with a building problem. Now on OSX 10.7.4
For forced updating reasons I was obliged to up start a chain of up
updates that ended up on upgrading to Xcode 4.3.2 and now I get these
errors linking (well, a lot more)
/System/Library/Frameworks/Carbon.framework/Carbon
