Hello support team,Pre-defined build configuration cannot be built when it is added from `Manage Configuration` dialogue as following screen copies.(1) Create a project for a `Release` build configuration.(2) Add a `HardwareDebug` build configuration from `Manage Configuration` dialogue.(3) First buid error of the `HardwareDebug` build configuration.(4) Second buid error of the `HardwareDebug` build configuration.(5) Third buid error of the `HardwareDebug` build configuration.(6) On the other hand, of course, the `Release` build configuration can be built.To be continued.
The reason of the build error is somehow no toolchain is set as following screen copy. But even if toolchain is set, still build error is not solved as following screen copy.[Related issue]The following post is another case that a `Release` build configuration is added from `Manage Configuration` dialogue.プロジェクト作成後、ビルド構成のReleaseを追加したいがエラーになるcommunity-ja.renesas.com/cafe_rene/forums-groups/mcu-mpu/rl78/f/forum18/9885/release/
Hi Nomay,
Thank you for the feedback.
I wonder if you could try something quickly. I've not looked into this in detail.
I did reproduce that the copied debug configuration does not seem to have a toolchain configured.
There can be some issues as this CDT method for creating a configuration will not setup the build options like the project generation step. However no toolchain at all seems odd to me too.
I used the right click on project "Renesas C/C++ Project Settings> Change Toolchain Version" feature. I selected the installed toolchain and then pressed OK.
I then get similar build results to the Release configuration.
See if that makes things better for you too.
Best regards,
Mark.
Hello Mark,> I then get similar build results to the Release configuration.Which device do you use? RL78? RX? RA?At least, in case of RL78/G23 (R7F100GLG), setting toolchain still causes build error.But I can guess that other devices `may not` cause build error after setting toolchain.Best regards,NoMaY
I checked RL78 with CCRL.
Changing the toolchain via the Right-click project menu, "Renesas C/C++ Project Settings> Change Toolchain Version" seemed to work for me. Note, I was testing 2023-01. Note, this is just working around what is definitely non-desirable behaviour.
Rest assured I have pushed this towards the builder team for in-depth investigation.
Hello Mark,Thank you for the reply. I use 2023-01 too. Therefore, the following result means that I have to provide more files of my project at my side. I will post them as zip files later.> I checked RL78 with CCRL.> I was testing 2023-01> "Renesas C/C++ Project Settings> Change Toolchain Version" seemed to work for me.Best regards,NoMaY
Hello Mark,> I will post them as zip files later.The following zip file contains four zip files as follows.issue_TestCCRL_20230221.zip
TestCCRL_1.zip : Release build configration which is created at project generation.TestCCRL_2.zip : HardwareDebug build configration is added, but before setting toolchain.TestCCRL_3.zip : HardwareDebug build configration is added, and after setting toolchain. --> This still causes build error.TestCCRL_4.zip : HardwareDebug build configration which is created at project generation.Maybe the active build configuration has to be changed from `Release` to `HardwareDebug` for TestCCRL_{2, 3}.zip.
TestCCRL_3.zip still causes build error. The error is as follows. (And it is the third screen copy of my second post of this thread.)
Renesas Optimizing Linker W3.05.00 [02 Dec 2022] Copyright (C) 2011, 2022 Renesas Electronics CorporationW0561001:Option "auto_section_layout" is ineffective without option "device"W0561001:Option "security_id" is ineffective without option "device"W0561017:Paid license of CC-RL V1 is not found, and the evaluation period has expired. Please consider purchasing the product.W0561521:Cannot generate section ".option_byte"E0562310:Undefined external symbol "__STACK_ADDR_END" referenced in ".\generate\cstart.obj"E0562310:Undefined external symbol "__STACK_ADDR_START" referenced in ".\generate\cstart.obj"
I compare .rcpc files between TestCCRL_3.zip and TestCCRL_4.zip. The following screen copy shows the difference. You can see wrong setting such as -cpu=S1 or S3 (S1:NG, S3:OK) and many lack of setting such as -device=XXX.Left: HardwareDebug build configration by `Manage Configuration`,Right: HardwareDebug build configration by project creation.Best regards,NoMaY
Hello Mark and the builder team,I'm concerned about also CC-RX and CC-RH. Today is a case of CC-RX. Maybe tomorrow is a case of CC-RH.The following zip file contains four zip files as follows.issue_TestCCRX_20230222.zip
TestCCRX_1.zip : Release build configration which is created at project generation.TestCCRX_2.zip : HardwareDebug build configration is added, but before setting toolchain.TestCCRX_3.zip : HardwareDebug build configration is added, and after setting toolchain. --> This still causes build error.TestCCRX_4.zip : HardwareDebug build configration which is created at project generation.Maybe the active build configuration has to be changed from `Release` to `HardwareDebug` for TestCCRX_{2, 3}.zip.
TestCCRX_3.zip still causes build error. The error is as follows. (And the screen copy of the error is attached in this post.)
'Invoking: Linker''Building target:'LinkerTestCCRX.tmp= -MAKEUD=C:\Renesas\GitHubDesktop\workspaces\workspace_e2v202301\TestCCRX\HardwareDebug/TestCCRX_l.ud -noprelink -input=".\generate\dbsct.obj" -input=".\generate\hwsetup.obj" -input=".\generate\intprg.obj" -input=".\generate\resetprg.obj" -input=".\generate\sbrk.obj" -input=".\generate\vecttbl.obj" -input=".\src\TestCCRX.obj" -library=".\TestCCRX.lib" -start= -output="TestCCRX.abs" -form=absolute -nomessage -list=TestCCRX.map -nooptimize -nologorlink -subcommand="LinkerTestCCRX.tmp"E0562010:Option "start" requires parameterRenesas Optimizing Linker Abort
I compare .rcpc files between TestCCRX_3.zip and TestCCRX_4.zip. The following screen copy shows the difference. You can see several wrong settings even though all source files can be compiled.Left: HardwareDebug build configration by `Manage Configuration`, Right: HardwareDebug build configration by project creation.The screen copy of the error is the following.Best regards,NoMaY
Hi NoMaY,
Sorry for the problems. What you are explaining seems right. It would affect all the toolchains.
We are still looking into this. Thank you for the updated information.
I think it is clear that adding configurations in this manner is not setting the options in the same way as the project generator. You mention that the "Set toolchain feature" is not working for you.
Could you also test if this feature solves the problem (just workaround it I mean)?
"Renesas C/C++ Project Settings> Change Device"
I think this might kick the options to be the same. e.g. the RX v2 setting.
Thanks,Mark.
Hello Mark and the builder team,Thank you for the reply. The following precedure solves the problem.> Could you also test if this feature solves the problem (just workaround it I mean)?> "Renesas C/C++ Project Settings> Change Device"The following zip file contains one new zip file: TestCCRX_3b.zip.issue_TestCCRX_20230222_2.zip
TestCCRX_1.zip : Release build configration which is created at project generation.TestCCRX_2.zip : HardwareDebug build configration is added, but before setting toolchain.TestCCRX_3.zip : HardwareDebug build configration is added, and after setting toolchain. --> This still causes build error.TestCCRX_3b.zip : HardwareDebug build configration is added, and after setting toolchain and changing device. --> OKTestCCRX_4.zip : HardwareDebug build configration which is created at project generation.Maybe the active build configuration has to be changed from `Release` to `HardwareDebug` for TestCCRX_{2, 3, 3b}.zip.
The precedure is as following screen copies.Best regards,NoMaY
Hello Mark and the builder team,Now probably I understand correctly what you said about CC-RL 3 days ago. The following precedure solves the problem at my side too. I'm sorry for my misunderstanding.> I checked RL78 with CCRL.> Changing the toolchain via the Right-click project menu, "Renesas C/C++ Project Settings> Change Toolchain Version" seemed to work for me. The precedures are as following screen copies.CC-RL:CC-RX:Best regards,NoMaY
Hello Mark and the builder team,The following zip file contains five zip files as follows. There are two way to set toolchain. One is from Project Properties Dialogu (--> NG). The other is from Change Toolchain Version Dialogu (--> OK). I cannot compare .rcpc files because e2 studio cannot generate .rcpc file for CC-RH as of today (as of e2 studio 2023-01).issue_TestCCRH_20230224.zip
TestCCRH_1.zip : Release build configration which is created at project generation.TestCCRH_2.zip : HardwareDebug build configration is added, but before setting toolchain.TestCCRH_3.zip : HardwareDebug build configration is added, after setting toolchain from Project Properties Dialogu --> NG.TestCCRH_3c.zip : HardwareDebug build configration is added, after setting toolchain from Change Toolchain Version Dialogu --> OK.TestCCRH_4.zip : HardwareDebug build configration which is created at project generation.Maybe the active build configuration has to be changed from `Release` to `HardwareDebug` for TestCCRH_{2, 3, 3c}.zip.
The precedures of TestCCRH_3.zip and TestCCRH_3c.zip are as following screen copies.TestCCRH_3.zip (using Project Properties Dialogu) --> NGTestCCRH_3c.zip (using Change Toolchain Version Dialogu) --> OKBest regards,NoMaY