[macports-ports] 01/04: qtkeychain: build out of source
mcalhoun at macports.org
Sun Dec 3 14:37:31 UTC 2017
I am not aware of any reason why cmake 1.1 PG can not be used.
It was simply used in the original commit .
The resulting builds are different, however.
For example in qtkeychain-qt4, the cmake file
QtKeychainLibraryDepends-macports.cmake is installed instead of
This seems to intentional ( vs ).
Further, the cmake 1.0 PG has a fairly recent change that I assume
should be applied to the cmake 1.1 PG as well .
What is the policy for the cmake 1.1 PG?
Use it unless there is a very good reason not to?
Sorry for the long reply to a short question, but I only know the
basics of cmake and do not fully understand the differences between
the two portgroups .
On Sun, Dec 3, 2017 at 12:41 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
> On Dec 2, 2017, at 10:13, Marcus Calhoun-Lopez wrote:
>> Marcus Calhoun-Lopez (MarcusCalhoun-Lopez) pushed a commit to branch master
>> in repository macports-ports.
>> commit e12355262540398d3ea36eb78af3b4b6876fa480
>> Author: Marcus Calhoun-Lopez <mcalhoun at macports.org>
>> 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?
More information about the macports-dev