Hey there,
I am not really following the Sli3r project too intensely but work with it for cutting & combining STL objects under Linux. Quite a while ago I came across the Wiki for Slic3r for using the CLI when watching out for a solution to do mass conversion from 3MF to STL. It took me quite a while to understand that the Wiki entry for CLI is not really meant for the Perl / C++ Version which is around for Linux, Mac and Windows but the C++ version of Slic3r.
I haven't found a pre-compiled version of Slic3r C++ but was able to compile it using a provided Docker Build container and installing a whole lot of libs related to some Boost stuff IIRC. The Wiki for Slic3r links to non-existent containers.
Ok, my questions so far:
1) Wouldn't it make sense to "relabel" Slic3r in the C++ to a somewhat different name for this CLI stuff ? It seems to make less sense to me providing a CLI description for a tool which is essentially a different tool which everybody uses ? May be slic3r-cli or slic3r-c++ ?
2) Wouldn't it not also make sense to provide a pre-compiled package for slic3r-cl (or whatever once calls this) ?
Hey there, I am not really following the Sli3r project too intensely but work with it for cutting & combining STL objects under Linux. Quite a while ago I came across the Wiki for Slic3r for using the CLI when watching out for a solution to do mass conversion from 3MF to STL. It took me quite a while to understand that the Wiki entry for CLI is not really meant for the Perl / C++ Version which is around for Linux, Mac and Windows but the C++ version of Slic3r.
I haven't found a pre-compiled version of Slic3r C++ but was able to compile it using a provided Docker Build container and installing a whole lot of libs related to some Boost stuff IIRC. The Wiki for Slic3r links to non-existent containers.
Ok, my questions so far: 1) Wouldn't it make sense to "relabel" Slic3r in the C++ to a somewhat different name for this CLI stuff ? It seems to make less sense to me providing a CLI description for a tool which is essentially a different tool which everybody uses ? May be slic3r-cli or slic3r-c++ ? 2) Wouldn't it not also make sense to provide a pre-compiled package for slic3r-cl (or whatever once calls this) ?