Hi JeDi,
If you look carefully, you will notice that, when you create a project
through a macro (e.g. myproject), CMake will create a dummy project
named "Project" and assume you're using C and C++ as default languages.
Note that I intentionally chose a non-supported language, CPP, in the
example
On Friday 11 September 2009, David Cole wrote:
> When you say "make the project name a target" what do you mean by that?
> (1) internally create a CMake target with the given name?
> (2) create a makefile target with that name that builds all the cmake
> targets in that cmake project?
I think this
On Fri, Sep 11, 2009 at 4:22 PM, Marcel Loose wrote:
> Hi David,
>
> I don't see the exact difference between (1) and (2). And yes, I was
> thinking of using the project name as a target. You are right, that it
> might cause clashes with existing projects, though :-(
>
> We use the convention that
Hi David,
I don't see the exact difference between (1) and (2). And yes, I was
thinking of using the project name as a target. You are right, that it
might cause clashes with existing projects, though :-(
We use the convention that project names are always capitalized, so we
usually don't run int
When you say "make the project name a target" what do you mean by that?
(1) internally create a CMake target with the given name?
(2) create a makefile target with that name that builds all the cmake
targets in that cmake project?
(3) something else?
(1) is probably not feasible for most folks --
Hi all,
I was wondering whether it's a good idea to make the project name (i.e.
the argument to the 'project' command) a target.
Rationale: I have a project that consists of numerous sub-projects and I
would like to be able to build some of these separately. Wrapping the
'project' command in a m
