synthetos / g2

g2core - The Next Generation
Other
622 stars 296 forks source link

Error Compiling: Windows 10 Atmel Studio #497

Closed toozinger closed 3 years ago

toozinger commented 3 years ago

Hi all,

I seem to be stuck with the same/similar errors as mentioned in #163, #252, #366, and #437.

Why I'm trying to compile: I was able to flash the most recent release to my Due and move an axis and test some functionality, but the pin mappings for the custom digital output pins are all set to -1, and this is a function I very much would like to use. If there's an easier way to re-map pins or get some signal output during machine operation, I'm open to other options.

Error

recipe for target '../Motate/MotateProject/motate/../../Tools/win32/gcc-arm-none-eabi/bin' failed
recipe for target 'win32/gcc-arm-none-eabi' failed

Output

------ Build started: Project: g2core, Configuration: gShield ARM ------
Build started.
Project "g2core.cppproj" (default targets):
Target "PreBuildEvent" skipped, due to false condition; ('$(PreBuildEvent)'!='') was evaluated as (''!='').
Target "CoreBuild" in file "C:\Program Files (x86)\Atmel\Studio\7.0\Vs\Compiler.targets" from project "C:\Users\dowdt\g2\g2core\g2core.cppproj" (target "Build" depends on it):
    Using "RunCompilerTask" task from assembly "C:\Program Files (x86)\Atmel\Studio\7.0\Extensions\Application\AvrGCC.dll".
    Task "RunCompilerTask"
        Shell Utils Path C:\Program Files (x86)\Atmel\Studio\7.0\shellUtils
        C:\Program Files (x86)\Atmel\Studio\7.0\shellUtils\make.exe -C "C:\Users\dowdt\g2\g2core" -f "Makefile" BOARD=gShield CONFIG=ShapeokoDualY COLOR=0 VERBOSE=1 
        make: Entering directory 'C:/Users/dowdt/g2/g2core'
        "Found that we're in Atmel Studio"
        The system cannot find the path specified.
        Installing the necessary tools...
        cd ../Motate/MotateProject/motate/../../Tools && make "ARCH=gcc-arm-none-eabi"
        make[1]: Entering directory 'C:/Users/dowdt/g2/Motate/Tools'
        The system cannot find the path specified.
        mkdir -p win32 && cd win32 && ../7za/7za x -ogcc-arm-none-eabi "gcc-arm-none-eabi-5_4-2016q2-20160622-win32.zip"zip"
        A subdirectory or file -p already exists.
        Error occurred while processing: -p.
        A subdirectory or file win32 already exists.
        Error occurred while processing: win32.
        make[1]: *** [win32/gcc-arm-none-eabi] Error 1
C:\Users\dowdt\g2\g2core\Makefile(135,1): error: recipe for target 'win32/gcc-arm-none-eabi' failed
        make[1]: Leaving directory 'C:/Users/dowdt/g2/Motate/Tools'
C:\Users\dowdt\g2\Motate\MotateProject\motate\Motate.mk(404,1): error: recipe for target '../Motate/MotateProject/motate/../../Tools/win32/gcc-arm-none-eabi/bin' failed
        make: *** [../Motate/MotateProject/motate/../../Tools/win32/gcc-arm-none-eabi/bin] Error 2
        make: Leaving directory 'C:/Users/dowdt/g2/g2core'
    Done executing task "RunCompilerTask" -- FAILED.
Done building target "CoreBuild" in project "g2core.cppproj" -- FAILED.
Done building project "g2core.cppproj" -- FAILED.

Build FAILED.
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========

Troubleshooting

As per #163: I tried deleting the "-p" and "win32" folders in Motate, but it still downloads these files and then has the same conflict again.

As per #252: I have 64bit git installed (version 2.31.1.1). I also confirmed that curl was usable in cmd and git-bash. I was a little confused on the "7za" issue/resolution.

As per #366: I'm not sure if my git install is pointed to correctly in the "Motate.mk" file. Per the installation instructions, I should check line 236, which for me is OS := WIN32, but line 238 (which I assume is the udpated line number?) is PATH := $(TOOLS_PATH)/$(TOOLS_SUBPATH)/bin;c:\Program Files\Git\bin;c:\Program Files\Git\cmd;c:\Program Files\Git\mingw32\bin;c:\Program Files\Git\mingw64\bin;$(PATH), and I'm unsure how that relates to my git install on C:\Users\dowdt\AppData\Local\Programs\Git

As per #437: I have confirmed my git install is 64 bit, as it's in \Programs and not \Program Files (x86)

Thanks!

-Teal

toozinger commented 3 years ago

I have decided to instead move to the grbl_esp32 project.