After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 683257 - build: don't always rebuild .vapi file
build: don't always rebuild .vapi file
Status: RESOLVED FIXED
Product: libgd
Classification: Platform
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: libgd maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-09-03 10:36 UTC by Christophe Fergeau
Modified: 2012-09-03 15:22 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
build: don't always rebuild .vapi file (1.06 KB, patch)
2012-09-03 10:36 UTC, Christophe Fergeau 		committed Details | Review

Description Christophe Fergeau 2012-09-03 10:36:12 UTC 
vapigen not touching nor overwrite the dest file if its content hasn't
changed. This causes the rule to generate the .vapi file to always trigger
as it will always be older than the .gir file which is generated
during the build. Workaround this issue by touching the .vapi file
after generating it.
Comment 1 Christophe Fergeau 2012-09-03 10:36:14 UTC 
Created attachment 223277 [details] [review]
build: don't always rebuild .vapi file
Comment 2 Cosimo Cecchi 2012-09-03 14:52:29 UTC 
Review of attachment 223277 [details] [review]:

Feel free to push, even though I can imagine this is a problem for other applications too, so a more correct fix would need to live in vapigen itself.
Comment 3 Christophe Fergeau 2012-09-03 15:06:07 UTC 
I haven't mentioned this in the log, but Marc-André has been talking with vala people about this, so a better solution will probably happen at some point.
Comment 4 Christophe Fergeau 2012-09-03 15:22:05 UTC 
Attachment 223277 [details] pushed as 16cc32d - build: don't always rebuild .vapi file