Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » C / C++ IDE (CDT) » Eclipse autotool usage / hierarchy (implementing / invoking autotools in Eclipse IDE )
Eclipse autotool usage / hierarchy [message #1772852] Sun, 17 September 2017 16:09 Go to next message
Vaclav Sal is currently offline Vaclav SalFriend
Messages: 163
Registered: September 2014
Senior Member
There are many tutorials on autotools.
I have been using this one

The tutorial is OK , but the author choose to complicate things with importing existing file instead of just building "Hello world" project from scratch.

The most important part , IMHO, is the following sentence:

Now, BEFORE building the project for the first time, let's take a look at the properties of the project, where you can see we now have an autotools part, where you can customize the autotools versions you might want to use (I

What I am having an issue with is how Eclipse and autotools interact , because another tutorial laconically states that "Buidl Project" is all what needs to be done to come up with executable.

So far autottols ( configure?) builds "Build(GNU) " configuration only ( no "Host(GNU) " and when I attempt to use it I can only execute "Local C/C++ Application" configuration.

Here is another "automatic under the hood" Eclipse behaviour . After adding host armv71-unknown-linux-gnueabihf to "Platform specifiers" I get this in "CDT Global build console" - but I have to select the "GDT global console" to see the output so the "automatic" behaviour of IDE is not really fully automatic.
I my opinion changing the "Platform specifier" should not trigger the "Generating Makefile" in first place.

There are "invoking autotools" options like autoconf and autoreconf - neither one by default gives any meaningful output when "invoked".

I am not asking for how to utilize autotools, just like to know if there is a overall document how Eclipse works when I actually "invoke" any autotool.

Perhaps all these tools need verbose option as general default , they are after all developers tools and he could use as much help as feasible during development.
Making things "automatic" without documentation is not very helpful.

Here is a sample output of invoking "configure " to create "makefile" - from unknown origin / source:

Generating Makefile in build directory: /home/os64/eclipse-7/TEST_3/

sh -c "/home/os64/eclipse-7/TEST_3/configure --host=armv71-unknown-linux-gnueabihf --target=armv71-unknown-linux-gnueabihf"
checking build system type... x86_64-unknown-linux-gnu
checking host system type... armv71-unknown-linux-gnueabihf
checking target system type... armv71-unknown-linux-gnueabihf
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for armv71-unknown-linux-gnueabihf-strip... no
checking for armv71-unknown-linux-gnueabihf-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for armv71-unknown-linux-gnueabihf-gcc... no
checking for armv71-unknown-linux-gnueabihf-gcc... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: executing depfiles commands
[Operation successful]

Re: Eclipse autotool usage / hierarchy [message #1772855 is a reply to message #1772852] Sun, 17 September 2017 17:47 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 29187
Registered: July 2009
Senior Member
Questions about C/C++ are best asked on the CDT forum.
Previous Topic:Can another Plugin be triggered after creating a new project
Next Topic:Eclipse and autotools
Goto Forum:

Current Time: Wed Feb 21 10:07:34 GMT 2018

Powered by FUDForum. Page generated in 0.01640 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software