On 17 June 2015 at 22:58, Stephen Kelly wrote:
> Klaim - Joël Lamotte wrote:
>
> > Thinking about boost, if package files works well with header-only
> > libraries (which I
> > suppose it should as long as the boost define header-only targets)
> > then it would be very useful indeed.
>
> Yes, I w
Klaim - Joël Lamotte wrote:
> Thinking about boost, if package files works well with header-only
> libraries (which I
> suppose it should as long as the boost define header-only targets)
> then it would be very useful indeed.
Yes, I wrote some cmake 3.0 features specifically for the Boost use cas
On 17 June 2015 at 20:50, Stephen Kelly wrote:
> Klaim - Joël Lamotte wrote:
>
> > I didn't realize at all that the FindPackage way is supposed to be
> > obsolete now.
>
> It is not obsolete, but it is not a good approach (since CMake 2.6.0
> already) if the upstream uses cmake, because config fi
Klaim - Joël Lamotte wrote:
> I didn't realize at all that the FindPackage way is supposed to be
> obsolete now.
It is not obsolete, but it is not a good approach (since CMake 2.6.0
already) if the upstream uses cmake, because config file packages provide a
better experience for downstreams
h
On 16 June 2015 at 11:49, Johannes Zarl-Zierl
wrote:
> On Monday 15 June 2015 22:43:41 you wrote:
> > Just a last question: I assume that most find module scripts distributed
> > with cmake are
> > not using this feature at the moment, right?
>
> Sadly, no.
>
> > After reading your explaination I
On Monday 15 June 2015 22:43:41 you wrote:
> Just a last question: I assume that most find module scripts distributed
> with cmake are
> not using this feature at the moment, right?
Sadly, no.
> After reading your explaination I looked at documentation for FindBoost and
> FindGTest
> which are bo
On 15 June 2015 at 18:20, Johannes Zarl-Zierl
wrote:
> On Monday 15 June 2015 16:40:10 Klaim - Joël Lamotte wrote:
> > So far I didn't get what imported targets helps with, so I'm a bit lost
> on
> > the usefulness of "namespaces"
> > but I am sure that I am missing something.
>
> Imported target
On Monday 15 June 2015 16:40:10 Klaim - Joël Lamotte wrote:
> So far I didn't get what imported targets helps with, so I'm a bit lost on
> the usefulness of "namespaces"
> but I am sure that I am missing something.
Imported targets improve the handling of find_package stuff. In the "old days",
th
On 13 June 2015 at 22:29, Alexander Neundorf
wrote:
> On Thursday, June 11, 2015 19:18:55 Klaim - Joël Lamotte wrote:
> > On 11 June 2015 at 15:22, Johannes Zarl-Zierl <
> johannes.zarl-zi...@jku.at>
> >
> > wrote:
> > > Hi,
> > >
> > > > I tried several times now to find documentation about how
On Thursday, June 11, 2015 19:18:55 Klaim - Joël Lamotte wrote:
> On 11 June 2015 at 15:22, Johannes Zarl-Zierl
>
> wrote:
> > Hi,
> >
> > > I tried several times now to find documentation about how to define
> > > and use target names which seem to have namespaces, like Qt ones.
> > >
> > > Fo
On 11 June 2015 at 15:22, Johannes Zarl-Zierl
wrote:
> Hi,
>
> > I tried several times now to find documentation about how to define
> > and use target names which seem to have namespaces, like Qt ones.
> >
> > For example: add_executable( MyProject::some_target ... )
>
> AFAIK target namespaces
Hi,
> I tried several times now to find documentation about how to define
> and use target names which seem to have namespaces, like Qt ones.
>
> For example: add_executable( MyProject::some_target ... )
AFAIK target namespaces are intended for imported targets, not "regular"
targets:
"A NAMES
Hi,
I tried several times now to find documentation about how to define
and use target names which seem to have namespaces, like Qt ones.
For example: add_executable( MyProject::some_target ... )
I can't find any documentation or even name for this.
Is it considered a "namespace"?
In any way I f
13 matches
Mail list logo
