#163 Building project on Eclipse using GNU ARM
Hello,
I am trying to build a project (uPy) using Eclipse (Mars), and have come across the GNU ARM toolchain and Eclipse environment.
Having followed the instructions in the gnuarmeclipse website (installing the relevant build and toolchain environment), the test program works fine, yet when I try to open the project that I'm working on (using http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2Fgetting_started%2Fcdt_w_import.htm) and build using the GNU ARM toolchain, I receive the following error message:
22:54:17 * Incremental Build of configuration Default for project uPy_board_ARMgcc *
make all
Use make V=1 or set BUILD_VERBOSE in your environment to increase build verbosity.
mkdir -p build-PYBV10/genhdr
../py/mkrules.mk:75: recipe for target 'build-PYBV10/genhdr' failed
process_begin: CreateProcess(NULL, mkdir -p build-PYBV10/genhdr, ...) failed.
make (e=2): The system cannot find the file specified.
make: *** [build-PYBV10/genhdr] Error 2
22:54:17 Build Finished (took 479ms)
Regards,
Adam
Using:
Eclipse Mars
Java Version 8 update 60
GNU ARM cross compiler (in eclipse) 1.14.1.201508190739
Windows 10
Toolchain (pre built gnu) 4.9 2015 q2
Discussion
my first guess would be the use of the import procedure. in Eclipse you can safely import a project only if it was exported by the very same plug-ins, otherwise unexpected things might happen.
in addition, your project does not seem to be a managed project, but a makefile project, which completely avoids the Eclipse configuration pages. it can be configured to work in Eclipse, but you need to know what you are doing.
i understand that it is developed under linux, and am looking to set up a windows dev environment.
yes, it is a makefile project - with quite a complicated makefile. what steps would i need (or is there any available documentation) to configure it to work in Eclipse?
for makefile projects you need first to make them work manually in a terminal.
once done, you can figure out how to run them in Eclipse.
I suggest you start with a manually written minimal makefile (single .c source file Hello World) and then move to more complicated things.
I have had success doing that and have the general idea of how they work. The makefile that I am using is maintained by other developers, so I am more interested in being able to set up a 'simple' build environment with a visual debug.
Eclipse seems to be the ideal tool to do this, and I am able to compile the entire project under MinGW. However, from what I understand, this would not work for an ARM processor - so when trying to build using the ARM build/toolchain I am running into problems.
From the error messsage, I am assuming that the problem is something to do with the mkdir exe? Or is it possible that I have not set up the toolchain correctly?
as I said, you need to first make the build process work manually in a terminal, without any Eclipse or other visual environment; until you succeed on this it makes no sense to expect Eclipse to work.
if you installed the GNU ARM Eclipse Windows Build Tools, this package is taylored for managed projects make files, it does not include ANY program that might be required in a custom makefile.
however, since it uses busybox, you can try to copy busybox.exe as mkdir.exe (and possibly other executables).
ok - so the project compiles under MinGW in a terminal, with the arm-none-eabi-gcc added to the system path.
I'll give that a go (busybox) and see what happens
Thanks,
Adam
adding mingw and/or the toolchain to system path is generally a very bad idea, and interferes with the path management features implemented in the Eclipse plug-ins.
it might be possible to make it work, but you're on your own.
so mingw isn't on the system path, just the arm-none-... upon removing it from the system path, nothing works
using busybox doesn't change anything either
what do you mean by managed projects?
project with the makefile automatically generated by Eclipse CDT
did you figure out how to use the plug-ins to build your project?