On Sat, Sep 20, 2014 at 9:52 AM, René J.V. wrote:
On Friday September 19 2014 19:42:06 Lawrence Velázquez wrote:
No ... it was easier to just remove the offending include directory ...
That's an unacceptable solution. If a user interrupts the build, that
directory might never be put back
On Saturday September 20 2014 11:20:04 Mojca Miklavec wrote:
So I uploaded a diff for my current version of the Portfile:
https://trac.macports.org/ticket/45107 . The upstream bug report is here:
https://bugs.kde.org/show_bug.cgi?id=339180
The trac ticket has a Portfile patch against the one
On Sep 18, 2014, at 7:55 PM, René J.V. Bertin rjvber...@gmail.com wrote:
Now there is another thing with this new digikam version. I comes with a
newer copy of libkgeomap. The cmake system is supposed to add the path to the
included header files to the compiler options, but apparently the
On Sep 19, 2014, at 8:18 AM, René J.V. Bertin rjvber...@gmail.com wrote:
On Friday September 19 2014 10:56:20 Lawrence Velázquez wrote:
So does the CMake build add -I arguments for the included headers or not?
Can you add them?
For me it didn't, and I honestly have no idea how to
On Friday September 19 2014 11:18:06 Bradley Giesbrecht wrote:
Have you tried configure.cppflags [1]?
configure.cppflags -I${worksrcpath}/include
or
configure.cppflags -I${worksrcpath}/include -I${prefix}/include
No ... it was easier to just remove the offending include directory ...
On Sep 19, 2014, at 2:31 PM, René J.V. Bertin rjvber...@gmail.com wrote:
On Friday September 19 2014 11:18:06 Bradley Giesbrecht wrote:
Have you tried configure.cppflags [1]?
configure.cppflags -I${worksrcpath}/include
or
configure.cppflags -I${worksrcpath}/include -I${prefix}/include
Hi Ian,
On Friday September 19 2014 09:20:10 Ian Wadham wrote:
I don't know why Ruby should be required here. AFAIK KDE apps
do not use Ruby and PO (translation) files come in via some (dynamic?)
KDE route. Could there be a spurious dependency here?
Turns out it's all about nothing. The ruby
