 Technical error [message #1750107] |
Fri, 16 December 2016 08:22  |
|
Hi Everyone,
I look forward to whom who knows CDT error well in this forum.
Suddenly my error console says, 
Invoking autoreconf in build directory: C:/STM32_toolchain/Workspace/adapt_rc/Debug
Configuration failed with error
(Cannot run program "sh" (in directory "C:\STM32_toolchain\Workspace\adapt_rc"): CreateProcess error=2,
Let me know what type of error it is?
1. Make file?
2. Project profile?
3. Build configuration?
4. Autotools ?
|
|
|
|
| Re: Technical error [message #1750226 is a reply to message #1750165] |
Mon, 19 December 2016 06:22  |
|
Quote:It's not a CDT error.
Yes, may be , I am unknown to it. I keep posting this issue in Newcomer also.
Quote:The message means that 'sh' couldn't be found. Some project distributions have an installation script named something like bootstrap.sh or autoconf.sh These build the configure script.
I see. nice information. You mean these installer support Ecilipse to run program?
Quote:You also need a version of autotools .
I have arranged a new project. Previously I didnt see autotools.
Kindly suggest me how to remove it from my project properties?
Quote:These are provided by MinGW or cygwin.
My application is ARM based project, these will not support I heard from compiler forum.
|
|
|
| Re: Technical error [message #1750259 is a reply to message #1750226] |
Mon, 19 December 2016 11:16 |
David Vavra
Messages: 1426
Registered: October 2012 |
Senior Member |
|
|
You perpetually seem to misunderstand what it is Eclipse does for you.
It is an editor which provides a platform for creating make files; executing Make to build the executables; and running the program with and without the debugger. With the exception of Make (which Eclipse can emulate) and beyond editing, all tools used are external to Eclipse. You have to provide them. It is your responsibility to understand how they work outside of Eclipse.
Autotools builds the configure script which, in turn, builds the Makefile(s) so Eclipse is not involved in creating the make files. The Autotools plugin allows Eclipse to interact with the external autotools. Autotools expects that you have a shell conformant to the sh specifications.
If you expect to use Eclipse to run the autotools functions then you need
1) a version of Autotools compatible with Windows;
2) a shell compatible with both sh and Windows;
3) to install them somewhere; and
4) fix your system PATH to point toward them
The (not necessarily current) Eclipse Autotools User's Guide:
https://wiki.eclipse.org/Linux_Tools_Project/Autotools/User_Guide
Note: "The Autotools plug-in is not supported under a regular Windows environment "
Autotools Plug-in User Guide in the Neon help document:
http://help.eclipse.org/neon/index.jsp?nav=%2F7
As far as I know, only cygwin provides a way for fully implementing autotools under Windows. At least GNU (the author of Autotools) seems to expect you to use cygwin.
https://en.wikipedia.org/wiki/GNU_Build_System
https://sourceware.org/autobook/autobook/autobook_135.html
MinGW may. If you only intend to run the configure script build by autotools, then you only need a compatible shell and (I think) a windows version of AutoConf.
http://www.mingw.org/category/wiki/autotools
http://gnuwin32.sourceforge.net/packages/autoconf.htm
You should learn to use autotools as a standalone tool set or you will likely never understand what Eclipse is doing with them. Frankly, outside of the editors for Autotools files, I've found the Autotools plugin to be unhelpful and that it's best to run the tools outside of Eclipse. YMMV
If you don't want Autotools (which makes me wonder why you created an Autotools project), it's easier to delete the project and create a new one without Autotools.
[Updated on: Mon, 19 December 2016 13:32] Report message to a moderator |
|
|
|
| Re: Technical error [message #1750331 is a reply to message #1750259] |
Tue, 20 December 2016 04:42 |
|
Quote:You should learn to use autotools as a standalone tool set or you will likely never understand what Eclipse is doing with them. Frankly, outside of the editors for Autotools files, I've found the Autotools plugin to be unhelpful and that it's best to run the tools outside of Eclipse. YMMV
I beg pardon what do you mean here by outside?
Quote:If you don't want Autotools (which makes me wonder why you created an Autotools project), it's easier to delete the project and create a new one without Autotools.
If I delete and create new one, which step is wrong selection of auto-tools ?
|
|
|
Powered by
FUDForum. Page generated in 0.03933 seconds
] 
Search
Help
Register
Login
Home
