Add the following text to the schema files: Now we will show how to map the set_static_library_cflags() statement to the Visual Studio properties GUI.You can now also rename the target (VisualGDB will automatically read and write the “target.name” property we defined):.no other target shares the same definition) and will then edit it according to the rules we specified. VisualGDB will automatically update the register_static_library() statement: This happens because VisualGDB will internally locate the “target.sources” property, confirm that it’s defined in a unique way (i.e.Try adding a new source to the static library:.Locate the StaticLibrary1 target in Solution Explorer and verify that the Matching layout rule for it is CustomStaticLibrary: Open VisualGDB Project Properties and set the Custom Target Definitions Directory to “ TargetDefinitions“:.They are defined as shortcuts to the name and sources subproperties of cl. target.name and target.sources are special statement names expected by VisualGDB.cl is defined as an instance of the register_static_library() statement (that internally exposes the name and sources properties per the custom.stmt file).In this example, it defines the register_static_library() statement that exposes 2 properties: name (1 token) and sources (0 or more tokens).įinally, custom.prop file defines one property category and 3 properties: The custom.stmt file tells VisualGDB how to interpret various statements. It specifies a priority (in case the backtrace has multiple statements matching different targets) and links to properties and statements files. the call stack when the target was registered). ![]() The custom.tgt file defines a rule that will be used for all targets that have ‘register_static_library()’ in their backtrace (i.e. Create a subdirectory called “TargetDefinitions” inside your project directory and add the following files there:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |