Additional linker input relative path not working Sysprogs forums › Forums › VisualGDB › Additional linker input relative path not working This topic contains 1 reply, has 2 voices, and was last updated by support 2 months, 1 week ago. Log In Register Lost Password Viewing 2 posts - 1 through 2 (of 2 total) Author Posts May 10, 2019 at 12:43 #24956 ChangedDailyParticipant Hi, I am adding additional linker inputs to my project under the MSBuild settings->Additional Linker Inputs option. I can browse to the required file and select it: <span>$(BuildDir)\protocol\bluetooth\lib\EFR32MG12P\GCC\binapploader.o</span> but when I come to compile I get the error: <span>Error /protocol/bluetooth/lib/EFR32MG12P/GCC/binapploader.o: No such file or directory… </span> This is a standalone project and I am using VGDB 5.4R3. How to fix this please? PS – If I change to use an absolute path it is OK. I have also checked the BuildDir is correct. This topic was modified 2 months, 2 weeks ago by ChangedDaily. May 10, 2019 at 17:23 #24960 supportKeymaster Thanks for reporting this. It turns out, VisualGDB incorrectly substituted VisualGDB-level variables that are not available on the MSBuild level. Please try using the relative path (from the .vcxproj file’s directory) instead. You can also try this VisualGDB build that will not substitute unsupported variables when editing settings via VisualGDB Project Properties: VisualGDB-126.96.36.19946.msi Author Posts Log In Register Lost Password Viewing 2 posts - 1 through 2 (of 2 total) You must be logged in to reply to this topic.