Welcome! Log In Create A New Profile

Advanced

moving from bug-fix build to release build

Posted by doug_scott 
moving from bug-fix build to release build
April 13, 2020 06:51PM
I have been running the bug-fix source of Marlin for quite a while and decided to move over to the release version instead. I figured I should be able to just copy my 2 config files and the platformio.ini file into the new source directory, then create the new workspace in Visual Studio Code. Did that, and ran the build. Got errors about running old config files, so I changed the version info inside the 2 files to 200005 and ran the build again. Next errors were in regards to #define Z_SAFE_HOMING not being enabled, so I enabled it. Now I get a warning saying
"warning: Calling missing SConscript without error is deprecated.
Transition by adding must_exist=0 to SConscript calls.
Missing SConscript 'Marlin\src\HAL\HAL_LPC1768\upload_extra_script.py'
File "C:\Users\Administrator\.platformio\penv\lib\site-packages\platformio\builder\main.py", line 164, in "

followed by
"In file included from Marlin\src\module/stepper/trinamic.h:29,
from Marlin\src\module/stepper/indirection.h:44,
Compiling .pio\build\LPC1768\src\src\core\utility.cpp.o
from Marlin\src\module/stepper.h:47,
from Marlin\src\MarlinCore.cpp:37:
.pio\libdeps\LPC1768\TMCStepper_ID5513\src/TMCStepper.h:14:10: fatal error: SPI.h: No such file or directory
14 | #include
| ^~~~~~~
compilation terminated.
*** [.pio\build\LPC1768\src\src\MarlinCore.cpp.o] Error 1"

Any ideas on how to correct this? I have checked and there are 3 different SPI.h files in the directory structure, none of which are in the directory where TMCStepper.h file is located. The SPI.h is mentioned in the TMCStepper.h file without any relative folder information, and to me that means the file must reside in the same folder, or be in the folder where the TMCStepper.h file is mentioned. I am not a programmer, and I am using old DOS batch file logic to arrive at that opinion. Inside the TMCStepper.h file it also includes a file named "Stream.h", again without any relative folder information, and that file does not exist in the folder that contains the TMCStepper.h file.
Re: moving from bug-fix build to release build
April 27, 2020 08:04PM
I just had this same error after merging the mainline into my branch that had been isolated for some time. In the end, I made a fresh copy of the unaltered Marlin code, then introduced my configuration changes in stages, testing if it built, in order to figure out which configuration option caused the errors. Turns out, none of them were the problem. When I finished, and the fresh copy had all of my configuration in it, it still built. So, then I did a diff of the directories to see what was different, and I found that the platformio.ini file had outdated lib_deps values. Maybe that will fix it for you too? Also make sure that your Platform IO libraries are all up-to-date. Hope that helps :-)
Re: moving from bug-fix build to release build
May 01, 2020 10:58AM
Thanks for the reply. Here is what I have under lib_deps. I do not really understand what you mean by outdated, but, I do see that the U8glib-HAL is using a bugfix.zip link, since I am trying to run a release build of Marlin, shouldn't this be linked to something other than "bugfix.zip"?

lib_deps =
LiquidCrystal
TMCStepper@>=0.6.1,<1.0.0
Adafruit NeoPixel
U8glib-HAL=https://github.com/MarlinFirmware/U8glib-HAL/archive/bugfix.zip
Adafruit_MAX31865=https://github.com/adafruit/Adafruit_MAX31865/archive/master.zip
LiquidTWI2=https://github.com/lincomatic/LiquidTWI2/archive/master.zip
Arduino-L6470=https://github.com/ameyer/Arduino-L6470/archive/0.8.0.zip
SailfishLCD=https://github.com/mikeshub/SailfishLCD/archive/master.zip
SailfishRGB_LED=https://github.com/mikeshub/SailfishRGB_LED/archive/master.zip
SlowSoftI2CMaster=https://github.com/mikeshub/SlowSoftI2CMaster/archive/master.zip
Re: moving from bug-fix build to release build
May 02, 2020 02:30AM
I recommend always copying the settings manually. There can be so many changes that you miss otherwise. It doesn't always have to give errors but some values that are related to values elsewhere in other files might have changed relatively and it can cause all sorts of issues. Prepare for problems if you copy paste files around from different releases of Marlin.


http://www.marinusdebeer.nl/
Sorry, only registered users may post in this forum.

Click here to login