Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

RFC: Backticks

<< < (2/4) > >>

ollydbg:

--- Quote from: oBFusCATed on June 19, 2021, 01:58:56 pm ---What happens without the quotes?
Generally backticks are more useful in the compiler or linker options and not for search paths.

--- End quote ---

If I remove the backtick, then the build log becomes:


--- Code: ---g++.exe -Wall -fexceptions -g -I"echo aaa" -c D:\code\test_git_temp\test_cmdcmd\main.cpp -o obj\Debug\main.o
--- End code ---

oBFusCATed:
quotes=="
backticks==`

 ::)

ollydbg:
I can't control the quote, it was always added by our compiler gcc plugin when generating the compile command.

oBFusCATed:
Then backticks are not meant to be used there. Use them in the other places.

ollydbg:

--- Quote from: oBFusCATed on June 20, 2021, 04:48:29 pm ---Then backticks are not meant to be used there. Use them in the other places.

--- End quote ---

I put this line:


--- Code: ---`echo -lm`
--- End code ---

In the linker settings->Other linker options, and it works, here is the log:


--- Code: ---g++.exe  -o bin\Debug\test_cmdcmd.exe obj\Debug\main.o  -lm 
Output file is bin\Debug\test_cmdcmd.exe with size 60.84 KB
Process terminated with status 0 (0 minute(s), 0 second(s))
0 error(s), 0 warning(s) (0 minute(s), 0 second(s))

--- End code ---

I think the backtick should also enabled in the search path settings, because for example, we can use
something like: eranif/wx-config-msys2: wx-config tool for MSYS2 based installation of wxWidgets using the mingw64 repository, Oh, maybe, those tools can be only used in the "Other linker options" or "Other Compiler options".  So, we don't need use backtick in the search directories.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version