BGCode install #12
Comments
|
try installing zlib with the following command in SSH and then reinstall the plugin. |
|
The other option is just to disable the bgcode format from the slicer completely and not use that format. you don't gain anything from it with OctoPrint.
|
|
I believe the issue might be here: https://github.com/jneilliii/libbgcode/blob/main/CMakeLists.txt#L120 Apparently version argument has to be on the second argument to Interestingly enough on Alpine linux chroot used for octo4a if one does not install |
E: Unable to locate package zlib-dev |
When I revert prusaslicer to gcode from bgcode I see that prusalink, should I decide to ask it to print instead of octoprint, does not draw the picture of the object being printed, so I'd like to use bgcode for that reason alone at this stage. |
|
Embedded thumbnails in gcode doesn't work with the new firmware? My Slicer Thumbnails plugin can extract those from the gcode file on upload to OctoPrint. If your slicer is configured for OctoPrint instead of PrusaLink you should be able to send directly to OctoPrint, but I don't understand the first part of your statement.
|
If I drop a gcode file into prusalink it does not show the image, if i drop a bgcode one in it does show the image. See screenshot. Both come from prusaslicer set to print on a prusa Mk3.5
|
|
I wonder if these instructions might help you....extracted from #11 (comment) |
All are already installed |
|
Hi, I had the same issue, upgrading from an old install of octoprint when upgrading from a Prusa MK3s+ to a Mk3.9. |
|
@Flatstrap , thanks for the tip but it didn't help. Installing plugin "BGCode" from https://github.com/jneilliii/OctoPrint-BGCode/archive/master.zip... -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY PY_BUILD_CMAKE_PACKAGE_NAME -- Build files have been written to: /tmp/pip-install-v3288la_/pybgcode_69c4b944712c4a618a122f37089b0cb1/.py-build-cmake_cache/cp37-cp37m-linux_armv7l During handling of the above exception, another exception occurred: Traceback (most recent call last):
|
|
Also having issues installing it. `Installing plugin "BGCode" from https://github.com/jneilliii/OctoPrint-BGCode/archive/master.zip... × Preparing metadata (pyproject.toml) did not run successfully. find_package(ZLIB COMPONENTS ...) will always fail. CMake Error at /tmp/pip-build-env-euxcxv74/normal/lib/python3.7/site-packages/cmake/data/share/cmake-3.29/Modules/FindPackageHandleStandardArgs.cmake:230 (message): -- Configuring incomplete, errors occurred! note: This error originates from a subprocess, and is likely not a problem with pip. × Encountered error while generating package metadata. note: This is an issue with the package mentioned above, not pip. |
|
I didn't make the underlying package, PrusaResearch did. Whatever build dependencies that are necessary for building it from their repo should give you a hint as to what you might need to install the plugin successfully. The one that seems to stand out is missing zlib-dev. So you could try |
|
On Debian, Ubuntu etc, it's Would you be open to upload the plugin to PyPI, in case even with pre-compiled wheels? I could help with GitHub Actions workflows to do this either triggered, or automatically when a new release is tagged. |
|
I'm totally open to that, but really wish the PrusaResearch team would do it on their repo so I can just have it as a dependency in my plugin. For the actions I assume those would be made against the other repo I've forked from them. I was using a fork since there's no telling what they are changing without any release/versioning happening. |
|
ideally, compatible with 32bit octopi images... |
Oh that's true, I did not recognise this dependency. Hmm, of course you could theoretically publish libbgcode as fork on PyPI as well, but that is not optimal. I found the requests upstream: They even have the build workflows already: https://github.com/prusa3d/libbgcode/actions/runs/8466159186 We could edit the workflow on your fork to test all this and do uploads to https://test.pypi.org/ with a different module name (to avoid conflicts with PrusaResearch, in case they want to do the same). And when everything works well, do a PR. Since there is no reaction on the two linked issues, a PR seems to be the only chance to bring things forward. |
I'm cool with that approach. I'll add you as a contributor to my fork to make this process a little easier. |
|
sudo apt install cmake |
|
@MichaIng @jneilliii any progress on this? Thanks so much in advance! |
|
Coincidentally I found some time today to review this issue, and have the GitHub Actions workflow open in my notepad++ right now 😄. But I did not yet start to implement the changes. First, Will most likely open a PR tomorrow. |
|
I don't really know what you have to pass to |
|
@MichaIng has already started on the PR here: jneilliii/libbgcode#1 can't remember if it's ready or not to merge TBH. |
|
Ah, I wanted to split off the |
Running octoprint on a Pi.
It has worked well for a few years talking to a Prusa Mk3S+.
I've just upgraded the Prusa to Mk3.5 where Prusaslicer delivers BGCode.
So, I select your BGCode plugin to install. It says successfully installed at end but does not show up in the plugin list.
I reran the install, same problem, here is the log,
I am running octoprint 1.9.3
Any suggestions?
The text was updated successfully, but these errors were encountered: