[Qgis-developer] automatic sip files generation

[Alessandro Pasotti]

On Thu, Mar 30, 2017 at 5:02 PM, Denis Rouzaud <denis.rouzaud at gmail.com>
wrote:

>
>
> Le jeu. 30 mars 2017 à 16:56, Tim Sutton <tim at kartoza.com> a écrit :
>
>> Hi
>>
>> On 30 Mar 2017, at 3:18 PM, Denis Rouzaud <denis.rouzaud at gmail.com>
>> wrote:
>>
>> Dear all,
>>
>> I'd like to raise the attention on a new workflow I just merged to
>> automatically generate SIP files using the header as source only.
>>
>> A PR is pending for the documentation, but you can read it here
>> https://github.com/3nids/QGIS-Documentation/blob/
>> 6e3a9fb6f98a2869aef27c01b7ab70eb0a4c7556/source/docs/developers_guide/
>> codingstandards.rst#sip-bindings
>> (waiting to be merged).
>>
>> For the moment, only 3 files are generated (qgsattributes, qgsfeature and
>> qgsvectorlayer). One can starts adding new files to the process by adapting
>> their header and removing them from python/auto_sip.blacklist.
>>
>>
>> This is really great! A couple of questions:
>>
>> 1) the blacklist implies that any new .h files added to the source tree
>> will automatically have sip bindings generated unless you explicitly
>> blacklist them?
>>
>
> As soon as you add the include in python/core/core.sip (or gui, analysis),
> the SIP is considered as automatically generated from header except if you
> blacklist it.
>
>
>> 2) are you thinking to maintain the sip files in Git still or remove the
>> from revision in favour of having them as build time artifacts only? I ask
>> this because I often direct people to use the sip files as a reference
>> guide for the python API if they want to dig under the hood a bit more.
>>
>
> The goal is to remove the SIP files and have them created on build time.
>
>
I surely missed something: how can you deal with annotations?


-- 
Alessandro Pasotti
w3:   www.itopen.it
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20170330/546c73f1/attachment.html>