<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><br></div><div dir="ltr">We are kinda going to need to see those errors....</div><div dir="ltr"><br><blockquote type="cite">On 29 Sep 2019, at 2:03 pm, Mark Anderson <mark@macports.org> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">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.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Sep 29, 2019 at 8:58 AM Mojca Miklavec <<a href="mailto:mojca@macports.org">mojca@macports.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sun, 29 Sep 2019 at 13:56, Mark Anderson wrote:<br>
><br>
> 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?<br>
<br>
Doesn't<br>
sudo port -v build <portname><br>
give you what you are looking for?<br>
<br>
Maybe<br>
sudo port -d build <portname><br>
but that one is usually way too noisy.<br>
<br>
Mojca<br>
</blockquote></div>
</div></blockquote></body></html>