The cmake 1.1 PG is now used by qtkeychain [1].
The cmake 1.1 PG is also now consistent with the cmake 1.0 PG [2].
[1]
https://github.com/macports/macports-ports/commit/56742c7ae2b4e773efe507da209d63aeebc4a84c
[2]
https://github.com/macports/macports-ports/commit
On Dec 3, 2017, at 08:37, Marcus Calhoun-Lopez wrote:
> I am not aware of any reason why cmake 1.1 PG can not be used.
> It was simply used in the original commit [1].
>
> The resulting builds are different, however.
> For example in qtkeychain-qt4, the cmake file
> QtKeyc
I am not aware of any reason why cmake 1.1 PG can not be used.
It was simply used in the original commit [1].
The resulting builds are different, however.
For example in qtkeychain-qt4, the cmake file
QtKeychainLibraryDepends-macports.cmake is installed instead of
QtKeychainLibraryDepends
480
>
> commit e12355262540398d3ea36eb78af3b4b6876fa480
>
> Author: Marcus Calhoun-Lopez
> AuthorDate: Sat Dec 2 09:02:41 2017 -0700
>
>
> qtkeychain: build out of source
> +cmake.out_of_source yes
Any reason not to instead switch over to the cmake 1.1 portgroup, which
defaults to building out of source?
Hey Mac-mavens,
could someone add the aforementioned software to our plethoric but not enough
collection of coddled ports? Or shall I proceed on my own?
Thanks and enjoy the weekend!
Vincent