[MINC-development] MINC with NetCDF 4.4?

[Robert D. Vincent]

Ahh, I see, I need to build completely outside of the source tree...

On Fri, Sep 11, 2015 at 12:47 PM, Vladimir S. FONOV <
vladimir.fonov at gmail.com> wrote:

> Do you build in separate directory?
>
> On 15-09-11 12:19 PM, Robert D. Vincent wrote:
>
>> I've done the merge for libminc, but I'm finding that the either my
>> brain or the CPack packaging appears to be dysfunctional. I can't get a
>> clean source tarball that doesn't include all of the build junk. Any
>> clues?
>>
>>      -bert
>>
>>
>> On Fri, Sep 11, 2015 at 1:01 AM, Andrew Janke <a.janke at gmail.com
>> <mailto:a.janke at gmail.com>> wrote:
>>
>>     minc-tools develop is fine for merge to master last I looked. The
>>     only thing I haven't checked is if all remanants of automake and
>>     autoconf have been removed.
>>
>>     there should be two archives in their respective github trees from
>>     my perspective.
>>
>>     a
>>
>>     On 11/09/2015 2:26 pm, "Robert D. Vincent"
>>     <robert.d.vincent at mcgill.ca <mailto:robert.d.vincent at mcgill.ca>>
>> wrote:
>>
>>         Hi Steve,
>>
>>         I can try to make an official tarball asap. For Debian packaging
>>         purposes, can you handle separate tarballs for libminc and
>>         minc-tools?
>>
>>              -bert
>>
>>
>>         On Thu, Sep 10, 2015 at 10:57 PM, Steve M. Robbins
>>         <steve at sumost.ca <mailto:steve at sumost.ca>> wrote:
>>
>>             On August 24, 2015 07:18:09 PM Robert D. Vincent wrote:
>>             > Hi all,
>>             >
>>             > I've fixed the issue with netCDF 4.4 and checked the fix
>> into the develop
>>             > branch.
>>             >
>>             > I agree that we should do an official release of the minc
>> libraries and
>>             > tools.
>>
>>             Andrew fixed up the minc-tools version number.  Things look
>>             pretty good to me!
>>             Should we expect a merge to master and a release anytime
>>             soon?   If not, I can
>>             take a snapshot of develop to package in Debian.  But if an
>>             official tarball is
>>             immanent: I can hold off for a bit.
>>
>>             Thanks,
>>             -Steve
>>
>>             _______________________________________________
>>             MINC-development mailing list
>>             MINC-development at bic.mni.mcgill.ca
>>             <mailto:MINC-development at bic.mni.mcgill.ca>
>>
>> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>>
>>
>>
>>         _______________________________________________
>>         MINC-development mailing list
>>         MINC-development at bic.mni.mcgill.ca
>>         <mailto:MINC-development at bic.mni.mcgill.ca>
>>         http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>>
>>
>>     _______________________________________________
>>     MINC-development mailing list
>>     MINC-development at bic.mni.mcgill.ca
>>     <mailto:MINC-development at bic.mni.mcgill.ca>
>>     http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>>
>>
>>
>>
>> _______________________________________________
>> MINC-development mailing list
>> MINC-development at bic.mni.mcgill.ca
>> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>>
>>
>
> --
> Best regards,
>
>  Vladimir S. FONOV ~ vladimir.fonov <at> gmail.com
>
> _______________________________________________
> MINC-development mailing list
> MINC-development at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.bic.mni.mcgill.ca/pipermail/minc-development/attachments/20150911/44c7e527/attachment-0001.html>