[zeromq-dev] zproject basic question

[Arnaud Loonstra]

Yes, it did. It gave an error even. I just missed it I guess :S

On 4/4/19 2:03 PM, Luca Boccassi wrote:
> Nice!
> 
> Was there any warning from gsl about the illegal char?
> 
> On Thu, 2019-04-04 at 13:25 +0200, Arnaud Loonstra wrote:
>> Hi Luca & Kevin,
>>
>> Thanks, so I was right in thinking that zproject should update the
>> headers. I found I was using an illegal character in my api file. It
>> now
>> updates the headers indeed.
>>
>> I must say that when you get the setup right it's quite a joy to
>> build
>> with zproject and czmq together. I'm not doing C stuff a lot but
>> I've
>> never been able to build stuff this fast using C. Last hackathon got
>> me
>> started!
>>
>> Rg,
>>
>> Arnaud
>>
>> On 4/4/19 12:29 PM, Kevin Sapper wrote:
>>> Hi Arnaud,
>>>
>>> I did the same and I worked for me as well.
>>>
>>> Cheers Kevin
>>>
>>> Luca Boccassi <
>>> luca.boccassi at gmail.com
>>>   <mailto:
>>> luca.boccassi at gmail.com
>>>>>
>>> schrieb am Do., 4. Apr. 2019, 12:13:
>>>
>>>      On Thu, 2019-04-04 at 10:57 +0200, Arnaud Loonstra wrote:
>>>       > Hey all,
>>>       >
>>>       > I'm testing zproject for a new library. Simple question to
>>> clear it
>>>       > out
>>>       > for me; zproject does generate some header files, I'm just
>>> not sure
>>>       > when
>>>       > which. For example I have setup a simple project with an
>>> api.
>>>       >
>>>       > ie:
>>>       >
>>>       > <class name = "sphactor" state = "stable">
>>>       >      <constructor>
>>>       >          Constructor, creates a new Sphactor node.
>>>       >          <argument name = "name" type = "string" optional =
>>> "1" />
>>>       >          <argument name = "uuid" type = "zuuid" optional =
>>> "1" />
>>>       >      </constructor>
>>>       > etc.
>>>       >
>>>       > Zproject has parsed this and has provided me with a skeleton
>>> with a
>>>       > header include/sphactor.h. If I now update the api file
>>> with:
>>>       >
>>>       >      <method name = "endpoint">
>>>       >          Return our sphactor's endpoint, after successful
>>>       > initialization.
>>>       >          The endpoint is usually inproc://<uuid>
>>>       >          <return type = "string" />
>>>       >      </method>
>>>       >
>>>       > And rerun zproject. The include/sphactor.h is not updated. I
>>> have to
>>>       > do
>>>       > this manually. Is this correct or is there a way to let
>>> zproject
>>>       > reflect
>>>       > the changes in the api to the header?
>>>       >
>>>       > As reference, here's the project file:
>>>       >
>>> https://github.com/sphaero/libsphactor/blob/master/project.xml
>>>
>>>       >
>>>       >
>>>       > Rg,
>>>       >
>>>       > Arnaud
>>>
>>>      Hi, I just tried to download the project, generate it with gsl
>>>      project.xml, add that method to the api file and regenerate it
>>> again,
>>>      and it works as expected, the header is updated:
>>>
>>>      $ git diff include/sphactor.h
>>>      diff --git a/include/sphactor.h b/include/sphactor.h
>>>      index e1e5767..75ecef4 100644
>>>      --- a/include/sphactor.h
>>>      +++ b/include/sphactor.h
>>>      @@ -45,6 +45,10 @@ SPHACTOR_EXPORT const char *
>>>        SPHACTOR_EXPORT void
>>>            sphactor_set_name (sphactor_t *self, const char *name);
>>>
>>>      +//  Set the public name of this sphactor node overriding the
>>> default.
>>>      +SPHACTOR_EXPORT void
>>>      +    sphactor_sut_name (sphactor_t *self, const char *name);
>>>      +
>>>        //  Start node, after setting header values.
>>>        //  Returns 0 if OK, -1 if it wasn't possible to start the
>>> node.
>>>        SPHACTOR_EXPORT int
>>>
>>>      --
>>>      Kind regards,
>>>      Luca Boccassi
>>>      _______________________________________________
>>>      zeromq-dev mailing list
>>>      
>>> zeromq-dev at lists.zeromq.org
>>>   <mailto:
>>> zeromq-dev at lists.zeromq.org
>>>>
>>>      
>>> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> zeromq-dev mailing list
>>> zeromq-dev at lists.zeromq.org
>>>
>>> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>>
>>>
>>
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>>
>> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>
>>
>>
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> https://lists.zeromq.org/mailman/listinfo/zeromq-dev