Cmake build problem workaround

[Randolph M. Fritz]

And, on top of this, it turns out that the Labs insisted on a click-through
license, back when the code was released. I think I'm going to put this on
the back burner, and use my portfile only for my own purposes.

Maybe, eventually, I'll be able to get that license changed. But I think
I've got better things to do with my time.
-- 
Randolph M. Fritz || +1 206 659-8617 || rmfritz3 at gmail.com


On Sun, Jul 1, 2018 at 9:32 PM Randolph M. Fritz <rmfritz3 at gmail.com> wrote:

> After more study, I found the code that produced that error. So that's
> done. But there are many more problems with the CMake files when building
> in a package manager environment; many files are being installed in wrong
> places. To be continued…
>
> --
> Randolph M. Fritz || +1 206 659-8617 || rmfritz3 at gmail.com
>
> On Tue, Jun 26, 2018 at 9:44 PM, Randolph M. Fritz <rmfritz3 at gmail.com>
> wrote:
>
>> Oh, could you send your cleaned up version of the portfile back to me?
>>
>> --
>> Randolph M. Fritz || +1 206 659-8617 || rmfritz3 at gmail.com
>>
>> On Tue, Jun 26, 2018 at 9:22 PM, Randolph M. Fritz <rmfritz3 at gmail.com>
>> wrote:
>>
>>> Thank you.
>>>
>>> Sigh…the developers have left the building. Kitware was hired to do the
>>> port for NREL, which is on hard times and does not fund support. I seem to
>>> be "the developers" right now, and I don't know enough.
>>>
>>> Maybe I've now figured out enough that I can place a request for help on
>>> the cmake list and get a useful answer. :-(
>>>
>>> --
>>> Randolph M. Fritz || +1 206 659-8617 || rmfritz3 at gmail.com
>>>
>>> On Tue, Jun 26, 2018 at 8:48 PM, Ryan Schmidt <ryandesign at macports.org>
>>> wrote:
>>>
>>>> Right. I am able to reproduce the problem. I made various improvements
>>>> to the portfile for stylistic and other reasons but I haven't made any
>>>> progress on resolving the problem we're seeing. I will try to take another
>>>> look at it.
>>>>
>>>> You started working on this years ago... did you ever report the
>>>> problems to the developers? Did they have any response? It's their build
>>>> system that's broken; ultimately it's their responsibility to fix it.
>>>>
>>>> \r
>>>>
>>>>
>>>> > On Jun 26, 2018, at 22:46, Randolph M. Fritz <rmfritz3 at gmail.com>
>>>> wrote:
>>>> >
>>>> > Ryan, it's been a week, any luck with this?
>>>> >
>>>> > --
>>>> > Randolph M. Fritz || +1 206 659-8617 || rmfritz3 at gmail.com
>>>> >
>>>> > On Tue, Jun 19, 2018 at 5:04 PM, Randolph M. Fritz <
>>>> rmfritz3 at gmail.com> wrote:
>>>> > Wow, thanks.
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Randolph M. Fritz || +1 206 659-8617 || rmfritz3 at gmail.com
>>>> >
>>>> > On Tue, Jun 19, 2018 at 2:46 PM, Ryan Schmidt <
>>>> ryandesign at macports.org> wrote:
>>>> >
>>>> > On Jun 19, 2018, at 12:15, Randolph M. Fritz wrote:
>>>> >
>>>> > > Ryan Schmidt – Portfile attached.
>>>> >
>>>> > Thanks. It references the patchfile cmakelists_patches.diff; could
>>>> you attach that too? I want to try to build the port.
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20180910/f6262ec6/attachment.html>