Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README for Windows #1309

Merged
merged 89 commits into from
Feb 2, 2023
Merged

Update README for Windows #1309

merged 89 commits into from
Feb 2, 2023

Conversation

DivingDuck
Copy link
Collaborator

Update for README.md and release_windows.bat.

Import latest updates from Kliment
Merge last changes from Kliment
Update to latest version from Kliment
Latest updates from Kliment
New updates from Kliment macos package
Pull newest updates from Kliment
Update from Kliment RC8
Updates from Kiment master
Replacing time.clock() with time.perf_counter() --> Deprecated since Python 3.3 and deleted in Python 3.8

Replacing wx.FutureCall with wx.CallLater --> wxPyDeprecationWarning
1. Add directory GTK3Windows10-64 with all needed DLL’s
2. Modified release_windows.bat for local compilation too
3. Modified Github action workflow for Windows 10-64bit only
Select GTK-3 binaries based on available bundle and x32/x64 architecture
…tory, change buildpackage-win.yml to integrate GTK3 as submodule and compile the correct version GTK3 version for 32-/64-bit or as external reference via windows system environment path
…as these are not longer accepted for Python 3.10Correction for update pip and remark for droped wxPython x86 support
…so pyglet version needs to be below 2.0 (requirements.txt and release_windows.bat)

Add superslicer.ini to .gitignore.
Latest changes from Kliment
merge branch testPython3.10 into master
Fix and update Windows build scripts by DivingDuck
README: Update Debian/Ubuntu installation
release_windows.bat: Update instruction and deactivate echo for wxPython workaround
Additional update for Windows
@DivingDuck
Copy link
Collaborator Author

DivingDuck commented Feb 2, 2023

A GIT noob question: Can you give me a tip how I can compress those differences in my repository w/o loosing my info's?

@DivingDuck DivingDuck mentioned this pull request Feb 2, 2023
2 tasks
@rockstorm101
Copy link
Collaborator

Can you give me a tip how I can compress those differences in my repository w/o loosing my info's?

I would say git rebase is your best friend here. I use it all the time on my local copy before submitting PRs here. Caution note, it's a command that rewrites history so it must be used with care and never really on public repositories. This guide I think is quite good: https://www.atlassian.com/git/tutorials/rewriting-history/git-rebase

@kliment
Copy link
Owner

kliment commented Feb 2, 2023

I'll squash them all into one commit here. Now that your repo is up to date with mine, you don't need to keep all those merge commits.

@kliment kliment merged commit afdbe5b into kliment:master Feb 2, 2023
@kliment
Copy link
Owner

kliment commented Feb 2, 2023

If you just want to get the same state on your side without all the merge commits you can also pull from my repo and force-push to yours.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants