Easy way to get started to contribute ?

[DzzD]

Hello,

I would like to contribute to Super Slicer, for some ressources but also as a developer, unfortunatly I cant find any clear path to get started and I am confused in the relation betwenn Super Slicer/Slic3r/Prusa Slicer.

Does anyone can give me a clear path to get started (more for window, but I am also interrested by general information )?

I have read the windows article on this reository but I would like more or clearer exlanatinon plz....

[supermerill]

Hello
First, you have to succeed to compile it.
Then, you can modify a little thing you want to work on, like a new infill pattern.
after that, ask for a pull request to have your contribution merged.

I don't know what could motivate you, i can help you by explaining how some part of the software works, if you have an idea to implement.

[DzzD]

I decided tonight to give a try to compile, but failed on cmake :/

I use this line : cmake .. -G "Visual Studio 17 2022" -A x64

because the 16 2019 was giving me another error

Can you help ?

EDIT: forget aboout this I will install 2019 tool

[supermerill]

you have to install visual studio 2019

[DzzD]

I was thinking that 2022 will be able to compile for 2019 :/ so I need to find a place where to find it

[supermerill]

I didn't try VS2022, so maybe, maybe not.If there is some problems, first thing is to stick with something that is known to work.

[DzzD]

fo sure it can compile "Visual Studio 17 2022" , I must missing some component as it dont find "Visual Studio 16 2019"

[DzzD]

So I manage to execute cmake fine with 2022, but I got 7 error in the next step msbuild process, here is one :

   "C:\Dev\SuperSlicer\deps\build\ALL_BUILD.vcxproj" (cible par défaut) (1) ->
   "C:\Dev\SuperSlicer\deps\build\deps.vcxproj" (cible par défaut) (3) ->
   "C:\Dev\SuperSlicer\deps\build\dep_cereal.vcxproj" (cible par défaut) (14) ->
     C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(
   242,5): error MSB8066: la build personnalisée de 'C:\Dev\SuperSlicer\deps\build\CMakeFiles\68d68a99c5c535af854c5
   0d82b97a5f8\dep_cereal-mkdir.rule;C:\Dev\SuperSlicer\deps\build\CMakeFiles\68d68a99c5c535af854c50d82b97a5f8\dep_
   cereal-download.rule;C:\Dev\SuperSlicer\deps\build\CMakeFiles\68d68a99c5c535af854c50d82b97a5f8\dep_cereal-update
   .rule;C:\Dev\SuperSlicer\deps\build\CMakeFiles\68d68a99c5c535af854c50d82b97a5f8\dep_cereal-patch.rule;C:\Dev\Sup
   erSlicer\deps\build\CMakeFiles\68d68a99c5c535af854c50d82b97a5f8\dep_cereal-configure.rule;C:\Dev\SuperSlicer\dep
   s\build\CMakeFiles\68d68a99c5c535af854c50d82b97a5f8\dep_cereal-build.rule;C:\Dev\SuperSlicer\deps\build\CMakeFil
   es\68d68a99c5c535af854c50d82b97a5f8\dep_cereal-install.rule;C:\Dev\SuperSlicer\deps\build\CMakeFiles\efd2c0bbac0
   b3e326198571208a7f310\dep_cereal-complete.rule;C:\Dev\SuperSlicer\deps\build\CMakeFiles\c35c6af29a8fb793aed2fba8
   d6617004\dep_cereal.rule;C:\Dev\SuperSlicer\deps\CMakeLists.txt' s'est arrêtée. Code 1. [C:\Dev\SuperSlicer\deps
   \build\dep_cereal.vcxproj]

any idea ?

[supermerill]

no, never happened to me.

[DzzD]

I still got one error.... when building dependency :

ÉCHEC de la build.

       "C:\Dev\SuperSlicer\deps\build\ALL_BUILD.vcxproj" (cible par défaut) (1) ->
       "C:\Dev\SuperSlicer\deps\build\deps.vcxproj" (cible par défaut) (3) ->
       "C:\Dev\SuperSlicer\deps\build\dep_openvdb.vcxproj" (cible par défaut) (17) ->
       "C:\Dev\SuperSlicer\deps\build\dep_blosc.vcxproj" (cible par défaut) (19) ->
       (CustomBuild cible) ->
         CUSTOMBUILD : warning : squelched 54 whitespace errors [C:\Dev\SuperSlicer\deps\build\dep_blosc.vcxproj]
         CUSTOMBUILD : warning : 4 lines applied after fixing whitespace errors. [C:\Dev\SuperSlicer\deps\build\dep_blo
       sc.vcxproj]


       "C:\Dev\SuperSlicer\deps\build\ALL_BUILD.vcxproj" (cible par défaut) (1) ->
       "C:\Dev\SuperSlicer\deps\build\deps.vcxproj" (cible par défaut) (3) ->
       "C:\Dev\SuperSlicer\deps\build\dep_CGAL.vcxproj" (cible par défaut) (4) ->
       "C:\Dev\SuperSlicer\deps\build\dep_boost.vcxproj" (cible par défaut) (9) ->
       (CustomBuild cible) ->
         C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(
       242,5): error MSB8066: la build personnalisée de 'C:\Dev\SuperSlicer\deps\build\CMakeFiles\5119d4c7bcf2580fb03bc
       6647c79bc61\dep_boost-configure.rule;C:\Dev\SuperSlicer\deps\build\CMakeFiles\5119d4c7bcf2580fb03bc6647c79bc61\d
       ep_boost-build.rule;C:\Dev\SuperSlicer\deps\build\CMakeFiles\5119d4c7bcf2580fb03bc6647c79bc61\dep_boost-install.
       rule;C:\Dev\SuperSlicer\deps\build\CMakeFiles\efd2c0bbac0b3e326198571208a7f310\dep_boost-complete.rule;C:\Dev\Su
       perSlicer\deps\build\CMakeFiles\c35c6af29a8fb793aed2fba8d6617004\dep_boost.rule' s'est arrêtée. Code 1. [C:\Dev\
       SuperSlicer\deps\build\dep_boost.vcxproj]

    2 Avertissement(s)
    1 Erreur(s)

It seems related to bootstrap :
"Please consult bootstrap.log for further diagnostics."

wich contain :

...
...
property-set.c
sequence.c
order.c
G‚n‚ration de code en cours...
###
### Unknown toolset: vcunk
###
### Known toolsets are: acc, borland, cc, como, clang, darwin, gcc, gcc-nocygwin, intel-darwin, intel-linux, intel-win32, kcc, kylix, metrowerks, mipspro, msvc, qcc, pathscale, pgi, sun, sunpro, tru64cxx, vacpp, xlcpp, vc7, vc8, vc9, vc10, vc11, vc12, vc14, vc141, vc142, vmsdecc
###
###
### Unknown toolset: vcunk
###
### Known toolsets are: acc, borland, cc, como, clang, darwin, gcc, gcc-nocygwin, intel-darwin, intel-linux, intel-win32, kcc, kylix, metrowerks, mipspro, msvc, qcc, pathscale, pgi, sun, sunpro, tru64cxx, vacpp, xlcpp, vc7, vc8, vc9, vc10, vc11, vc12, vc14, vc141, vc142, vmsdecc
###

[supermerill]

seems like it's not compatible with 2022

[DzzD]

Ok so I failed to compile dependencies with VS 2022 .. for only 2 modules :(

If anyone is searching for the old download of Visual Studio 2019, it can be downloaded here : https://docs.microsoft.com/fr-fr/visualstudio/releases/2019/history

[DzzD]

So now that I can compile & run ! is there some kind of documentation somewhere that you can point to me ?

What are each package for ?

Can you show me a little example so it will be easier to sart ? like where package/file can I add a text field to the printer settings screen ?

[DzzD]

perfect I suppose there is no visual editor ?

[supermerill]

no, just restart.

[DzzD]

And for here :

seems that the ui files begin inside the panel

[supermerill]

That is much more difficult thing to do. You have to modify the Tab class. You're on your own with that.

[DzzD]

ok, thanks again as I found exacly where it is in Tab.cpp, now the problem is to re-learn c++ and it should be ok ;)

[DzzD]

This is going well, I got the GUI mostly done, now I need to play whith "Preset" and it, seems that it will be the hard part with all the hierarchical strcutre and so.

[supermerill]

You can "just" "apply" your modification to the current full print config. The hard part is to re-apply it when needed and to be able to make the gui to not be tagged as "modified".

[DzzD]

Hello, How are we supposed to send you a patch ?

[DzzD]

I know but this is for a tiny change unrelated from what I am working on (sub/version preset), this is just two little patches, I was wondering if there was a way to send it, but I can create a pull request if required

[tome9111991]

I will find the best solution is you fork SuSi and make change on your forked repo.
If you done you can create a Pull request.
Merill can see the changes and cand merge with one click.

[DzzD]

Yes I already did it and I am working on it, I will do a pull request but I was just wondering if sometime little patch could be applied without all the complexity of a fork etc..., (note that I am also learning at the same time for one of my own project that I open sourced this weeks ! https://github.com/DzzD/TiGL ;) )

[supermerill]

Your local repo is a fork.
You can submit any branch as a pullrequest. If you add some commit in a branch (moving the branch tag), then the pull request will update accordingly.
You have a little thing to submit? commt, create a branch here, push and click on "submit pr".
The little commit is in the middle of a a big work-in-progress? create a branch at my master, then cherry-pick the commit, push the branch, click on "submit pr"
With tortoisegit, it's one click per step. Done in ~20 sec.
Giving a patch to incorporate nececitate more work on your side & my side.

[DzzD]

ok, thanks for this summary