User forums > Embedded development
advanced C++ features with GNU GCC for ARM
stahta01:
Since you ignored my advice I am now ignoring you!
Tim S.
oBFusCATed:
Pavel_47:
When you've set your project to use custom makefile then you've told CB - "I know what I'm doing and handle everything related to the build".
So if you want to use one specific compiler with your makefile then you need to modify it. CB cannot set the compiler for you!
What you need to do is open a cmd window; cd to the root of your project and then run make -f <yourmakefile> then fix any errors you encounter.
Changing options in the compiler or project settings won't have any effect on your build.
So you're on your own here...
Pavel_47:
--- Quote from: stahta01 on November 05, 2014, 05:45:36 pm ---Since you ignored my advice I am now ignoring you!
Tim S.
--- End quote ---
Hello Tim,
Sorry
I was misunderstood.
I have no any intention to ignore your suggestions as well as anyone who answer me.
The problem with my projetc(s) - they are closely related to Contiki staff, where the code behavior is strongly dependent on different option flags that are placed in different locations - essentially in headers, but also in custom make files.
So, it's recommended by Contiki experts to use custom make files.
Probably there is another way to take into account Contiki compiler options put into make file.
For the moment I have no idea how to do it (i.e. where to place Contiki compiler options in CB interface) ... your suggestions here are wellcome.
Nevertheless I've tried to create project and compile it with "default" make.
The project type was "Console Application".
I've also tried with "ARM Project", but even couldn't succeed to create project - on step "Please select compiler to use" there were no any options in the "Compiler" combobox.
Here is compiler log with default make:
--- Code: ---||=== Build: Debug in C_Features_Test (compiler: GNU GCC Compiler for ARM) ===|
c:\program files (x86)\gnu tools arm embedded\4.8 2014q1\bin\..\lib\gcc\arm-none-eabi\4.8.3\..\..\..\..\arm-none-eabi\lib\libc.a(lib_a-exit.o)||In function `exit':|
exit.c:(.text.exit+0x2c)||undefined reference to `_exit'|
c:\program files (x86)\gnu tools arm embedded\4.8 2014q1\bin\..\lib\gcc\arm-none-eabi\4.8.3\..\..\..\..\arm-none-eabi\lib\libc.a(lib_a-sbrkr.o)||In function `_sbrk_r':|
sbrkr.c:(.text._sbrk_r+0x18)||undefined reference to `_sbrk'|
c:\program files (x86)\gnu tools arm embedded\4.8 2014q1\bin\..\lib\gcc\arm-none-eabi\4.8.3\..\..\..\..\arm-none-eabi\lib\libc.a(lib_a-writer.o)||In function `_write_r':|
writer.c:(.text._write_r+0x20)||undefined reference to `_write'|
c:\program files (x86)\gnu tools arm embedded\4.8 2014q1\bin\..\lib\gcc\arm-none-eabi\4.8.3\..\..\..\..\arm-none-eabi\lib\libc.a(lib_a-closer.o)||In function `_close_r':|
closer.c:(.text._close_r+0x18)||undefined reference to `_close'|
c:\program files (x86)\gnu tools arm embedded\4.8 2014q1\bin\..\lib\gcc\arm-none-eabi\4.8.3\..\..\..\..\arm-none-eabi\lib\libc.a(lib_a-fstatr.o)||In function `_fstat_r':|
fstatr.c:(.text._fstat_r+0x1c)||undefined reference to `_fstat'|
c:\program files (x86)\gnu tools arm embedded\4.8 2014q1\bin\..\lib\gcc\arm-none-eabi\4.8.3\..\..\..\..\arm-none-eabi\lib\libc.a(lib_a-isattyr.o)||In function `_isatty_r':|
isattyr.c:(.text._isatty_r+0x18)||undefined reference to `_isatty'|
c:\program files (x86)\gnu tools arm embedded\4.8 2014q1\bin\..\lib\gcc\arm-none-eabi\4.8.3\..\..\..\..\arm-none-eabi\lib\libc.a(lib_a-lseekr.o)||In function `_lseek_r':|
lseekr.c:(.text._lseek_r+0x20)||undefined reference to `_lseek'|
c:\program files (x86)\gnu tools arm embedded\4.8 2014q1\bin\..\lib\gcc\arm-none-eabi\4.8.3\..\..\..\..\arm-none-eabi\lib\libc.a(lib_a-readr.o)||In function `_read_r':|
readr.c:(.text._read_r+0x20)||undefined reference to `_read'|
||=== Build failed: 8 error(s), 0 warning(s) (0 minute(s), 0 second(s)) ===|
--- End code ---
Best Regards
Pavel
Pavel_47:
--- Quote from: oBFusCATed on November 05, 2014, 06:46:33 pm ---Pavel_47:
When you've set your project to use custom makefile then you've told CB - "I know what I'm doing and handle everything related to the build".
So if you want to use one specific compiler with your makefile then you need to modify it. CB cannot set the compiler for you!
--- End quote ---
Hello oBFusCATed
First, thanks for response.
1. If CB cannot set the compiler for me, what signifies the following interface (please, see the snapshot below)
2. I've tried to compile in cmd window as you suggested (i.e. run make -f <yourmakefile>). The output is exactly the same as in "Build log" window of CB ... so I still don't see which executables are used for making projects.
Best Regards
Pavel
[attachment deleted by admin]
oBFusCATed:
If you use a custom makefile project, this dialog is ignored.
If you have a normal cb project, then try to rebuild it and post the full build log if it fails.
Navigation
[0] Message Index
[*] Previous page
Go to full version