User forums > Help
Compiler Toolchain Setting seems to be ignored in Version 20.03
BackInTheSandbox:
--- Quote from: oBFusCATed on April 28, 2020, 10:06:39 am ---It seems your C compiler (when used for linking) is under-linking, is this a project generated by a template?
--- End quote ---
We are using the same Control Units from the same Supplier as
--- Quote from: manuelS on April 20, 2020, 06:15:09 pm ---
--- Quote ---Why do you need a C++ linker in the first place?
--- End quote ---
I basically still use the toolchain setup that came from the supplier of the hardware and bios libraries. Never thought about changing it.
--- End quote ---
--- Quote from: oBFusCATed on April 28, 2020, 10:06:39 am ---Can you reproduce this in a minimal project?
--- End quote ---
I'm not sure, if I can setup a minimal project without supplier's libraries which would still show the issue. But I can try in my spare time.
--- Quote from: oBFusCATed on April 28, 2020, 10:06:39 am ---Is there some public documentation for this compiler/libc combination?
--- End quote ---
It seems the only publicly available information is this:
https://www.stw-technic.com/products/canbus-modules/hardware-and-software-tools/c-compiler-and-debugger/
The manual of the product with the instructions on how to set up Code::Blocks and gcc seems to be available only to customers who buy the ECU.
BackInTheSandbox:
--- Quote from: oBFusCATed on April 28, 2020, 10:06:39 am ---Can you reproduce this in a minimal project?
--- End quote ---
Attached a minimal project for GNU GCC Compiler for TriCore v3.4.6.
The "Release" build uses the C++ Linker, while the "Debug" build uses the C-Linker.
stahta01:
https://www.stw-technic.com/wp-content/uploads/2018/02/ESX-3CM-User-Manual.pdf
No idea if the above links gives useful information.
Tim S.
oBFusCATed:
BackInTheSandbox: Can you check in the docs if the use of cosf requires mentions that you have to explicitly link with libm?
BackInTheSandbox:
--- Quote from: oBFusCATed on April 28, 2020, 06:46:42 pm ---BackInTheSandbox: Can you check in the docs if the use of cosf requires mentions that you have to explicitly link with libm?
--- End quote ---
I checked and libm is not mentioned. It would have surprised me anyway. The manufacturer builds a hardware, and programs a BIOS/Bootloader in the system. No idea what kind of IDE and compiler they use for that.
For their customers they provide basic support for open source tools which don't require a license. They probably are not very proficient with these tools. Maybe that's the reason why they recommend to use the C++ linker instead of the C linker. The latter didn't work for them and they found by trial and error that the former does, so they recommend that setting to their customers. Just a theory of course, but we can't expect in depth expertise from them, and therefore the documentation doesn't help either.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version