Hi Brad,
The project structure now lists an array of artifacts per target.
Best Regards,
Tobias
On Fri, Jun 10, 2016 at 5:48 PM, Brad King wrote:
> On 06/10/2016 11:24 AM, Tobias Hunger wrote:
>>> The cmGeneratorTarget::GetFullName method will give you the name of the
On 06/13/2016 03:12 PM, Stephen Kelly wrote:
> I suggest switching gears and designing the initial protocol handshake and
> version negotiation, and come back to this buildsystem description part of
> the protocol later.
>
> Designing the how versioning the protocol works can include design and
Tobias Hunger wrote:
>> * Designing a protocol like this is hard (and not fast)
>
> We have been discussing this for about two years now.
That's a misleading thing to say.
Time since an effort or discussion started has never been a guideline for
when something is ready for CMake master.
> I
Hi Stephen,
Am 11.06.2016 15:37 schrieb "Stephen Kelly" :
>
> On 06/10/2016 11:35 PM, Tobias Hunger wrote:
> >
> > > Part of the design of the daemon is that messages that it sends can be
> > > 'spontaneous' - it watches for filesystem changes and can tell
> > clients to
> > >
Hi Stephen,
Am 10.06.2016 20:53 schrieb "Stephen Kelly" :
> > [== CMake MetaMagic ==[
> > {
> > # Reply header:
> > "cookie":"",
> > "type":"reply"
> > "inReplyTo":"project",
>
> Part of the design of the daemon is that messages that it sends can be
> 'spontaneous' - it
Tobias Hunger wrote:
> Hello everybody,
>
> I made some progress with extracting project structure from cmake via the
> daemon-mode. I am rather happy with the information and would love to get
> some feedback from other interested parties.
>
> Here is the format that is currently reported
On 06/10/2016 11:24 AM, Tobias Hunger wrote:
>> The cmGeneratorTarget::GetFullName method will give you the name of the
>> "main" file for a target. Passing `implib = true` will give the DLL
>> import library path on platforms where IsDLLPlatform returns true.
>
> I would have never found that!
On Fr, 2016-06-10 at 10:41 -0400, Brad King wrote:
> On 06/10/2016 10:28 AM, Tobias Hunger wrote:
> > Any pointers on how to get to that information? Any example code that gets
> > the
> > artifact list?
> >
> > I do not think this information is particularly worthwhile to add, but am
> > open
>
On 06/10/2016 10:28 AM, Tobias Hunger wrote:
> Any pointers on how to get to that information? Any example code that gets the
> artifact list?
>
> I do not think this information is particularly worthwhile to add, but am open
> to change this.
An "artifactDirectory" field is not appropriate
On Fr, 2016-06-10 at 10:06 -0400, Brad King wrote:
> On 06/09/2016 11:52 AM, Tobias Hunger wrote:
> > [== CMake MetaMagic ==[
>
> What is the purpose of this non-json wrapper in the content?
> Just part of the message protocol so that readers do not have
> to parse the json to know when the end
On 06/09/2016 11:52 AM, Tobias Hunger wrote:
> [== CMake MetaMagic ==[
What is the purpose of this non-json wrapper in the content?
Just part of the message protocol so that readers do not have
to parse the json to know when the end of the message is reached
(balanced with the start)?
I'd
On Thursday 09 June 2016 12:59:40 Tobias Hunger wrote:
> Hi Milian,
...
> > > "targets":
> > > [
> > > {
> > > "fullName":"test",
> > > "name":"test",
> > > "type":"GLOBAL_TARGET"
> > > },
> >
> >
> > A
Hello everybody,
Ok, so far I changed this:
* sourceGroups got renamed to fileGroups
* System include paths get reported
* GLOBAL_TARGETs are no longer listed.
So this is what it looks right now:
[== CMake MetaMagic ==[
{
# Reply header:
"cookie":"",
"type":"reply",
On Do, 2016-06-09 at 16:07 +0200, Milian Wolff wrote:
> On Donnerstag, 9. Juni 2016 13:27:26 CEST Tobias Hunger wrote:
> > On Do, 2016-06-09 at 08:43 -0400, Brad King wrote:
> > > > "includePath":
> > > > [
> > > >
On Do, 2016-06-09 at 09:47 -0400, Brad King wrote:
> On 06/09/2016 09:27 AM, Tobias Hunger wrote:
> > I am using the output of cmState::GetTargetTypeName.
>
> Okay. We could consider excluding GLOBAL_TARGET targets from the
> output. They never have source files and are nebulously defined.
OK,
On 06/09/2016 09:27 AM, Tobias Hunger wrote:
> I am using the output of cmState::GetTargetTypeName.
Okay. We could consider excluding GLOBAL_TARGET targets from the
output. They never have source files and are nebulously defined.
> How can I get the directory a library/executable will be put
On Do, 2016-06-09 at 08:43 -0400, Brad King wrote:
> On 06/09/2016 05:47 AM, Tobias Hunger wrote:
> > I made some progress with extracting project structure from cmake via the
> > daemon-mode. I am rather happy with the information and would love to get
> > some
> > feedback from other interested
Hi Milian,
great that you have found the time to look over this! It is greatly appreciated!
On Do, 2016-06-09 at 12:32 +0200, Milian Wolff wrote:
> > [== CMake MetaMagic ==[
> > {
> > # Reply header:
> > "cookie":"",
> > "type":"reply"
> > "inReplyTo":"project",
> >
> > # Data:
> >
On Donnerstag, 9. Juni 2016 09:47:44 CEST Tobias Hunger wrote:
> Hello everybody,
Hey Tobias,
> I made some progress with extracting project structure from cmake via the
> daemon-mode. I am rather happy with the information and would love to get
> some feedback from other interested parties.
19 matches
Mail list logo