Exactly.
On 23 May 2017 at 20:40, Albert Astals Cid wrote:
> El dimarts, 23 de maig de 2017, a les 2:04:54 CEST, Aleix Pol va escriure:
>> On Mon, May 22, 2017 at 7:54 PM, Shaheed Haque wrote:
>> > On 21 May 2017 at 22:27, Aleix Pol wrote:
>> >> On Sat, May 20, 2017 at 7:41 PM, Shaheed Haque
>
> I don't understand what you're trying to do.
Me neither :-). Let me take a step back to try to provide some
context. It is my assessment that part of the problem with the
maintenance of bindings has been the lack of automation both in
support of the initial development of the bindings, and then
El dimarts, 23 de maig de 2017, a les 2:04:54 CEST, Aleix Pol va escriure:
> On Mon, May 22, 2017 at 7:54 PM, Shaheed Haque wrote:
> > On 21 May 2017 at 22:27, Aleix Pol wrote:
> >> On Sat, May 20, 2017 at 7:41 PM, Shaheed Haque
wrote:
> >>> Actually, there is one thing about "target CMake"-bas
On Mon, May 22, 2017 at 7:54 PM, Shaheed Haque wrote:
> On 21 May 2017 at 22:27, Aleix Pol wrote:
>> On Sat, May 20, 2017 at 7:41 PM, Shaheed Haque wrote:
>>> Actually, there is one thing about "target CMake"-based KF5 that I
>>> don't quite understand: is there a way to get to the C++ compile f
On Thu, May 18, 2017 at 7:04 PM, Shaheed Haque wrote:
> Hi,
>
> On 18 May 2017 at 12:51, Andreas Hartmetz wrote:
>> On Samstag, 13. Mai 2017 23:48:33 CEST Shaheed Haque wrote:
>>> Hi,
>>>
>>> On 13 May 2017 at 22:04, Sven Brauch wrote:
>>> > Hi,
>>> >
>>> > On 05/13/2017 06:06 PM, Shaheed Haque
On 21 May 2017 at 22:27, Aleix Pol wrote:
> On Sat, May 20, 2017 at 7:41 PM, Shaheed Haque wrote:
>> Actually, there is one thing about "target CMake"-based KF5 that I
>> don't quite understand: is there a way to get to the C++ compile flags
>> needed from CMake? That is, the modern equivalent of
On Sat, May 20, 2017 at 7:41 PM, Shaheed Haque wrote:
> Actually, there is one thing about "target CMake"-based KF5 that I
> don't quite understand: is there a way to get to the C++ compile flags
> needed from CMake? That is, the modern equivalent of Foo_COMPILE_FLAGS
> but for target Foo? Even if
Actually, there is one thing about "target CMake"-based KF5 that I
don't quite understand: is there a way to get to the C++ compile flags
needed from CMake? That is, the modern equivalent of Foo_COMPILE_FLAGS
but for target Foo? Even if the general answer is "no", I'm interested
in at least the CMa
Hi,
On 18 May 2017 at 12:51, Andreas Hartmetz wrote:
> On Samstag, 13. Mai 2017 23:48:33 CEST Shaheed Haque wrote:
>> Hi,
>>
>> On 13 May 2017 at 22:04, Sven Brauch wrote:
>> > Hi,
>> >
>> > On 05/13/2017 06:06 PM, Shaheed Haque wrote:
>> >> The printed output shows that the variable KF5KIO_INCL
On Samstag, 13. Mai 2017 23:48:33 CEST Shaheed Haque wrote:
> Hi,
>
> On 13 May 2017 at 22:04, Sven Brauch wrote:
> > Hi,
> >
> > On 05/13/2017 06:06 PM, Shaheed Haque wrote:
> >> The printed output shows that the variable KF5KIO_INCLUDE_DIRS is
> >> not
> >> set. In poking around, I see referen
Hi,
On 13 May 2017 at 22:04, Sven Brauch wrote:
> Hi,
>
> On 05/13/2017 06:06 PM, Shaheed Haque wrote:
>> The printed output shows that the variable KF5KIO_INCLUDE_DIRS is not
>> set. In poking around, I see references to a (new-to-me) target-based
>> system, and using that like this:
> The quest
Hi,
I'm a bit confused as to how the current KF5 CMake support works. I
have a small fragment that looks like this:
find_package(KF5KIO REQUIRED)
message(STATUS "KF5KIO includes = ${KF5KIO_INCLUDE_DIRS}")
The printed output shows that the variable KF5KIO_INCLUDE_DIRS is not
set. In pokin
12 matches
Mail list logo
