Eclipse Community Forums: C / C++ IDE (CDT) » Gcc cross - arm linux gnuebihf

Home » Language IDEs » C / C++ IDE (CDT) » Gcc cross - arm linux gnuebihf - compiling problem

Gcc cross - arm linux gnuebihf - compiling problem [message #1806824]

Wed, 15 May 2019 13:15

Eclipse User

I have problem with implementating the library .a file for eclipse.

Already i have add the library file in Proporties>C/C++ General>Paths and Symbols>Libraries and earesed the .a at the end of the filename. Couse otherwise eclipse toolchain can't see the lib file.

But now i have problem with building the whole code. I have error like that:

makefile:31: recipe for target 'LED_TESTER_V1' failed" with line: @echo 'Building target: $@'

Probably i didin't add some parameters that is needed to compile my library.

I'm using the gpio library from the element14 named iolib.

In the instruction is: "Compile using: gcc -c main.c -o main.o followed by gcc main.o liofunc o main_app"

Maybe i need to add somewhere -liofunc but i don't know where. Or this is another problem.

Here you have two screenshots:

Attachment: fVX7R.png
(Size: 189.88KB, Downloaded 79 times)
Attachment: VDB0s.png
(Size: 183.01KB, Downloaded 84 times)

Re: Gcc cross - arm linux gnuebihf - compiling problem [message #1806925 is a reply to message #1806824]

Fri, 17 May 2019 14:34

Eclipse User

Please go get the GNU linker manual <https://www.gnu.org/manual/manual.en.html>.
The linker (ld) manual is a part of the Binutils package.

The manual explains the two options how to specify a library file.

Re: Gcc cross - arm linux gnuebihf - compiling problem [message #1806952 is a reply to message #1806925]

Sun, 19 May 2019 04:59

Eclipse User

Your error seems to be a -lxxx with the xxx missing.
Note: the error you highlighted is just make telling you something went wrong.
The actual error precedes it in the log.

I think the dialogs in Project --> Properties --> C/C++ General --> Paths and Symbols
are misleading.

I think on the Libraries tab, you should only put the library base name.
For example, for libxxx.a you would just put xxx
The paths to the libraries are placed in the Library Paths tab
In your case, xxx should be iofunc

Frankly, I don't use these dialogs. Instead I use the dialog panes found at
Project --> Properties --> C/C++ Build --> Settings --> Tool Settings tab --> Linker --> Libraries
I think they are easier to use.
Of course, YMMV

[Updated on: Sun, 19 May 2019 05:07] by Moderator

Previous Topic:	Cannot complete the install C/C++ Gt Support
Next Topic:	catkin_make --force-cmake -G "Ecplise CDT4 - Unix Makefiles" fails

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Nov 06 20:51:28 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter