µTasker Forum
µTasker Forum => NXPTM M522XX, KINETIS and i.MX RT => Topic started by: mark on February 09, 2018, 12:22:23 AM
-
Hi All
The Kinetis project includes a BAT file that can be used as a port-build step in Visual Studio to cross-compile for the HW target.
I don't know why but some versions of make.exe, which is used in the GNU tool chain (for example by KDS) gives an error when it tries to work with the make file and the error is
make (e=2): The system cannot find the file specified.
Possibly it has something to do with formatting in the make file (like use of TABs and/or spaces) since I know that this was rather sensitive in the past.
If this problem occurs I use a version of make.exe that i have copied for a version of the tool-chain that has always operated well/correctly and simply replace the one that fails.
This version is attached for use by anyone who encounters the same issue...
Good luck
Regards
Mark
P.S. The attached version is as follows (make -v)
GNU Make 3.82
Built for i686-w64-mingw32
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
An example of a version that fails can't display its details due to a missing DLL called "intl.dll", which may be the reason for the error when not used in a certain environment.
-
Hi Mark,
By default the path in BAT file "Build_Kinetis.bat" was set to "D" drive and I had to change it to "C" where I installed the KDS
SET PATH=%PATH%;D:\Freescale\KDS_v3\Toolchain\bin
SET PATH=%PATH%;C:\Freescale\KDS_v3\Toolchain\bin
Thanks,
-
Hi
I have a small SSD (C:) and a large conventional drive (D:) so have installed KDS on drive D:, and I use the GCC binaries from there too.
Yes, the path in the .bat file needs to point to whatever GCC version is being used so will usually need adjusting.
Regards
Mark