All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Guillaume Le Louët" <guillaume.lelouet@gmail.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] .gitignore contains .c and .h ?
Date: Mon, 04 May 2015 13:37:46 +0200	[thread overview]
Message-ID: <55475A0A.1000007@gmail.com> (raw)
In-Reply-To: <20150504130102.2b796406@thh440s>

You're right, I noticed that compiling with make was removing my 
modifications.
I ended up modifying the qapi-schema.json .

May I advise to move the generated .c and .h files into a generated/ 
folder ?

Thank you Thomas.

Le 04/05/2015 13:01, Thomas Huth a écrit :
> On Mon, 04 May 2015 09:47:11 +0200
> Guillaume Le Louët <guillaume.lelouet@gmail.com> wrote:
>
>> Hello.
>>
>> The .gitignore in the master branch contains the following lines :
>> /qapi-types.[ch]
>> /qapi-visit.[ch]
>> /qapi-event.[ch]
>>
>> Why is it so ? Are they generated automatically each time I compile the
>> project ?
>> I am modifying qapi-types.h and qapi-types.c , am I doing wrong ?
> Yes, they are created automatically and you should not edit them
> manually. Just have a look at the main Makefile:
>
> qapi-modules = $(SRC_PATH)/qapi-schema.json $(SRC_PATH)/qapi/common.json \
>                 $(SRC_PATH)/qapi/block.json $(SRC_PATH)/qapi/block-core.json \
>                 $(SRC_PATH)/qapi/event.json
>
> qapi-types.c qapi-types.h :\
> $(qapi-modules) $(SRC_PATH)/scripts/qapi-types.py $(qapi-py)
>          $(call quiet-command,$(PYTHON) $(SRC_PATH)/scripts/qapi-types.py \
>                  $(gen-out-type) -o "." -b -i $<, \
>                  "  GEN   $@")
>
> So if you want to change something in this area, you likely have to
> touch the *.json files instead.
>
>   Thomas

  reply	other threads:[~2015-05-04 11:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04  7:47 [Qemu-devel] .gitignore contains .c and .h ? Guillaume Le Louët
2015-05-04 11:01 ` Thomas Huth
2015-05-04 11:37   ` Guillaume Le Louët [this message]
2015-05-04 11:59     ` Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55475A0A.1000007@gmail.com \
    --to=guillaume.lelouet@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.