[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cfe-dev
Subject:    [cfe-dev] [clang-dev] Any way I can add custom compile arguments when using ParsedAttrInfo as plugin
From:       Yafei Liu via cfe-dev <cfe-dev () lists ! llvm ! org>
Date:       2020-10-23 2:17:29
Message-ID: CAMUQRevWa47qpy356n4CKounXOxNAxLHc+QKNA3Y=ArH6d-vYA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


In my case, I create a plugin using ParsedAttrInfo to add custom
attributes, but It seems that ParsedAttrInfo does not have an API to handle
custom command line arguments like PluginASTAction. Currently I just create
a PluginASTAction and use extern variables to communicate
with ParsedAttrInfo, but I think it is not very nice for reviewing.

So can I add a custom command line argument like PluginASTAction except
that I only use ParsedAttrInfo in my plugin?

[Attachment #5 (text/html)]

<div dir="ltr">In my case, I create a plugin using  ParsedAttrInfo to add custom \
attributes, but It seems that ParsedAttrInfo does not have an API to handle custom \
command line arguments like  PluginASTAction. Currently I just create a  \
PluginASTAction and use extern variables to communicate with  ParsedAttrInfo, but I \
think it is not very nice for reviewing.<div><br></div><div>So can I add a custom \
command line argument like  PluginASTAction except that I only use  ParsedAttrInfo in \
my plugin?</div></div>


[Attachment #6 (text/plain)]

_______________________________________________
cfe-dev mailing list
cfe-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev


[prev in list] [next in list] [prev in thread] [next in thread]