If the target CommandOnly is not intended to call a compiler why is the clean step then a compiler used, or why does it not return an empty command array? If no, why is in the DirectCommands::GetTargetCleanCommands the call to Compiler* compiler = target ? CompilerFactory::GetCompiler(target->GetCompilerID()) not gated. ![]() If yes, then why do all compiler options are disabled? It will work if the user uses squirrel scripting in the pre build commands (i think this is the best use case.) ![]() This will not work, unless we introduce some special syntax in the pre/post build steps, or give the user the ability to give the command in a separate options field. Is it intended to make operations on files? I read the code, but i do not get any clue about it. Can not fix this unless i understand how the CommandOnly target type is intended to work.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |