CMake Question

Chris Jones jonesc at hep.phy.cam.ac.uk
Sun Sep 29 16:57:41 UTC 2019


We are kinda going to need to see those errors....

> On 29 Sep 2019, at 2:03 pm, Mark Anderson <mark at macports.org> wrote:
> 
> 
> Sorry, I mean to say, I'm writing a new port. One for osquery. And I can get it to build fine by itself, but once I start the build in a portfile, I get build errors and I'm almost certain it's some stupid configuration variable I missed from when I did ccmake.
> 
>> On Sun, Sep 29, 2019 at 8:58 AM Mojca Miklavec <mojca at macports.org> wrote:
>> On Sun, 29 Sep 2019 at 13:56, Mark Anderson wrote:
>> >
>> > So I have a CMake build that builds fine when I build it locally by hand using ccmake, but as I try to turn it into a port file using the cmake portgroup it fails. Does anyone know of a way to make ccmake spit out a command line of what it used to generate?
>> 
>> Doesn't
>>     sudo port -v build <portname>
>> give you what you are looking for?
>> 
>> Maybe
>>     sudo port -d build <portname>
>> but that one is usually way too noisy.
>> 
>> Mojca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20190929/711fae1e/attachment.html>


More information about the macports-dev mailing list