Eclipse Community Forums: C / C++ IDE (CDT) » Eclipse autotools

Home » Language IDEs » C / C++ IDE (CDT) » Eclipse autotools - part 2 (make / makefile verbose )

Eclipse autotools - part 2 [message #1773215]

Sun, 24 September 2017 16:56

Eclipse User

Simple question
Is there a way to option ALL autolool make files to output verbose in ONE place?

From Eclipse "help"
Build (Project ?) runs "configure " first than --- what ?

apparently on first attempt autoconfig
and when successful than autoreconf from then on.

Since the actual outputs go to DIFFERENT consoles it it harder to keep tract of progress or no progress / debug.

The individual autotools options also appear NOT to be permanent / saved .

[Updated on: Sun, 24 September 2017 16:58] by Moderator

Re: Eclipse autotools - part 2 [message #1773219 is a reply to message #1773215]

Sun, 24 September 2017 20:53

Eclipse User

Like most things with Eclipse it's best to be able to do them without Eclipse then you'll understand what Eclipse is doing for you.

Although I usually add the autotools flavor to my projects which use Autotools, I rarely use the commands in the plugin.
Once you have Makefile.am in all subdirectories and configure.ac you often only need:

autoreconf --install --force
./configure

and, unless you are changing the .am and .ac files, you are done with Autotools for most projects.
You can also make a shell script to do them which is handy for remembering configure options.

I usually execute them from a terminal then refresh the project in the Project Explorer view.
Afterward, I treat the project as a Makefile project.

EDIT:
This may put you in the right direction:
https://www.gnu.org/software/automake/manual/html_node/Creating-amhello.html#Creating-amhello

Along with:
https://www.gnu.org/software/autoconf/manual/autoconf.html
https://www.gnu.org/software/autoconf/manual/automake.html
https://www.gnu.org/software/libtool/manual/libtool.html

[Updated on: Mon, 25 September 2017 01:48] by Moderator

Re: Eclipse autotools - part 2 [message #1773251 is a reply to message #1773219]

Mon, 25 September 2017 10:59

Eclipse User

Thanks for the reply.
I realize my mistakes - first one was selecting Eclipse to develop software for Raspberry Pi.
This may by an understatement - but Eclipse is NO IDE. Its "integration " stops after "Hello world".

Secondly - I have been avoiding to learn how "make" fits into the scheme of things, hoping that GUI IDE will do the dirty work for me.
Not so.

Now I have no choice but to dive into this mess by totally reversing MY development process by doing the "make" first.

Cheers
Vaclav

Previous Topic:	Can't run c code after building it: Launch failed. Binary not found.
Next Topic:	CDT source code build error

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Mar 19 03:27:57 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter