Smashing / smashing

The exceptionally handsome dashboard framework in Ruby and Coffeescript.
https://smashing.github.io/
MIT License
3.22k stars 324 forks source link

Compatibility error while installing Smashing #168

Closed Qumera closed 3 years ago

Qumera commented 4 years ago

This is a request for support and not a bug (as labelled).

kinow commented 4 years ago

Hi @Qumera , I saw that when you created this issue it had a more detailed description. Did you remove it? If you could include it, I think it would be easier to try to reproduce/debug it, please.

Thanks!

Qumera commented 4 years ago

Hi @kinow, I might have removed it by mistake. I am adding the description here.

I am trying to install Smashing (1.2.0) and facing the following error: ERROR: While executing gem ... (Encoding::CompatibilityError) incompatible character encodings: ASCII-8BIT and UTF-8

To reproduce: gem install smashing

OS: Windows 10 Browser: Chrome Version 83.0.4103.116 (Official Build) (64-bit) ruby 2.3.3p222 (2016-11-21 revision 56859) [i386-mingw32] gem 2.5.2

gem list- actioncable (5.1.3) actionmailer (5.1.3) actionpack (5.1.3) actionview (5.1.3) activejob (5.1.3) activemodel (5.1.3) activerecord (5.1.3) activerecord-sqlserver-adapter (5.1.1) activesupport (5.1.3) arel (8.0.0) bigdecimal (1.2.8) builder (3.2.3) bundler (1.15.3) coffee-rails (4.2.2) coffee-script (2.4.1) coffee-script-source (1.12.2) concurrent-ruby (1.0.5) did_you_mean (1.0.0) erubi (1.6.1) execjs (2.7.0) ffi (1.9.18 x86-mingw32) globalid (0.4.0) i18n (0.8.6) io-console (0.4.5) jquery-rails (4.3.1) json (1.8.3) loofah (2.0.3) mail (2.6.6) method_source (0.8.2) mime-types (3.1) mime-types-data (3.2016.0521) mini_portile2 (2.3.0) minitest (5.8.5) net-telnet (0.1.1) nio4r (2.1.0) nokogiri (1.8.1 x86-mingw32) pg (0.21.0 x86-mingw32) power_assert (0.2.6) psych (2.1.0) rack (2.0.3) rack-test (0.6.3) rails (5.1.3) rails-dom-testing (2.0.3) rails-html-sanitizer (1.0.3) railties (5.1.3) rake (12.1.0, 10.4.2) rb-fsevent (0.10.2) rb-inotify (0.9.10) rb-readline (0.5.5) rdoc (4.2.1) rubyzip (1.2.1) sass (3.5.1) sass-listen (4.0.0) sass-rails (5.0.6) sprockets (3.7.1) sprockets-rails (3.2.1) sqlite3 (1.3.13 x86-mingw32) sqlite3-ruby (1.3.3) test-unit (3.1.5) thor (0.20.0) thread_safe (0.3.6) tilt (2.0.8) tiny_tds (2.0.0 x86-mingw32) tzinfo (1.2.3) websocket-driver (0.6.5) websocket-extensions (0.1.2)

I have tried most of the solutions on the internet but the issue is not resolved.

Thank you.

kinow commented 4 years ago

Thanks @Qumera ! Will try to reproduce it on a Win 10.

Any reason you couldn't use smashing 1.3.0?

Qumera commented 4 years ago

It is because the rails version I are using has ruby version 2.3 and Smashing 1.3 requires ruby 2.5 But even if I try to install the latest Smashing version I am still facing this error.

kinow commented 4 years ago

It is because the rails version I are using has ruby version 2.3 and Smashing 1.3 requires ruby 2.5

Ah, good point!

But even if I try to install the latest Smashing version I am still facing this error.

Good to know, should make it easier to investigate the problem.

Thanks @Qumera !

kinow commented 4 years ago

Hi @Qumera

Tested with the latest version, on Windows 10 Pro. I installed Ruby with the Linux subsystem, using Ubuntu from Windows store. It took near 1 hour to install everything :eyes:

Once it was installed, everything worked with no issues.

Capture

I installed Ruby 2.7.1 following these instructions with rbenv: https://gorails.com/setup/windows/10

Hope that helps

Qumera commented 4 years ago

Thank you @kinow, I shall try this.

kinow commented 3 years ago

Hi @Qumera ,

I finally found some spare time to try installing Smashing on Windows. I installed the current gem (1.3.4), on Windows 10 pro, with Ruby 3.0.0 (stable, installed with RubyInstaller). Had to also install NPM, and patch two gems.

Updated installation instructions: https://github.com/Smashing/smashing/wiki/Installation#windows

I'd still recommending using Linux if possible, or WSL on Windows. Windows itself being the last option due to the gems issues with Windows.

Hope that helps! Bruno